Depends on D188104
> TestExpectations.json
> Launcher specs Puppeteer Puppeteer.launch should launch Chrome properly with
Those tests can't work on Mozilla CI because we don't perform a regular install of puppeteer there.
> TestExpectations.json
> Launcher specs Puppeteer Puppeteer.launch should work with no default arguments
Same thing.
> TestExpectations.json
> [proxy.spec] request proxy should respect proxy bypass list
This test frequently fails on our CI because the responseCompleted event is received too late (ie after navigate has resolved). Filed https://bugzilla.mozilla.org/show_bug.cgi?id=1852891 about this.
> TestExpectations.json
> [network.spec] network Response.fromCache should work
I am not sure how this one passes on the puppeteer CI. Locally I never get a second request for the CSS file which we expect to get from the cache. Maybe we are completely missing the request in this case, but I don't know how this can pass on the puppeteer CI.
> TestExpectations.json
> [waittask.spec] waittask specs Frame.waitForFunction should work when resolved right before execution context disposal
The polling mechanism used in this test always fail for me locally and on CI. It might pass on puppeteer CI if it has slightly different timings?
> evaluation.spec.ts
> should not throw an error when evaluation does a navigation
Is ending too quickly on our CI, and the next test is trying to use the browsing context which is navigating, failing frequently.
> page.spec.ts
> Page.Events.PageError should fire
I frequently receive other errors for the same context during the test, which make the test fail. I'm proposing to wait for the specific error message here to avoid the issue.
> target.spec.ts
> should timeout waiting for a non-existent target
Depending on which test ran before, there could be a `server.EMPTY_PAGE` target available, and for some reason that lead the test to immediately fail with a TIMEOUT. Not quite sure why, but I think using an obviously not matching URL is safer?
Differential Revision: https://phabricator.services.mozilla.com/D188105
An explanation of the Firefox Source Code Directory Structure and links to
project pages with documentation can be found at:
https://firefox-source-docs.mozilla.org/contributing/directory_structure.html
For information on how to build Firefox from the source code and create the patch see:
https://firefox-source-docs.mozilla.org/contributing/contribution_quickref.html
If you have a question about developing Firefox, and can't find the solution
on https://firefox-source-docs.mozilla.org/, you can try asking your question on Matrix at chat.mozilla.org in `Introduction` (https://chat.mozilla.org/#/room/#introduction:mozilla.org) channel.
Nightly development builds can be downloaded from:
https://archive.mozilla.org/pub/firefox/nightly/latest-mozilla-central/
- or -
https://www.mozilla.org/firefox/channel/desktop/#nightly
Keep in mind that nightly builds, which are used by Firefox developers for
testing, may be buggy.
5da943f86c