From eb6edbf0df07c82dc689a61ef9feb0817f07cbfd Mon Sep 17 00:00:00 2001 From: Andreas Tolfsen Date: Fri, 16 Aug 2019 12:58:32 +0000 Subject: [PATCH] bug 1540655: remote: document how to run Puppeteer tests; r=remote-protocol-reviewers,jdescottes Differential Revision: https://phabricator.services.mozilla.com/D39659 --HG-- extra : moz-landing-system : lando --- remote/doc/Testing.md | 25 +++++++++++++++++++++++-- 1 file changed, 23 insertions(+), 2 deletions(-) diff --git a/remote/doc/Testing.md b/remote/doc/Testing.md index 855b2c4ee86b..8d1387c887ad 100644 --- a/remote/doc/Testing.md +++ b/remote/doc/Testing.md @@ -23,8 +23,8 @@ 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_: @@ -47,3 +47,24 @@ 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