TestNG


TestNG is a testing framework for the Java programming language created by Cédric Beust and inspired by JUnit and NUnit. The design goal of TestNG is to cover a wider range of test categories: unit, functional, end-to-end, integration, etc., with more powerful and easy-to-use functionalities.

Features

TestNG's main features include:
  1. Annotation support.
  2. Support for data-driven/parameterized testing.
  3. Support for multiple instances of the same test class
  4. Flexible execution model. TestNG can be run either by Ant via build.xml, or by an IDE plugin with visual results. There isn't a TestSuite class, while test suites, groups and tests selected to run are defined and configured by XML files.
  5. Concurrent testing: run tests in arbitrarily big thread pools with various policies available, and test whether the code is multithread safe.
  6. Embeds BeanShell for further flexibility.
  7. Default JDK functions for runtime and logging.
  8. Dependent methods for application server testing.
  9. Distributed testing: allows distribution of tests on slave machines.

    Data Provider

A data provider in TestNG is a method in a test class, which provides an array of varied actual values to dependent test methods.
Example:

//This method will provide data to any test method that declares that its Data Provider is named "provider1".
@DataProvider
public Object createData1
// This test method declares that its data should be supplied by the Data Provider named "provider1".
@Test
public void verifyData1
// A data provider which returns an iterator of parameter arrays.
@DataProvider
public Iterator createData
// A data provider with an argument of the type java.lang.reflect.Method.
// It is particularly useful when several test methods use the same
// provider and you want it to return different values depending on
// which test method it is serving.
@DataProvider
public Object createData

The returned type of a data provider can be one of the following two types:
  • An array of array of objects where the first dimension's size is the number of times the test method will be invoked and the second dimension size contains an array of objects that must be compatible with the parameter types of the test method.
  • An Iterator. The only difference with Object is that an Iterator lets you create your test data lazily. TestNG will invoke the iterator and then the test method with the parameters returned by this iterator one by one. This is particularly useful if you have a lot of parameter sets to pass to the method and you don't want to create all of them upfront.

    Tool Support

    TestNG is supported, out-of-the-box or via plug-ins, by each of the three major Java IDEs - Eclipse, IntelliJ IDEA, and NetBeans. It also comes with a custom task for Apache Ant and is supported by the Maven build system. The Hudson continuous integration server has built-in support for TestNG and is able to track and chart test results over time. Most Java code coverage tools, such as Cobertura, work seamlessly with TestNG.


    Note: TestNG support for Eclipse is only embedded in the Eclipse Marketplace for Eclipse versions up to 2018-09. For later versions of Eclipse, TestNG must be manually installed as per instructions in the TestNG site.

    Reporting

    TestNG generates test reports in HTML and XML formats. The XML output can be transformed by the Ant JUnitReport task to generate reports similar to those obtained when using JUnit. Since version 4.6, TestNG also provides a reporter API that permits third-party report generators, such as ReportNG,
    PDFngreport and TestNG-XSLT, to be used.

    Comparison with JUnit

    The differences between and respective advantages of the two seemingly competing Java tools, TestNG and JUnit, have been debated throughout the decade. Both camps have strong grounds and supporters. Stackoverflow discussions reflect this controversy.

    Annotations

    In JUnit 4, the @BeforeClass and @AfterClass methods have to be declared as static. TestNG does not have this constraint.
    TestNG has provided four additional setup/teardown pairs for the suite, test and groups, i.e. @BeforeSuite, @AfterSuite, @BeforeTest, @AfterTest, @BeforeGroup and @AfterGroup, @BeforeMethod and @AfterMethod.
    TestNG provide wide range of support to automate application using selenium.

    Parameterized testing

    is implemented in both tools, but in quite different ways.
    TestNG has two ways for providing varying parameter values to a test method: by setting the testng.xml, and by defining a @DataProvider method.
    In JUnit 4, @RunWith and @Parameters are used together to facilitate parameterized tests, while the @Parameters method has to return List with all the actual values, which will be fed into a dedicated class constructor as an argument. In JUnit5 there is also the @ParameterizedTest annotation, which lets allows for the creation of a parameterized testing function.

    Conclusion

    JUnit is often shipped with mainstream IDEs by default, which contributes to its wider popularity. However, TestNG's goal is much wider, which includes not only unit testing, but also support of integration and acceptance testing, etc. Which one is better or more suitable depends on use contexts and requirements.
    OWIKI.org. Text is available under the Creative Commons Attribution-ShareAlike License.