Closed Bug 1585274 Opened 5 years ago Closed 5 years ago

Run Puppeteer unit tests in non-headless mode by default

Categories

(Remote Protocol :: Agent, task, P1)

task

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: whimboo, Assigned: whimboo)

References

Details

Attachments

(2 files)

Right now it is not possible to run any of the remote protocol tests in non-headless mode. Given that other test jobs only use that mode by default in CI, but not locally on developers machines, we should do the same for this test suite.

Actually the browser chrome tests by default don't use headless mode. It's really only the Puppeteer unit tests.

Summary: Allow to run remote protocol tests in non-headless mode → Allow to run Puppeteer unit tests in non-headless mode
Blocks: puppeteer
Priority: -- → P3
Assignee: nobody → hskupin
Status: NEW → ASSIGNED
Priority: P3 → P1
Summary: Allow to run Puppeteer unit tests in non-headless mode → Run Puppeteer unit tests in non-headless mode by default

Similar to all the other test jobs also the Puppeteer jobs should
not run in headless by default. Instead it should be an opt-in.

Pushed by hskupin@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/cd07efc3b577
[remote] Run Puppeteer unit tests in non-headless mode by default. r=remote-protocol-reviewers,maja_zf
https://hg.mozilla.org/integration/autoland/rev/777123ec0645
"mach test" for Puppeteer unit test has to default to non-headless mode. r=mozbase,ahal
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: