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
A clear and concise description of what the bug is.
We have a setup of E2E tests of React app with puppeteer. After upgrading project from Node 16 to Node 18, jest-puppeteer fails to determine that server is up and running (it reaches launchTimeout). After some digging I found out that library uses wait-on library which seems to have an issue with IPv6 addresses (which are favoured by Node since 17) jeffbski/wait-on#127.
I tried starting only hot server yarn start and using wait-on to see if issue also occurs and it does. Increasing launchTimeout doesn't help, tool simply cannot determine if anything listens on that port.
To Reproduce
Steps to reproduce the behavior:
Checkout repository or setup it on your own (create-react-app + puppeteer):
nvm use 18
yarn
yarn test:e2e
Expected behavior
jest-puppeteer recognises that server is running and proceeds with running tests.
I tested using wait-port instead of wait-on. This changes waitOnScheme but works for HTTP servers. Haven't tested sockets yet. It would be probably easier and more reliable to fix wait-on...
I'm ok with breaking changes if we need to switch dependencies. We are going to need breaking changes for this package to work with the latest version of puppeteer and jest.
🐛 Bug Report
A clear and concise description of what the bug is.
We have a setup of E2E tests of React app with puppeteer. After upgrading project from Node 16 to Node 18,
jest-puppeteer
fails to determine that server is up and running (it reacheslaunchTimeout
). After some digging I found out that library useswait-on
library which seems to have an issue with IPv6 addresses (which are favoured by Node since 17) jeffbski/wait-on#127.I tried starting only hot server
yarn start
and usingwait-on
to see if issue also occurs and it does. IncreasinglaunchTimeout
doesn't help, tool simply cannot determine if anything listens on that port.To Reproduce
Steps to reproduce the behavior:
Expected behavior
jest-puppeteer recognises that server is running and proceeds with running tests.
Link to repl or repo (highly encouraged)
https://gitlab.com/glayfieldWH/react-tests/-/tree/main/react-test
Run
npx envinfo --system --binaries --npmPackages expect-puppeteer,jest-dev-server,jest-environment-puppeteer,jest-puppeteer,spawnd --markdown --clipboard
Paste the results here:
The text was updated successfully, but these errors were encountered: