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

Change Testing Framework #117

Open
aidanm3341 opened this issue Oct 8, 2024 · 1 comment
Open

Change Testing Framework #117

aidanm3341 opened this issue Oct 8, 2024 · 1 comment

Comments

@aidanm3341
Copy link
Member

aidanm3341 commented Oct 8, 2024

This project currently uses Karma as its test runner. Since Karma is now deprecated and is no longer receiving any updates, we should update to use something more modern.

Technology Options

@bogdumi and I discussed this and came up with the following options:

  • Jest - Popular, but does not always play nicely with ESM or Typescript
  • Vitest - Newer, but focuses on ESM and Typescript, as well as being quick and robust.
  • Node Test Runner - Doesn't support Typescript natively, and is a very barebones framework. Perhaps does not have the features necessary for a larger project.

Given our positive experience with Vitest and the maturity of its features, we are leaning towards that as the framework of choice to replace Karma.

@Davidhanson90
Copy link

My experiences migrating our projects to Jest have left me disappointed. It's not terrible but not brilliant either. Debugging harder generally and module support patchy.

Vite test is interesting but not tried yet. Would be interested to trial it.

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

No branches or pull requests

2 participants