What's your favorite JS testing framework?

Nowadays, the industry is dominated by agile development and tight deadlines. Manual unit testing can be complex and time-consuming, so it makes sense to rely on automated frameworks.

Some of the favorites include: Jest, Mocha, Jasmine, Karma.

Do you unit test your code and what's your favorite testing framework?

Comments

[Madza]

Thanks for the valuable insight 💯👍✨

[Ben Halpern]

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.

[Madza]

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:

[Ben Halpern]

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.

[peerreynders]

Slow Tests

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.

• Fixing a Test Hourglass
• TotT

[Madza]

This is insightful, thanks 👍😉

[Mage]

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.

[Full Name]

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.

[Madza]

Thanks for the input 👍😉

[Siddharth]

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.

[Madza]

Awesome to hear, best of luck in you projects 👍😉

[Frédéric Bonnet]

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.

[Madza]

Thanks for the insight 🙏❤

[Jakub T. Jankiewicz]

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.

[Madza]

Thanks for the input 🙏❤

[Andrew Baisden]

Jest, Enzyme, React Testing Library and Cypress.

[Madza]

Thanks for the input 🙏❤

[Michael Knopke]

Cypress. But only for frontend testing (integration testing is awesome), jest for backend, nodejs testing.

[Madza]

Oh, yeah, heard about that too 😉👍