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.

Sign up for GitHub

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

Jump to bottom

Proposal: Moving from Jest to Vitest #894

Draft

lserra-iov wants to merge 1 commit into feature/2.3 from feature/replace-jest-with-vitest

Contributor

lserra-iov commented Nov 5, 2024

Vitest offers a great opportunity to improve our testing speed and workflow efficiency. Is compatible with Jest APIs, meaning minimal changes to our existing tests.

Comparison between action using Jest:

Test Suites: 21 passed, 21 total
Tests: 125 passed, 125 total
Snapshots: 0 total
Time: 107.327 s

Versus using Vitest:

Test Files  21 passed (21)
Tests  125 passed (125)
Start at  16:48:22
Duration  24.30s (transform 1.09s, setup 0ms, collect 50.36s, tests 701ms, environment 11.18s, prepare 2.19s)


          Replace jest with vitest

f551d3d

github-actions bot commented Nov 5, 2024

Dependency Review

The following issues were found:

✅ 0 vulnerable package(s)
✅ 0 package(s) with incompatible licenses
✅ 0 package(s) with invalid SPDX license definitions
✅ 0 package(s) with unknown licenses.
⚠️ 4 packages with OpenSSF Scorecard issues.

View full job summary

sonarqubecloud bot commented Nov 5, 2024

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet