test: migrate from jest to vitest#210
Merged
Merged
Conversation
Member
|
We did similar things 😬 #211 |
Contributor
Author
|
yes! Lets's merge yours first and I will rebase this one. |
fmalcher
reviewed
Jun 8, 2026
- Replace Jest with Vitest as test runner for improved performance - Update test configuration and snapshots to Vitest format - Add Angular 22 integration test to CI workflow - Update documentation to reflect Vitest usage - Add vitest.config.ts and remove jest.config.js - Update tsconfig for Vitest compatibility - Add Angular 22 test fixture for version compatibility testing - Fix trailing whitespace in README and contributor documentation - Update supported Angular version range from 18-21 to 18-22
- Change double quotes to single quotes in vitest MockInstance imports - Align quote style across test.command.allowUnknownOption.spec.ts - Align quote style across test.fork-fixes.spec.ts - Align quote style across test.options.version.spec.ts - Maintain consistency with project's single-quote preference
fmalcher
approved these changes
Jun 9, 2026
JohannesHoppe
added a commit
that referenced
this pull request
Jun 9, 2026
…e, docs) (#213) fix: tidy up Vitest migration follow-ups (#210) Small, non-behavioral cleanups after the Jest→Vitest migration: - interfaces.ts: revert beforeAdd param `any` → `unknown` (project No-any rule) - add missing vitest type imports (Mock / MockInstance) to 5 specs that used the types without importing them — they aren't provided by vitest/globals, so this fixes editor/tsc errors (runtime was unaffected; specs aren't typechecked in CI) - tsconfig.json: types ["vitest/globals", "node"] so specs keep Node ambient types (process, Buffer, …) - prune 2 obsolete jest-format snapshots left behind in ng-add.spec.ts.snap - builder-integration.spec.ts: drop an unnecessary `as any` - test.fork-fixes.spec.ts: restore the "implicitly tested by test.options.bool.no.spec.ts" note (lost with its empty describe, which vitest rejects) - docs: add "Supporting a new Angular version" to the contributor README TOC Build clean, all 430 tests green, no obsolete snapshots.
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.
Vitest migration