Feat/migrate jest to vitest #346
Open
Conversation
This file contains hidden or 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
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
- replace jest with vitest - remove jest references no longer used - add vitest configuration file in package - add vitest configuration file to workspace
- replace jest with vitest - remove jest references no longer used - add vitest configuration file in package - refactor extend functions so that they work with vitest - rename jest extensions file as `VitestExtensions.ts` - add vitest types
- replace jest with vitest - add vitest configuration file in package - remove jest configuration file
- remove tests scripts from package.json - delete tsconfig.test.json config file no longer needed - add vitest api as global so that import is no required such as describe, expect, it, etc.
- remove tests scripts from package.json - delete tsconfig.test.json config file no longer needed - add vitest api as global so that import is no required such as describe, expect, it, etc.
- remove tests scripts from package.json - delete tsconfig.test.json config file no longer needed - add vitest api as global so that import is no required such as describe, expect, it, etc.
- replace jest with vitest in examples/testing-suite - remove jest dependencies - install vitest dev dependency - replace jest config files with vitest config files
- pass vitest flags to test execution
hereje
force-pushed
the
feat/migrate-jest-to-vitest
branch
from
1d312b7 to
026064d
Compare
remove extra blank line
remove extra blank line
remove extra blank line
remove extra blank line
remove extra blank line
- add globals: true to vitest.config.ts on main path of workspace
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.
Moving automated tests to Vitest
Fixes: #228