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

refactor(test): moving unit testing over to Vitest #405

Merged
merged 1 commit into from
Aug 13, 2023

Conversation

erunion
Copy link
Member

@erunion erunion commented Aug 13, 2023

🧰 Changes

I've been extremely impressed with Vitest!

Before

npx nyc mocha "test/**/*.test.ts"  4.20s user 0.34s system 35% cpu 12.645 total

After

 Test Files  5 passed | 1 skipped (6)
      Tests  31 passed | 8 skipped (39)
   Start at  19:42:15
   Duration  5.42s (transform 230ms, setup 0ms, collect 653ms, tests 9.71s, environment 1ms, prepare 313ms)

npx vitest run  3.19s user 0.73s system 66% cpu 5.885 total

We unfortunately have to scuttle our browser tests for the moment though because Vitest's browser mode is still very experimental. When that's a bit more stable, and doesn't crash upon trying to run tests in a browser, I'll re-enable those in here.

@erunion erunion added the refactor Issues about tackling technical debt label Aug 13, 2023
@erunion erunion merged commit c2efb42 into main Aug 13, 2023
10 checks passed
@erunion erunion deleted the refactor/move-to-vitest branch August 13, 2023 02:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
refactor Issues about tackling technical debt
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant