Why TestNG? From main() to Professional Testing

Up until now, you have been writing Selenium code inside a main() method. You launch a browser, do some actions, print "Test passed" or "Test failed" to the console, and move on. That works for learning, but it is not how real companies run thousands of tests every night.

Think of it like cooking. When you cook at home, you just start making whatever you want. No structure, no rules. But if you run a restaurant kitchen, you need stations, timings, checklists, and a system. TestNG is that system for your test automation.

What Is TestNG?

TestNG stands for "Test Next Generation." It is a Java testing framework inspired by JUnit and NUnit. In the Selenium world, TestNG is the industry standard. Over 80% of Java-based Selenium frameworks use TestNG. When interviewers ask about your framework, they expect to hear "TestNG."

What Problems Does TestNG Solve?

Without a framework, you are writing code like this:

public class NoFrameworkTest {
    public static void main(String[] args) {
        WebDriver driver = new ChromeDriver();
        driver.get("https://www.testerrank.com/banking");

        // Login test
        driver.findElement(By.id("username")).sendKeys("testuser");
        driver.findElement(By.id("password")).sendKeys("pass123");
        driver.findElement(By.cssSelector("button[type='submit']")).click();

        // Check if login worked... but how?
        if (driver.getCurrentUrl().contains("/dashboard")) {
            System.out.println("Login test PASSED");
        } else {
            System.out.println("Login test FAILED");
        }

        // What if the test crashes here? Browser stays open forever.
        // What about running 500 tests? All in one main()?
        // What about reports? Who reads console output?
        // What about running tests in parallel? Impossible with main().

        driver.quit();
    }
}

This approach has serious problems. There is no automatic cleanup if a test crashes. You cannot run tests independently — one failure can kill the whole suite. There are no reports, no grouping, no parallel execution, and no way to retry flaky tests. TestNG solves all of these.

What TestNG Gives You

• Annotations — Mark methods as tests, setup, or teardown. @BeforeMethod opens the browser, @Test runs the test, @AfterMethod closes the browser. Every test gets a fresh browser automatically.
• Assertions — Built-in methods to check actual vs expected. No more if-else with println.
• DataProviders — Run the same test with 50 different data sets. Write once, test many.
• Groups — Tag tests as "smoke" or "regression." Run only what you need.
• Parallel execution — Run 10 tests at the same time instead of one after another.
• testng.xml — One config file that controls your entire test suite.
• Listeners — Take screenshots on failure, retry flaky tests, generate custom reports.
• Reports — HTML reports generated automatically after every run.

TestNG vs JUnit — Quick Comparison

You will hear about JUnit in interviews. Here is the honest comparison: