Vitest
Hacker ApprovedRanked 3 of 8 testing frameworks by recommenders
Fast, Jest-compatible test runner built on Vite that people adopt for new projects; the common caveat is trouble with mocks and debugging.
Fast, Jest-compatible test runner built on Vite that people adopt for new projects; the common caveat is trouble with mocks and debugging.
25 people gave an opinion
- recommend it
- 17
- criticize it
- 8
- approval share
- 68%
Recommended in 8 of 13 months
- November 2025: recommended
- December 2025: recommended
- January 2026: not recommended
- February 2026: recommended
- March 2026: recommended
- April 2026: not recommended
- May 2026: recommended
- June 2026: recommended
- July 2026: recommended
- August 2026: not recommended
- September 2026: recommended
- October 2026: not recommended
- November 2026: not recommended (month in progress)
Why it carries the badge
- 17 people recommend itNeeds 10 or more, met.
- 2.1 recommenders for every criticNeeds 2 to 1 or better, met.
- Recommended in 8 of 13 monthsNeeds 4 or more, met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Jest-compatible test runner on Vite
“it's a jest-compatible runner integrated to Vite”
Comment from 2 Jul 2026 in “Vite+ Beta” “jest -> vitest (works with vite)”
Comment from 2 Jul 2026 in “Vite+ Beta” Default choice for new projects
“I love Vite, Vitest, Oxlint and Oxfmt and look in their direction for most of my new projects!”
Comment from 2 Jul 2026 in “Vite+ Beta” “my default choice for new projects”
Comment from 27 Jun 2026 in “Jest/Vitest interactive course (runs in the browser)” Part of the Vite toolchain
“I love Vite, Vitest, Oxlint and Oxfmt and look in their direction for most of my new projects!”
Comment from 2 Jul 2026 in “Vite+ Beta” “Sure beats opening some ancient project and seeing some mix of Vite, Vitest, Oxlint and Oxfmt”
Comment from 2 Jul 2026 in “Vite+ Beta” “VoidZero's tools are all world-class”
Comment from 4 Jun 2026 in “VoidZero Is Joining Cloudflare” Browser mode for testing
“Upgrading to vitest with browser mode can solve these problems”
Comment from 20 Feb 2026 in “Web Components: The Framework-Free Renaissance” “yes, i've used vitest browser mode to test canvas operations”
Comment from 30 Dec 2025 in “Vitest Browser Mode Guide”
What people warn about
Each mark is one comment
Mocks cause trouble and misuse
“i have had a lot of trouble with vitest mocks for postgres and redis so far”
Comment from 4 Jan 2026 in “Ask HN: What's the future of software testing and QA?” “far too easy to call mock() in JS (with Jest/Vitest)”
Comment from 27 Jun 2026 in “Jest/Vitest interactive course (runs in the browser)” Hard to debug or isolate
“it's a pain to just "detach" for a specific frame and run that test in isolation”
Comment from 30 Dec 2025 in “Vitest Browser Mode Guide” “Nearly impossible to set breakpoints (they disappear in refresh)”
Comment from 30 Dec 2025 in “Vitest Browser Mode Guide”
Other testing frameworks people recommend
The four most recommended other testing frameworks, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
| Product | Recommend | Criticize | Approval | Months | Owned | Badge |
|---|---|---|---|---|---|---|
| Mockito | 19 | 13 | 59% | 3 | 4 yrs4 owners | — |
| cargo-nextest | 18 | 1 | 95% | 3 | — | — |
| VitestThis page | 17 | 8 | 68% | 8 | — | Approved |
| Testcontainers | 14 | 3 | 82% | 8 | — | Approved |
| pytest | 12 | 5 | 71% | 9 | — | Approved |
What people said
25 of the 29 comments that mention it, newest first. Each links to the original comment.
“vitest and object lifecycle crap”
“would be a nice performance win”
“The mere enumeration shows how bad it is.”
“jest -> vitest (works with vite)”
“It is pretty sweet with that setup.”
“However vitest is still great!”
“it's 1.5-2x slower than Jest”
“it's a jest-compatible runner integrated to Vite”
“an ultra fast test runner”
“the jank levels seem to generally be decreasing with every next attempt to get things right”
“Sure beats opening some ancient project and seeing some mix of Vite, Vitest, Oxlint and Oxfmt”
“I love Vite, Vitest, Oxlint and Oxfmt and look in their direction for most of my new projects!”
“far too easy to call mock() in JS (with Jest/Vitest)”
“my default choice for new projects”
“Vitest is a brilliant software”
“VoidZero's tools are all world-class”
“Coincided with test bugs so I moved to vitest completely.”
“over-complicated nature of both Jest and Vitest”
“Instead of sending adding Vitest to the backlog graveyard, I had it integrated and running in one or two evenings”
“Upgrading to vitest with browser mode can solve these problems”
“Vitest configs act as quality gates.”
“i have had a lot of trouble with vitest mocks for postgres and redis so far”
“Nearly impossible to set breakpoints (they disappear in refresh)”
“yes, i've used vitest browser mode to test canvas operations”
“it's a pain to just "detach" for a specific frame and run that test in isolation”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.