Using Puppeteer's new headless mode causes tests to fail
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 165
- Forks
- 42
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 9
Description
In working on PR#314 I noticed that Chrome/Puppeteer introduces a new headless mode:
More details here: https://developer.chrome.com/articles/new-headless/
When opting in to this new mode (by setting headlines: 'new' in the Puppeteer config) several tests fail. As this new mode will eventually become the default we should fix the tests issue or file bugs against Puppeteer.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review PR #314 and the Puppeteer configuration to locate how the new headless mode is enabled. Run the tests with that mode, identify the failures, and either fix the test issues or document bugs for Puppeteer; done means the relevant tests pass or external bugs are filed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100