-
Notifications
You must be signed in to change notification settings - Fork 34
Timeout errors #46
Comments
Would be awesome to fix this upstream in Jest. Simen has already a PR open to fix that. |
Agreed, I haven't been able to make the faked |
Close this until that is in place? |
This shouldn't be a problem with the e2e runner, because we don't use vm anywhere. |
So e2e runner is not using Jest to run test cases? |
Correct. The e2e test runner runs tests in a single node process. We can do this because all of the important code being tested is in the website running in the browser. The code in node is just the small bits used to drive the test. |
Ok - I will have to look into the playwright-runner e2e test runner later. Maybe I misunderstand, but I am using Jest for much more such as reporters, being able to customize runner options and many, many other of Jest's features (expect statements) etc. And I want to use Jest to run them in parallell, taking the caching. performance (run failed first) etc. into account. Edit: The examples in the README clearly use Jest syntax, so I suppose I've just not familiarized myself yet with the implementation details. |
For reference, see microsoft/playwright#2031
This piece of code will not work when running inside Jest:
It is possible that the TimeoutError is a different instance because Jest test cases is run inside a vm context, whereas PlaywrightRunnerE2E runs in Node.js.
This does work:
Note: Have not tested this with playwright-runner, but just assuming this is a problem here as well since it was with jest-playwright.
The text was updated successfully, but these errors were encountered: