Jasmine vs NUnit
Feature checklists rarely decide anything. What decides it is the pricing metric, who has to write the tests, and which limitation you can live with.
Entry price
Free and open source
Open sourceFree and open source
Open sourceWhat drives the bill
The metric that actually scales your invoice.
Free and open source. You pay in engineering time and CI minutes.
Free and open source. You pay in engineering time and CI minutes.
Free tier
Everything, self-hosted
Everything, self-hosted
Open source
MIT
MIT
Self-hostable
No-code authoring
Languages
Platforms
Fits teams
Adoption
Established
OSS community · since 2010
Widely used
.NET Foundation · since 2002
Strengths
- Self-contained: spies, clocks and matchers with no extra packages.
- Runs directly in a browser without bundling.
- Extremely stable API — old suites keep working.
- The most expressive built-in assertion library in .NET.
- Familiar attribute model for teams migrating from older frameworks.
- Very stable, very long-lived.
Limitations
- Feels dated; snapshot testing and modern mocking are absent or bolted on.
- Momentum has moved to Jest and Vitest, including within the Angular ecosystem.
- Weaker TypeScript ergonomics than newer runners.
- Shared test-class instances mean state can leak between tests unless you are careful.
- New Microsoft templates default to xUnit, so it is drifting from the mainstream.
- Attribute-heavy style feels dated.
Best for
Existing Angular codebases and browser-native test setups.
Existing .NET codebases already standardised on NUnit.
All of these integrate with: Jenkins.
Pricing last reviewed August 2026 and is indicative only — confirm on each vendor’s own page.