Migrate unit tests from Jasmine/Karma to a modern stack
I maintainer di solito rispondono entro 1 giorno
@alexandrevryghem ci sta già lavorando.
Dal 2/10/2026.
Valutazione
Questa issue non è ancora stata valutata.
Descrizione
Is your feature request related to a problem? Please describe.
Upgrade to Angular v18 was finalized in DSpace 9.0 (DSpace/dspace-angular#3304). However, Jasmine/Karma is still used for unit tests but, as noted in the issue, Karma is deprecated.
Angular v21 declared stable support for Vitest. This is also the Angular team's default choice for new projects in v21+ (moreover, Angular team also provided a guide on Migrating from Karma to Vitest, so the migration can be semi-automated.)
I'd like us to discuss and plan a migration away from Karma to a modern test runner. From what I can see, the most commonly mentioned options are:
- Vitest (default in Angular >=v21)
- Jest (has been around longer)
- Web Test Runner (runs tests in a real browser rather than Node/jsdom)
Vitest and Jest are both a test runner and a testing library, so they replace both Karma + Jasmine stack. Web Test Runner replaces only Karma (uses bult-in Mocha framework support, but has Jasmine adapter web-test-runner-jasmine).
Also, check out Vitest's Comparisons with Other Test Runners page.
What about Jasmine? Cypress?
Just to avoid confusion: Karma is only the test runner (it launches the browser and reports results). Jasmine is the testing framework we actually write tests with (spyOn etc.).
Both Vitest and Jest support Jasmine-style syntax (and maintain compatibility with most Jasmine functions)
We also use Cypress as the e2e tool (so it's not related to unit tests)
- To learn more, see also Vitest's comparison Cypress section
Describe the solution you'd like
This ticket is to discuss and plan a migration away from Karma.
Describe alternatives or workarounds you've considered
We are currently still using Karma via @angular-devkit/build-angular and @angular-builders/custom-webpack:karma. This works for now, but it depends on a deprecated package
Changing the unit test runner while on Angular v20 could make a future v21 upgrade smoother
Additional information
Karma/Jasmine and Angular Timeline
- Angular v16 declared that Karma was deprecated.
- This version added experimental support for Jest, and Web Test Runner [source]
- Angular v20 added experimental support for Vitest [source]
- Angular v21 declared Vitest as the primary test runner (and stable), replacing Karma [source]
- Before v21, however, it wasn't clear which runner Angular would ultimately favor. For example this great comment from Angular team developer suggested that Angular was really fond of supporting Jest
Vitest has gained significant traction recently. According to npm trends, Vitest downloads surpassed Jest around April 2026, and now seem to be 2x higher (Jest was first published in NPM 15 years ago, Vitest 5 years ago).
Questions for the Community
- Any strong opinions (for or against) any particular test runner?
- Any other alternatives we should consider?
- Has anyone already migrated a large Angular project from Karma? If so, what challenges did you face?
- Does anyone have experience with Vitest in a large Angular monorepo?
- Are there any DSpace-specific testing needs that might complicate migration?
References
- DSpace/dspace-angular#3304
- Vitest's Comparisons with Other Test Runners
- Angular's Migrating from Karma to Vitest Guide
- https://github.com/angular/angular-cli/issues/25217#issuecomment-1581581005
- Medium post comparing Jest and Vitest
- NPM Trends (in case of 404 error, please go directly to npmtrends.com and select packages manually)
Additional sources not directly mentioned in this issue:
- https://github.com/DSpace/dspace-angular/issues/2 - test stack original issue in DSpace/dspace-angular
- In Jest, default JS runner can be replaced with fast Rust-based SWC
- This post goes more into details on migrating from Karma to Vitest
- Angular Roadmap
- Lingua principale
- TypeScript
- Stelle
- 180
- Fork
- 577
- Merge medio
- 2g 1h
- PR unite (30g)
- 100
Preparare l'ambiente
- Include un Dockerfile o un file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di DSpace/dspace-angular
-
accessibility affects: 10.x affects: main bug ux
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
DSpace/dspace-angular#6531 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
accessibility affects: 10.x affects: main bug help wanted
Difficoltà 2/5 1-3 ore Idoneità per principianti 66/100
DSpace/dspace-angular#6530 ·
I maintainer di solito rispondono entro 1 giorno
-
Submission Form Allows Deletion of All Repeating Item EntriesForse già presa @Rowan-McKereghan l’ha presa 5 giorni fa. Apertaaffects: 8.x affects: 9.x bug component: submission
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
DSpace/dspace-angular#6511 · 2 commenti · 1 assegnatario ·
I maintainer di solito rispondono entro 1 giorno
-
Visual issues with qualdrop fieldsForse già presa @DanGastardelli l’ha presa 15 giorni fa. Apertaaffects: 10.x affects: 9.x bug claimed: Acervos Digitais component: submission Difficulty: Low ux
Difficoltà 2/5 1-3 ore Idoneità per principianti 66/100
DSpace/dspace-angular#6412 · 3 commenti · 1 assegnatario ·
I maintainer di solito rispondono entro 1 giorno
-
Facet headings have incorrect clickable area to expand/collapseForse già presa @jesielviana l’ha presa 12 giorni fa. Apertaaccessibility affects: 10.x affects: 8.x affects: 9.x bug ux
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
DSpace/dspace-angular#6364 · 3 commenti · 1 assegnatario ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di DSpace/dspace-angular
Issue simili
-
bug parity
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
WenyuChiou/agent-board#1489 ·
I maintainer di solito rispondono entro 1 giorno
-
area: bazaar bug complexity: medium
Difficoltà 2/5 1-3 ore Idoneità per principianti 74/100
accensa/x402-facilitator-stellar#779 ·
I maintainer di solito rispondono entro 1 giorno
-
bug good first issue P4 size:S web-ui
Difficoltà 2/5 Mezza giornata Idoneità per principianti 85/100
josephfung/curia#2600 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
cloudflare/partykit#444 ·