-
Notifications
You must be signed in to change notification settings - Fork 1
Catch 8000 missing project level deps bug in e2e tests #12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Ideas:
I believe (1) is a must. I am not sure (2) is needed or even helpful. |
I am able to repro in examples by removing project
But to run tests I need those deps. One clean way to do this is first copy the example to a temporary directory to make break the directory nesting which confuses our tooling. For example I got this unexpected error while running Vite in the example too: Apparently the example Vite is trying to interact with an ancestor tsconfig file. Didn't even know it was, not good. |
Hitting PW fixture issues ... https://discord.com/channels/807756831384403968/1361366612627820624 |
Resolved, issue was my misunderstanding about PW workers. If a fixture fails, the worker is re-created thus leading to worker-scoped fixtures also being recreated. |
Our e2e tests do not catch #11. They should.
The text was updated successfully, but these errors were encountered: