chore(web): migrate to vitest #5754
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jorge-dev
force-pushed
the
fix/web-dev-server-and-tests
branch
2 times, most recently
from
1d14196
to
4946666
Compare
jorge-dev
changed the title
… fix the dev command error
-- this removes jest dependencies
…jest-dom matchers in tests
jorge-dev
force-pushed
the
fix/web-dev-server-and-tests
branch
from
4946666
to
e234e11
Compare
jrasm91
changed the title
jrasm91
approved these changes
Jan 1, 2024
martabal
pushed a commit
that referenced
this pull request
Jan 9, 2024
* Updated vite and ts config file with vtest options and a new alias to fix the dev command error * Updated package script and update the packages -- this removes jest dependencies * Added new setup file needed in vitest in order to be able to use the jest-dom matchers in tests * Updated deprecated utilities when using faker * Updated test files and mocks to use vitest instead of jest * Enabled web test check in GitHub actions * remove babel dependencies as they are no longer needed with vitest * move the jest config files to a folder in case we need to go back to jest * chore: remove old files --------- Co-authored-by: Jason Rasmussen <jrasm91@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change fixes an error while trying to run the
npm run devcommand and serve the application.This was due to a missing alias in the vite config file.
The change is to re-enable the existing unit tests that were failing after the update to Svelte 4.
Most of the tests were failing due to Jest trying to import packages using require instead of import since it was running in CSJ mode instead of ESM mode that Svelte 4 requires.
I spent 2 days trying to configure jest to fix this issue but nothing worked.
That was the main reason to try vitest for this project.
Vitest works with almost no extra configuration and it was built using ESM so all the tests were able to be fixed with very minor modifications since vitest's api is almost fully compatible with Jest API (with some exceptions)
These changes only affect the testing environment
