We use Jest, and I've been pretty happy with it overall. I'm not so deep into this type of work any more, but every time I need something I find it easy enough to follow along with what I'm seeing in the files and/or find useful docs and guides.
I still remember reading your post on the DEVs tech stack and I was impressed seeing all the pieces working together so well 😉
Jest has proven itself as a solid framework, with lots of devs trusting it.
According to npmtrends:
We've since simplified the tech stack a little bit, but yes we have had a focus on maintaining a good test suite and having the tools that support stability as much as we can.
The tests take long enough to run that developers don't run them every time they make a change to the system under test (SUT). They wait until the next coffee break or other interrupt before running them. Or, whenever they run the tests they walk around and chat with other team members (or play Doom or surf the Internet or ...)
i.e. your test runner shouldn't be part of the problem - that's why uvu exists.
I use tape for most purposes. Simple, lightweight, works as well today as it did years and years ago. It's also very similar to Rust's built-in test runner, so when I move between languages the context switch is that much lighter.
I also personally dislike the bdd test style (thus I wouldn't use a framework that only provides that option, assuming the choice is mine). Not for any technical reasons that actually matter, just personal taste. So much noise for the same results.
We use React on our frontend, so Jest and Enzyme are our preferred JS testing frameworks. Since these are quite popular, there are also a lot of great resources out there on using them, and Jest is even recommended in React's docs.
Software engineer @avec_alan (opinions mine) | ex @Shopify | Tool Maker
| #SoftwareCraftsman
| C & Test lover
| Web Metamodernist
| Author of PicoTest, Colibri and Seaborg
For unit tests my favorite combo is Mocha/Chai, plus Sinon if I need mocks (though it's rarely the case for unit testing). For dev E2E I'm a big fan of CodeceptJS, far superior to Cypress IMHO.
Open-source developer with 15+ years of experience, active Polish Wikipedia editor, mentor, and official Wikimedia Polska trainer. Lead creator of the WikiZEIT project and photographer.
Tech Lead/Team Lead. Senior WebDev.
Intermediate Grade on Computer Systems-
High Grade on Web Application Development-
MBA (+Marketing+HHRR).
Studied a bit of law, economics and design
Location
Spain
Education
Higher Level Education Certificate on Web Application Development
Thanks for the valuable insight 💯👍✨
We use Jest, and I've been pretty happy with it overall. I'm not so deep into this type of work any more, but every time I need something I find it easy enough to follow along with what I'm seeing in the files and/or find useful docs and guides.
I still remember reading your post on the DEVs tech stack and I was impressed seeing all the pieces working together so well 😉
Jest has proven itself as a solid framework, with lots of devs trusting it.
According to npmtrends:
We've since simplified the tech stack a little bit, but yes we have had a focus on maintaining a good test suite and having the tools that support stability as much as we can.
Slow Tests
i.e. your test runner shouldn't be part of the problem - that's why uvu exists.
This is insightful, thanks 👍😉
I use tape for most purposes. Simple, lightweight, works as well today as it did years and years ago. It's also very similar to Rust's built-in test runner, so when I move between languages the context switch is that much lighter.
I also personally dislike the bdd test style (thus I wouldn't use a framework that only provides that option, assuming the choice is mine). Not for any technical reasons that actually matter, just personal taste. So much noise for the same results.
Thanks for the input 👍😉
We use React on our frontend, so Jest and Enzyme are our preferred JS testing frameworks. Since these are quite popular, there are also a lot of great resources out there on using them, and Jest is even recommended in React's docs.
Jest for now, though I'm building my own!
I try to build my own
<everything>. I'm building my own framework, my own ghost, my own programming language, etc.Awesome to hear, best of luck in you projects 👍😉
For unit tests my favorite combo is Mocha/Chai, plus Sinon if I need mocks (though it's rarely the case for unit testing). For dev E2E I'm a big fan of CodeceptJS, far superior to Cypress IMHO.
Thanks for the insight 🙏❤
ava is the one I like the most. Very similar to tape but adds some convenient features.
Thanks for the input 🙏❤
I use Jest and Ava, Ava was the only framework that allow async tests loading, so it was the only option for my Scheme interpreter.
Thanks for the input 🙏❤
The QA dept. 😂😂😂
Haha, made my day 😄😄
Jest, Enzyme, React Testing Library and Cypress.
Thanks for the input 🙏❤
Cypress. But only for frontend testing (integration testing is awesome), jest for backend, nodejs testing.
Oh, yeah, heard about that too 😉👍