☠☠ backed out by 79127c2c7123 ☠ ☠ | |
author | Andreas Tolfsen <ato@sny.no> |
Wed, 14 Aug 2019 14:58:16 +0000 | |
changeset 487927 | 641a7cb252988593c7d20107a2e833c83673f634 |
parent 487926 | 73236f81da44a9bb496fb00cba8beb3b5033725d |
child 487928 | 1a23d770d8a1c0f0d13b5211c5b9380e69c000f7 |
push id | 36433 |
push user | btara@mozilla.com |
push date | Wed, 14 Aug 2019 21:57:52 +0000 |
treeherder | mozilla-central@7d9a2196d313 [default view] [failures only] |
perfherder | [talos] [build metrics] [platform microbench] (compared to previous push) |
reviewers | remote-protocol-reviewers, jdescottes |
bugs | 1540655 |
milestone | 70.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
|
--- 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