Showing posts from December, 2007

TestNG versus JUnit4

Comparing JUnit 4 and TestNG 5.7

Excerpts from by Andy Glover.

JUnit is geared more towards unit testing - testing an object class in isolation.
TestNG provides more features and flexibility to facilitate its use not only for unit but integration, regression, functional, acceptance testings etc.

1. The setup method (annotated with @BeforeClass) needs to static and public with JUnit 4 but thats not required by TestNG. Thus TestNG is more flexible of the two.

2. Dependency testing:
Unlike JUnit, TestNG welcomes test dependencies through the dependsOnMethods attribute of the Test annotation. With this handy feature, you can easily specify dependent methods, which will execute before a desired method. What's more, if the dependent method fails, then all subsequent tests will be skipped, not marked as failed.

In JUnit 4, you can specify test orders using fixtures but if one test A fails then a test B that depends on test A will also b…

TestNG - java testing framework

Recently i got introduced to TestNG (version 5.7) at work. I was familiar to JUnit from the past and i kind of knew about the existance of TestNG and that it had improvements over JUnit but i never thought that it will gain so much traction that i will be made to use it soon. Here are some of the features:
JDK 5 Annotations (JDK 1.4 is also supported with JavaDoc annotations). Flexible test configuration - using multiple testng XML configuration files one per test suite. Support for data-driven testing (with @DataProvider).Support for parameters - you can pass parameters to test methods from the testng.xml file.
Allows distribution of tests on slave machines - support for parallel execution of tests and methods.
Powerful execution model (no more TestSuite) - test classes are annotated POJOs and don't have to extend any class or implement interface to have test methods. Supported by a variety of tools and plug-ins (Eclipse, IDEA, Ant, Maven, etc...).�������…