refactor: migrate testing framework from Jest to Vitest#336
Open
refactor: migrate testing framework from Jest to Vitest#336
Conversation
…for module resolution remove prettier glsl remains to validate do : git clean -dfx npm ci npx tsc -p packages/network-map-layers/tsconfig.json --noEmit npx tsc -p packages/network-viewer-core/tsconfig.json --noEmit npx tsc -p demo/tsconfig.json --noEmit npm run check npm run lint npm run lint:format npm start Signed-off-by: Arnaud Marant <[email protected]>
- Updated test scripts in package.json to use Vitest instead of Jest. - Removed Jest-related dependencies and added Vitest and its plugins. - Deleted svgTransform.ts as it is no longer needed. - Updated tsconfig.json to remove references to Jest and svgTransform.ts. - Added vitest.config.ts for Vitest configuration, including coverage settings. Signed-off-by: Arnaud Marant <[email protected]>
Contributor
|
Jest : |
Signed-off-by: Arnaud Marant <[email protected]>
|
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
the goal is to be able to use browser test with playwright, be 5x faster, and no longer have babel dependencies
Please check if the PR fulfills these requirements
What kind of change does this PR introduce?
Jest -> Vitest
What is the current behavior?
test are runned in Jest
What is the new behavior (if this is a feature change)?
test are runned in Vitest
Does this PR introduce a breaking change or deprecate an API?