bug 1540655: remote: document how to run Puppeteer tests; r=remote-protocol-reviewers,jdescottes
authorAndreas Tolfsen <ato@sny.no>
Fri, 16 Aug 2019 12:58:32 +0000
changeset 488506 836e302446342789cb0435701c4897599390c955
parent 488505 7712e6870bd3483cd4d2abe78f76de35dc6fda2e
child 488507 8a9e9189cd98350f27c9f36bddca67ff03082339
push id36444
push userccoroiu@mozilla.com
push dateFri, 16 Aug 2019 16:24:18 +0000
treeherdermozilla-central@8a9e9189cd98 [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewersremote-protocol-reviewers, jdescottes
bugs1540655
milestone70.0a1
first release with
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
last release without
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
bug 1540655: remote: document how to run Puppeteer tests; r=remote-protocol-reviewers,jdescottes Differential Revision: https://phabricator.services.mozilla.com/D39659
remote/doc/Testing.md
--- 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
 display.
 
 [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