-
-
Notifications
You must be signed in to change notification settings - Fork 319
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: update the test runner #7404
base: unstable
Are you sure you want to change the base?
Conversation
Performance Report✔️ no performance regression detected Full benchmark results
|
81ab175
to
1d459f7
Compare
does your |
No there is some issue that is causing it to not be compatible. Was looking into it ChainSafe/benchmark#29. Will upgrade it very soon. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## unstable #7404 +/- ##
============================================
- Coverage 48.45% 48.24% -0.21%
============================================
Files 602 602
Lines 40387 40248 -139
Branches 2069 2069
============================================
- Hits 19568 19417 -151
- Misses 20781 20793 +12
Partials 38 38 |
does this PR need vitest 3.x? can we maintain 2.x for now? |
01c80ca
to
4fc6a6a
Compare
The Vitest 3 comes with a lot of changes, but for our interests are:
Vite 6 is considered more performant (specially for frontend stack). I was more interested in workspaces and started this PR because of it, but could not get that fit in our workflow. One issue running tests from individual package folder. So nothing critical for us, so can hold this PR merge or merge it. As you feel better. |
Motivation
Update vitest and browser engine.
Description
configs
directorywebdriverio
toplaywright
which is more stable and recommended by Vitest.NOTE
Reverted the
playwright
upgrade. See the comments.lodestar/configs/vitest.config.base.browser.ts
Lines 41 to 43 in d2a7af0
Steps to test or reproduce
Run all tests