bug 1540655: remote: document how to run Puppeteer tests; r=remote-protocol-reviewers,jdescottes draft
Fri, 16 Aug 2019 13:22:34 +0000
changeset 2220734 25a68646e90c19ae4509bd3ed25a94b346576458
parent 2220733 00e1733fb011e778b4d73e4bc8df721764930af1
child 2220735 bee8fd5008cf93078ae46febc4feda5c0eaafdba
push id406994
push userreviewbot
push dateFri, 16 Aug 2019 13:23:14 +0000
treeherdertry@5f50de08beda [default view] [failures only]
reviewersremote-protocol-reviewers, jdescottes
bug 1540655: remote: document how to run Puppeteer tests; r=remote-protocol-reviewers,jdescottes Differential Revision: https://phabricator.services.mozilla.com/D39659 Differential Diff: PHID-DIFF-4mvx75aezpxfbioymgap
--- a/remote/doc/Testing.md
+++ b/remote/doc/Testing.md
@@ -18,18 +18,18 @@ chatty, it can sometimes be useful to ru
 	% ./mach xcpshell-test --sequential remote/test/unit/test_Assert.js
 The unit tests will appear as part of the `X` (for _xpcshell_) jobs
 on Treeherder.
 [xpcshell]: https://developer.mozilla.org/en-US/docs/Mozilla/QA/Writing_xpcshell-based_unit_tests
-Functional tests
+Browser chrome tests
 We also have a set of functional [browser chrome] tests located
 under _remote/test/browser_:
 	% ./mach mochitest remote/test/browser/browser_cdp.js
 The functional tests will appear under the `M` (for _mochitest_)
 category in the `bc` (_browser-chrome_) jobs on Treeherder.
@@ -42,8 +42,29 @@ mode]:
 The `--headless` flag is equivalent to setting the `MOZ_HEADLESS`
 environment variable.  You can additionally use `MOZ_HEADLESS_WIDTH`
 and `MOZ_HEADLESS_HEIGHT` to control the dimensions of the virtual
 [browser chrome]: https://developer.mozilla.org/en-US/docs/Mozilla/Browser_chrome_tests
 [headless mode]: https://developer.mozilla.org/en-US/Firefox/Headless_mode
+Puppeteer tests
+In addition to our own Firefox-specific tests, we run the upstream
+[Puppeteer test suite] against our implementation to track progress
+towards achieving full [Puppeteer support] in Firefox.
+These tests are vendored under _remote/test/puppeteer/_ and are
+run locally like this:
+	% ./mach test remote/test/puppeteer/test
+On try they appear under the `remote(pup)` symbol, but because they’re
+a Tier-3 class test job they’re not automatically scheduled.
+To schedule the tests, look for `source-test-remote-puppeteer` in
+`./mach try fuzzy`.
+[Puppeteer test suite]: https://github.com/GoogleChrome/puppeteer/tree/master/test
+[Puppeteer support]: https://bugzilla.mozilla.org/show_bug.cgi?id=puppeteer