Skip to content
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

Switch from Jest to Vitest #56

Merged
merged 1 commit into from
Sep 13, 2024
Merged

Switch from Jest to Vitest #56

merged 1 commit into from
Sep 13, 2024

Conversation

jsynowiec
Copy link
Owner

I now recommend using Vitest over Jest for unit and integration testing of TypeScript code. This PR has breaking changes and replaces Jest with Vitest.

Throughout 2023, my team and I gradually switched from Jest to Vitest in all the projects. We've found out that generally, Vitest is faster than Jest, especially for large test suits. Furthermore, Vitest has native support for ES modules, is easier to configure, and has a much nicer developer experience when used with TypeScript. For example, when working with mocks, spies and types.

@jsynowiec jsynowiec self-assigned this Apr 14, 2024
@jsynowiec jsynowiec merged commit 550dfd2 into main Sep 13, 2024
2 checks passed
@jsynowiec jsynowiec deleted the feature/vitest branch September 13, 2024 06:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant