You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Running puppeteer with jest is quite flakey and can cause issues. Is there anyway to do retries with this?
Describe the solution you'd like
Some kind of hook for a retry or some way to get handle to running puppeteer process
Describe alternatives you've considered
Tried jest-retries but didn't get it to work
Additional context
The text was updated successfully, but these errors were encountered:
When you say flaky, is it a specific issue with jest-puppetteer or are you pointing at a general issue when writing E2E tests?
I would assume you mean the latter (but if you know of some specifics with jest-puppeteer let me know!) and I agree that E2E tests are flaky, or rather harder to write and maintain.
Have you seen the expect-puppeteer API that gets added by jest-puppeteer, described here https://github.com/smooth-code/jest-puppeteer/tree/master/packages/expect-puppeteer/README.md#api? That sort of approach helps writing more robust E2E tests without having to go down the route of retrying the tests themselves.
I was having issues earlier with puppeteer crashing and giving out network errors in the middle of a test. I was looking earlier for a way to restart puppeteer between tests.
Is your feature request related to a problem? Please describe.
Running puppeteer with jest is quite flakey and can cause issues. Is there anyway to do retries with this?
Describe the solution you'd like
Some kind of hook for a retry or some way to get handle to running puppeteer process
Describe alternatives you've considered
Tried jest-retries but didn't get it to work
Additional context
The text was updated successfully, but these errors were encountered: