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
Move to vitest #3231
Move to vitest #3231
Conversation
41f8b22
to
10b8155
Compare
I think it's a good move, we should try to achieve this |
e48280d
to
92d0e25
Compare
8b5f5aa
to
eb24e26
Compare
Codecov ReportBase: 100.00% // Head: 100.00% // No change to project coverage 👍
Additional details and impacted files@@ Coverage Diff @@
## main #3231 +/- ##
===========================================
Coverage 100.00% 100.00%
Complexity 2129 2129
===========================================
Files 572 569 -3
Lines 9279 9255 -24
Branches 175 182 +7
===========================================
- Hits 9279 9255 -24
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
b25d30a
to
4a57d77
Compare
Waiting for vitest-dev/vitest#2245 to be resolved before merging this one. |
It's now ready, thank you @AriPerkkio for the help on vitest :) |
I'll claim $300 fot this issue. |
Thanks for your work @Gnuk and @AriPerkkio !!! Plz follow this https://www.jhipster.tech/bug-bounties/#-bug-bounties to claim each part of bounty As discussed between you, 300 for @Gnuk and 200 for you @AriPerkkio : hope it's ok :-) Don't forget to comment this pull request with the open collective link, so I can approve it |
@Gnuk : approved |
@AriPerkkio : approved :-) |
Played with it. The "setup" (npm run test:watch) is a little bit long but then we finally have acceptable feedback loops on TS tests! |
No description provided.