-
-
Notifications
You must be signed in to change notification settings - Fork 129
[test] Setup tests on all browsers #1592
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
[test] Setup tests on all browsers #1592
Conversation
✅ Deploy Preview for base-ui ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Firefox connection timeouts look like vitest-dev/vitest#7377 |
@@ -43,11 +43,16 @@ | |||
"test:regressions:dev": "vite --config test/regressions/vite.config.mjs", | |||
"test:regressions:run": "cross-env VITEST_ENV=chromium vitest --project regressions", | |||
"test:regressions:server": "serve test/regressions -p 5173", | |||
"test:jsdom": "cross-env NODE_ENV=test VITEST_ENV=jsdom vitest --project @base-ui-components/react --project docs", | |||
"test:_unit": "cross-env NODE_ENV=test vitest --project @base-ui-components/react --project docs", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is the underscore in test:_unit
intentional?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, to indicate it's a subtask, not meant to be used directly
Prepare npm scripts for running the test in each supported browser (Chromium, Firefox and WebKit) separately or in all at once.
I initially intended to run all browsers on CI, but they are quite unstable.