don't wait for networkidle2 unless a reason to #3118
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #3116
Prior to this change I would run
yarn test:testing headless
and sometimes it would break with:That error
Navigation failed because browser has disconnected!
supposedly "means that the node scripts that launched Puppeteer ends without waiting for the Puppeteer actions to be completed.".So there's something that attempts to close the
jest
tests without giving theexpect-puppeteer
a chance to close the browser instance.I'm more and more unimpressed with
expected-puppeteer
. It feels like walking on egg shells. And when certain errors happen sometimes, you have no idea where/which line in your*.test.js
code that started the headlesschrome
crashes.