8 engineers on Hacker News describe using Jest first-hand: 1 endorse it, 5 regret it, 0 are mixed.
“We switched from Jest to Vitest this summer as part of the effort to migrate a large node repository to ESM. Jest presented a lot of issues after switching to ESM.”
regret · production · britches11 · 2024-11-26 · source ↗ · wrong label?“almost invariably come to regret some of the choices that I, or our team, have made (which include... React, Gatsby, Flow, Stylus, Enzyme, Jest, SCSS”
regret · production · just_a_username · 2022-12-15 · source ↗ · wrong label?“I almost invariably come to regret some of the choices that I, or our team, have made (which include... React, Gatsby, Flow, Stylus, Enzyme, Jest, SCSS”
regret · production · azangru · 2022-12-06 · source ↗ · wrong label?“We ditched all JEST's snapshots statements in our code-base, because of code-coverage abuse and false sense of "being safe"”
regret · production · drinchev · 2020-06-25 · source ↗ · wrong label?“I've been using it for almost 2 years now through some of the rougher patches in its development”
endorse · production · 2 yr · b34r · 2016-12-08 · source ↗ · wrong label?“It was also really really slow when I tried it last year but I guess (hope?) it's better now”
regret · personal · Keats · 2016-08-31 · source ↗ · wrong label?“I tend to write tons of integration tests using Jest and they add up to a noticeable amount of time when running in CI.”
neutral · production · gpsmsn · 2021-12-27 · source ↗ · wrong label?“We ended up going with React/Jest/Puppeteer”
neutral · production · howdydoo · 2019-09-27 · source ↗ · wrong label?