Jest vs PHPUnit
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
BSD-3-Clause
Self-hostable
No-code authoring
Languages
Platforms
Fits teams
Adoption
Category standard
OpenJS Foundation · since 2014
Category standard
Sebastian Bergmann · since 2004
Strengths
- Everything in one dependency, with defaults that work for most projects on day one.
- The largest ecosystem of matchers, reporters and framework presets in JavaScript.
- Snapshot testing is genuinely useful for serialisable output when used with restraint.
- Universal in PHP — every framework builds on it.
- Mature mocking, data providers and coverage integration.
- Well documented and extremely stable.
Limitations
- Native ESM support remains awkward, and the Babel transform layer is a recurring configuration tax.
- Noticeably slower than Vitest on large suites.
- jsdom is not a browser; subtle DOM and CSS behaviour differs from reality.
- Major versions drop older PHP releases aggressively, forcing upgrade work.
- Verbose compared to newer wrappers such as Pest.
- Coverage requires an extension, which slows runs significantly.
Best for
Existing JavaScript codebases, React Native, and teams that value ecosystem depth over raw speed.
Every PHP project, directly or through a wrapper.
All of these integrate with: GitHub Actions, SonarQube.
Pricing last reviewed August 2026 and is indicative only — confirm on each vendor’s own page.