Migrate test infrastructure from Karma/Jasmine to Vitest with hybrid approach#16793

Draft

Copilot wants to merge 51 commits intomasterfrom

copilot/migrate-karma-to-vitest

Commits on Jan 22, 2026

Initial plan
Copilot
committed
Phase 1: Update dependencies and configuration files for Vitest migration

Copilot
and
ChronosSF
committed
Phase 2: Remove all Karma configuration files

Copilot
and
ChronosSF
committed
Phase 3: Convert spec files from Jasmine to Vitest syntax (automated conversion)

Copilot
and
ChronosSF
committed
Phase 3 continued: Complete Jasmine to Vitest syntax conversion

Copilot
and
ChronosSF
committed
Add migration documentation and finalize Karma to Vitest migration

Copilot
and
ChronosSF
committed
Fix code review issues: environment config, duplicate properties, missing vi imports

Copilot
and
ChronosSF
committed
Switch to official Angular Vitest support via @angular/build:unit-test builder

Copilot
and
ChronosSF
committed
Update Vitest to v4.0.17 and related packages

Copilot
and
ChronosSF
committed
chore(*): pushing in proper lock, temp npm install in ci
ChronosSF
committed
fix(*): fixing lint errors in agentic run
ChronosSF
committed
fix(tests): some small fixes
ChronosSF
committed
Fix coverage configuration for Angular unit-test builder

Copilot
and
ChronosSF
committed
chore(*): fixing imports for v8 and playwright
ChronosSF
committed
Fix library test configuration - use vitest directly instead of Angular builder

Copilot
and
ChronosSF
committed
Update documentation to explain library vs application testing approach

Copilot
and
ChronosSF
committed
fix(ci): making tests run
ChronosSF
committed

Commits on Jan 24, 2026

Commits on Jan 26, 2026

Commits on Jan 27, 2026

fix(cd): additional migration fixes
ChronosSF
committed

Commits on Jan 29, 2026

test(*): translating all remaining spec files to vitest
ChronosSF
committed

Commits on Jan 30, 2026