Testing Framework reviews from Reddit
Summary
We analyzed 170 Reddit reviews across 25 subreddits and 33 posts to rank the best Testing Framework brands recommended by redditors, including communities like r/java, r/typescript, r/node, r/embedded, r/QualityAssurance. Top-rated brands include Vitest (4.6/5), Jest (4.2/5), Cypress (4.4/5).
Stats
Reviews170
Subreddits25
Posts33
Brands87
Products22
170 reviews from
and
By Brand
/By Product
#1
Vitest
4.6
(14)
"Vitest"
"Try vitest with supertest if your project is ESM."
"Vitest works great even if you don't use Vite for the project it's in, fwiw."
"I second Vitest. It's everything Jest got right, and fixed a few pain points for me."
"Write a test 2. Run `vitest` There you go!"
"You can fix Jest by uninstalling it then installing Vitest. It just works."
"Just switch to Vitest, it works perfectly."
"Vitest is the standard one, it's a drop in replacement for Jest without all the setup headaches."
"Zero config, TypeScript out of the box, fast, just works."
"Just migrated to vitest which is great. Jest doesn't event work correctly when collecting coverage."
#2
Jest
4.2
(13)
"Jest is Best!"
"I was at Assert.js a couple of weeks ago and just about everyone was riding the jest train: easy setup, brilliant watch mode, built in coverage generation."
"Jest for unit tests. Jest + supertest for Node.js API/e2e tests. Jest + puppeteer for e2e browser tests."
"Jest + Supertest."
"I use a combination of jest or jasmine with supertest"
"I've used mocha a lot, and like it, but prefer jest for the built in mocking library and defaulting to parallelization."
"I love jest it can just be a little harder to set up than vitest for something like typescript in particular"
"It’s between Jest and Vitest at this point."
"Jest or jasmine... are u using typescript?"
"Jest is next best for me."
#3
Cypress
4.4
(7)
"We implemented Cypress using cucumber and it's the most stable set of automated UI tests."
"Cypress is a really nice solution depending on your requirements."
"Cypress. Really beautiful and good documentation."
"If you want something that covers Chrome and Firefox you can go for Cypress which is perfect and has really nice documentation."
"I use Cypress for e2e/functional UI tests and love it."
"I have used cypress and found it to be useful"
"Lacks cross browser support and cloud testing tools integration is awaited."
#4
Selenium
4.2
(6)
"Selenium is the oldest framework in the business and has maintained its popularity."
"I much prefer selenium over cypress or playwright."
"A very tried and true, classical approach is Selenium, with Java bindings."
"Selenium is a testing framework, you just need git repo to store your code."
"Selenium"
"We use Selenium to do integration tests of the full app."
#5
Unity
4.0
(6)
"Unity is great for the testing framework."
"Unity"
"Unity is great for quick and dirty projects."
"Quite happy with Unity."
"I like unity. We automate it using gitlab runners on our ci cd"
"I also like using Unity."
#6
Mocha
4.0
(6)
"I've used mocha a lot, and like it, but prefer jest for the built in mocking library and defaulting to parallelization."
"I’ve been using Mocha and Chai for assertion."
"I like mocha and chai, and a good test runner makes a big difference."
"Mocha + unexpected + mocha-webpack"
"Mocha + chai + sinon"
"I've only ever used mocha/chai/sinon but I feel like I hear more and more people moving to jest"
#7
Robot Framework
4.2
(5)
"Robot Framework has well maintained selenium/appium wrapper libraries."
"We are actually using Python+Robot Framework to build a testing system."
"For python probably robot framework, and for java you can look on selenide"
"I had experience with robot framework / Python. It was nice!"
"Robot framework"
#8
Playwright
4.8
(4)
"If you are testing a UI application write more integration tests using Playwright. It's great."
"Playwright"
"Playwright with Typescript is always the answer."
"Skip selenium and use playwright"
#9
NUnit
4.5
(4)
"NUnit is a great testing framework."
"NUnit has a clear pattern for setup stages that ensures tests are isolated."
"NUnit is great for unit tests."
"NUnit, xUnit, MsUnit, any of these would be good."
#10
XUnit
4.3
(4)
"XUnit is also a solid choice for testing."
"XUnit is also a solid choice for unit testing."
"I use MS test with visual studio."
"NUnit, xUnit, MsUnit, any of these would be good."
#11
Bun
4.7
(3)
"Super fast, like ridiculously so. Can run our thousand odd tests in under a second compared to about 10s for jest. No boilerplate or config."
"Buns test runner is insanely fast and no boilerplate needed"
"Consider switching to Bun. Probably won't be easy but it could save you a lot of time. Bun can run playwright too"
#12
JUnit
4.7
(3)
"Junit with jqwik for property based testing finds more bugs with less work!"
"JUnit is a good and universal tool for testing."
"How no one has mentioned junit and mockito is incredible."
#13
Detox
4.3
(3)
"Use detox. It’s basically industry standard for react-native."
"Detox is probably the way."
"I’d definetely seriously look into Detox if the developers are the ones writing tests."
#14
TestContainers
4.3
(3)
"Integration testing is so much easier with TC you can't afford to ignore it."
"You should investigate Testcontainers."
"I use testcontainers and cucumber for the integration and end2end testing."
#15
PHPUnit
4.0
(3)
"PHPUnit is really the best option out there, by far. Most well-organized open source projects maintain these unit tests, and the project is very well maintained."
"[PHPUnit](http://www.phpunit.de/)"
"PHPUnit is the de-facto unit-testing tool for PHP (for me it's too bloated and too verbose)."
#16
dbt
4.0
(3)
"...until we moved to dbt where the functionality exists natively."
"Dbt also supports SQL unit testing in its latest release."
"The most recent version (1.8 of the CLI) has implemented unit tests for SQL."
#17
JUnit 5
5.0
(2)
"Junit 5, you stay in the same language and also if you have a test that depends on junit 4 you can always use the vintage engine."
"Migrating to JUnit 5 seems to be the best long-term choice."
#18
Node
5.0
(2)
"Node test runner feels like a perfect match for your use case"
"We use node test runner and it's working great"
#19
Ceedling
4.5
(2)
"Ceedling"
"Ceedling simplifies the build process for testing."
#20
Gatling
4.5
(2)
"I can highly recommend Gatling for performance testing."
"Gatling is excellent for performance testing."
#21
GDUnit
4.5
(2)
"I use the GDUnit addon by Mike Schultze in all my projects and it works perfectly."
"It isn't perfect, but it works well enough for anything I've needed."
#22
Python
4.5
(2)
"Pytest is an excellent testing framework for Python."
"Doctest is great for testing interactive Python examples."
#23
GitHub
4.5
(2)
"There's a really straightforward single-header framework called CTest on GitHub, by bdvberg."
"AI tools out there that can help you immensely generating unit tests. some are AI Assistant like ghithub co-pilot or cursor, or even tabnine"
#24
CMocka
4.0
(2)
"I like using cmocka for unit tests."
"Quite happy with CMocka."
#25
RestAssured
4.0
(2)
"RestAssured is great for API testing."
"If you are trying to test your REST API, I used restassured in the past."
#26
Appium
4.0
(2)
"I personally would go with RF + Appium then."
"Appium is the closest to Selenium and is welcoming for beginners."
#27
JSSpec
3.5
(2)
"I like JSSpec. It's comprehensive and compatible, and I find that the "spec" terminology coaxes better test cases out of me."
"JSSpec, Qunit, or ScrewUnit"
#28
JSUnit
3.0
(2)
"[JsUnit] svn trunk. And subscribe to the mailing list for tips like getting it to work with Firefox 3."
"[JSUnit]. I just checked out QUnit and it looks pretty good too."
#29
Doctest
5.0
(1)
"Doctest and Catch2 are my bread and butter."
#30
Intuit
5.0
(1)
"The HTML report makes troubleshooting regressions easy by allowing comparison to previous requests/responses."
#31
Node.js
5.0
(1)
"Simplicity is king. Typescript friendly and no compiles."
#32
Wiremock
5.0
(1)
"Excellent tools for testing between microservices."
#33
Groovy
5.0
(1)
"Groovy simplifies the code of handling JSON and XML payload."
#34
FFF
5.0
(1)
"FFF is excellent for mocking and faking."
#35
Remote Dev Containers
5.0
(1)
"Remote Dev Containers make collaboration seamless."
#36
FakeItEasy
5.0
(1)
"FakeItEasy is excellent for mocking."
#37
FluentAssertions
5.0
(1)
"FluentAssertions makes assertions more readable."
#38
Microsoft.AspNetCore.TestHost
5.0
(1)
"Microsoft.AspNetCore.TestHost is useful for integration testing."
#39
Criterion
5.0
(1)
"I have been using Criterion on a recent project and enjoying it."
#40
Pytest
5.0
(1)
"You can't go wrong with Pytest – it's what almost everyone uses (or at least knows), and it's not hard to get into."
#41
Karate DSL
5.0
(1)
"Check out Karate DSL for an amazing experience!"
#42
Spring Framework
5.0
(1)
"Spring framework has very good documentation and examples of how to write tests."
#43
Mockito
5.0
(1)
"Mockito is a good and universal tool for testing."
#44
Cypress.io
5.0
(1)
"I love Cypress.io"
#45
MSTest
4.0
(1)
"I usually work with Mstest, but seen other frameworks in other projects."
#46
Spring Cloud Contract
4.0
(1)
"Check out Spring Cloud Contract."
#47
TestNG
4.0
(1)
"I would recommend TestNG or Junit5 with Selenium."
#48
CppUTest
4.0
(1)
"CppUTest fits the bill."
#49
CUnit
4.0
(1)
"We use CUnit at work."
#50
4.0
(1)
"The docs and examples are at least a bit better imho."
#51
SQLMesh
4.0
(1)
"SQLMesh supports SQL unit testing and can transpile SQL to DuckDB dialect."
#52
Google Test
4.0
(1)
"Google Test is pretty good, although it’s mainly used for C++."
#53
GTest
4.0
(1)
"GTest is ideal for more mature projects."
#54
embunit
4.0
(1)
"I have used embunit in the past, and it got the job done."
#55
Katalon
4.0
(1)
"I have used Katalon too, it's a good one."
#56
ACCELQ
4.0
(1)
"It has a simpler and more intuitive interface compared to Katalon."
#57
Spring
4.0
(1)
"Great for integration tests."
#58
Quarkus
4.0
(1)
"Works well for integration testing."
#59
Karate
4.0
(1)
"Karate is a solid choice for testing."
#60
Mockito Junit
4.0
(1)
"Mockito Junit is effective for unit and integration testing."
#61
H2
4.0
(1)
"H2 is a handy tool for database testing."
#62
Karate framework
4.0
(1)
"Debugging in Groovy code is much easier in IntelliJ."
#63
fast-check
4.0
(1)
"I get a lot of mileage out of fast-check, which I integrate with jest."
#64
WebdriverIO
4.0
(1)
"WebdriverIO"
#65
Bandit
4.0
(1)
"I'd recommend this one: https://github.com/offdev/bandit It's better than classic A/B testing."
#66
Jasmine
4.0
(1)
"I prefer Jasmine."
#67
SnapTest
4.0
(1)
"SnapTest really easy to use and has awesome webrunner"
#68
jQuery
4.0
(1)
"JQuery is great for DOM event testing since you can bind and trigger events symmetrically."
#69
ScrewUnit
4.0
(1)
"If you like BDD, ScrewUnit is VASTLY more powerful and convenient than JsSpec, the code is more extensible, the runner is much nicer."
#70
BugBug
4.0
(1)
"You can try BugBug.io if you want, we build a platform for web testing dedicated to SaaS."
#71
Prodmagic
4.0
(1)
"Have you checked out Prodmagic? It’s basically OpenAI’s Operator designed for repetitive tasks and testing with an AI."
#72
AssertJ
4.0
(1)
"You can't really go wrong with AssertJ + JUnit5."
#73
Spring Boot
4.0
(1)
"Makes JUnit5 simpler."
#74
Custom Testing Framework
4.0
(1)
"We have our own config driven testing framework where test logic is Inserted into a table..."
#75
QUnit
4.0
(1)
"I prefer QUnit, but then, I don't use mock objects or BDD; just plain simple tests."
#76
Great Expectations
4.0
(1)
"Maybe a library like Great Expectations can help you?"
#77
Native Test Runner
4.0
(1)
"Try the native test runner, it very likely comes with everything you need"
#78
PHPT
3.0
(1)
"Phpt of course: http://qa.php.net/write-test.php but you can also try out tinyspec"
#79
TinySpec
3.0
(1)
"You can also try out tinyspec: https://github.com/StanAngeloff/php-tinyspec"
#80
jQUnit
3.0
(1)
"Jqunit. It's not very well documented yet, but the example file should have all the info you need to get started."
#81
Spock
3.0
(1)
"The test framework doesn’t really matter, and I’ve yet to face an issue which can’t be solved in either Spock or JUnit."
#82
Behave
3.0
(1)
"You could use Behave (gherkin scenarios), but I have to warn you it gets tedious."
#83
SQLmesh
3.0
(1)
"Maybe SQLmesh can helpful, found it very interesting but never looked into it again..."
#84
Cucumber
2.0
(1)
"Cucumber can be heavy and cumbersome."
#85
Apple
2.0
(1)
"Appium is a huge PITA for iOS, consider using XCUITest instead."
#86
Topaz
2.0
(1)
"We've tried to use Topaz Total Test. Meh."
#87
Pact
2.0
(1)
"Pact lacks flexibility."
Discover your audience
GummySearch is an audience research toolkit for 130,000 unique communities on Reddit.
If you are looking for startup problems to solve, want to validate your idea or find your customers online, GummySearch is for you.
Sign up for free, get community insights in minutes.
Tell me more
Get started
