-
-
Notifications
You must be signed in to change notification settings - Fork 112
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
chore(vitest): add vitest 2 browser beta test #715
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for tresjs-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
e2e tests would be a big help. Looking forward to this. |
@andretchen0 we need to cover e2e tests, we have some internal team discussion about it, stay tuned |
Here a repository with advanced manual and on demand examples in the playground: https://github.com/userquin/tresjs-vitest-browser-tests Can also run in StackBlitz, link in the readme file. |
This is just a test using Vitest beta v2.0 packages to run the new added test in the browser:
src/components/TresCanvas.test.ts
cloned from my previous branch (https://github.com/Tresjs/tres/blob/userquin/feat-vitest-browser/src/components/TresCanvas.test.ts).To run the browser test:
pnpm install && pnpm build
from root folderpnpm test:browser:none
from rootWe can also use webdriverio or playwright, you need to add the corresponding dependencies as dev dependencies and run:
pnpm test:browser:webdriverio
from root orpnpm test:browser:playwright
from rootThis PR using vitest packages from local tgz from this PR: vitest-dev/vitest#5815
✔️ DONE: Once we released a new beta version we can use vitest from npm registry.
For CI, we need to include webdriverio or playwright and configure headless to true.