Jasmine vs pytest
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
Category standard
pytest-dev · since 2004
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.
- Fixtures are the best dependency-injection model in any test framework, and they compose cleanly.
- Assertion introspection produces genuinely useful failure output from a plain assert.
- Vast plugin ecosystem — pytest-xdist, pytest-cov, pytest-asyncio, pytest-django.
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.
- Fixture scope and ordering become genuinely hard to reason about in large suites.
- The magic that makes simple cases elegant makes complex cases opaque.
- Python only.
Best for
Existing Angular codebases and browser-native test setups.
Essentially every Python project.
All of these integrate with: Jenkins.
Pricing last reviewed August 2026 and is indicative only — confirm on each vendor’s own page.