Migrate tests from Karma to Vite + Vitest - #199
Open
v-aidaba wants to merge 1 commit into
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
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.
Karma and its Webpack test bundle are replaced by Vitest running in browser
mode on Playwright/Chromium, so the specs execute in a real browser without a
second build pipeline.
Testing
test.webpack.config.js
enums survive the esbuild transform, and fail loudly on unstubbed members
TestWrapper.render() helper
formatting model no longer supports
Scripts
Linux system packages) instead of a pretest hook, so test runs stay
offline-friendly
CI
--omit=dev)
Dependencies
entries, which typescript-eslint already provides
regenerator-runtime
5.11.1 and the visual utils to their 7.x releases
No production code changed. Verified with lint, package, npm audit --omit=dev
and test:coverage (63/63 passing).