TestNG alternatives and similar libraries
Based on the "Testing" category.
Alternatively, view TestNG alternatives based on common mentions on social networks and blogs.
-
-
-
-
Apache JMeter
Apache JMeter open-source load testing tool for analyzing and measuring the performance of a variety of services -
TestContainers
Testcontainers is a Java library that supports JUnit tests, providing lightweight, throwaway instances of common databases, Selenium web browsers, or anything else that can run in a Docker container. -
-
-
-
-
MockServer
MockServer enables easy mocking of any system you integrate with via HTTP or HTTPS with clients written in Java, JavaScript and Ruby. MockServer also includes a proxy that introspects all proxied traffic including encrypted SSL traffic and supports Port Forwarding, Web Proxying (i.e. HTTP proxy), HTTPS Tunneling Proxying (using HTTP CONNECT) and SOCKS Proxying (i.e. dynamic port forwarding). -
PowerMock
PowerMock is a Java framework that allows you to unit test code normally regarded as untestable. -
-
-
-
-
-
-
-
Pact JVM
JVM version of Pact. Enables consumer driven contract testing, providing a mock service and DSL for the consumer project, and interaction playback and verification for the service provider project. -
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Scott Test Reporter
Never debug a test again: Detailed failure reports and hassle free assertions for Java tests - Power Asserts for Java -
pojo-tester
Java testing framework for testing pojo methods. It tests equals, hashCode, toString, getters, setters, constructors and whatever you report in issues ;) -
InfluxDB - Power Real-Time Data Analytics at Scale
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of TestNG or a related project?
README
Documentation available at TestNG's main web site.
Release Notes
Need help?
Before opening a new issue, did you ask your question on
If you posted on both sites, please provide the link to the other question to avoid duplicating the answer.
Are you sure it is a TestNG bug?
Before posting the issue, try to reproduce the issue in a shell window.
If the problem does not exist with the shell, first check if the issue exists on the bugtracker of the runner, and open an issue there first:
- Eclipse :Issues Page
- IntelliJ:Issues Page
- Maven :Issues Page
- Gradle :Issues Page
Which version are you using?
Always make sure your issue is happening on the latest TestNG version. Bug reports occurring on older versions will not be looked at quickly.
Have you considered sending a pull request instead of filing an issue?
The best way to report a bug is to provide the TestNG team with a full test case reproducing the issue.
Maybe you can write a runnable test case (check the src/test/ folder for examples) and propose it in a pull request
Don't worry if the CI fails because it is the expected behavior.
This pull request will be a perfect start to find the fix :)
How to create a pull request?
Refer our [Contributing](.github/CONTRIBUTING.md) section for detailed set of steps.
We encourage pull requests that:
- Add new features to TestNG (or)
- Fix bugs in TestNG
If your pull request involves fixing SonarQube issues then we would suggest that you please discuss this with the TestNG-dev before you spend time working on it.
*Note that all licence references and agreements mentioned in the TestNG README section above
are relevant to that project's source code only.