Your First TestNG Test: Write and Run a TestNG Script

Writing The Code

On the eclipse window that you’re seeing now, write the following code. We are writing a code in order to verify the title of webpage.

CODE(self explanatory):

package newpack;

import org.openqa.selenium.WebDriver;
import org.openqa.selenium.chrome.ChromeDriver;
import org.testng.Assert;
import org.testng.annotations.Test;

public class NewTest {

    @Test
    public void firstTest() {
        // Selenium Manager downloads a matching ChromeDriver on the first run,
        // so there is no System.setProperty line and no driver path.
        WebDriver driver = new ChromeDriver();

        driver.get("https://www.testmuai.com/");

        // the assertion decides pass or fail; TestNG reports it
        String actualTitle = driver.getTitle();
        Assert.assertTrue(actualTitle.contains("TestMu"), "Unexpected title: " + actualTitle);

        driver.quit();
    }
}

After writing the code, save it and right click on ‘New Test.java’ → Run as→ TestNG Test.

Once you click on it, you’ll see a chrome browser window opening the website that you’ve entered in your code to test. And it will automatically close as soon as the test is completed and in the output section below, you’ll see ‘Test Passed’ as the status of your test on the console below.

With this, you have run your first automation test in TestNG using a local webdriver.

To verify the title of a given webpage matches the one already specified.

Austin Siewert

Co-Founder, Steadfast Systems

Discovered @TestMu AI yesterday. Best browser testing tool I've found for my use case. Great pricing model for the limited testing I do 👏

2M+ Devs and QAs rely on TestMu AI

Deliver immersive digital experiences with Next-Generation Mobile Apps and Cross Browser Testing Cloud

Sign up with googleSign up with Email

With TestNG certification, you can challenge your skills in performing automated testing with TestNG and take your career to the next level.

Here’s a short glimpse of the TestNG certification from TestMu AI:

Key Takeaway: A first TestNG script is one Java class that opens a browser in a @BeforeTest method, asserts a page title inside a @Test method, and quits the driver in @AfterTest.

How Do AI Agents Help You Write TestNG Scripts?

AI coding agents write the repetitive parts of a TestNG script: the class skeleton, the @BeforeTest driver setup, the @Test method and the assertion. You still supply the locators and review the output.

Three uses are worth knowing when you start writing TestNG code:

• Editor agents: GitHub Copilot and Cursor read an open Page Object class and generate the matching @Test method, including a @DataProvider signature, from a plain comment describing the scenario.
• Browser-connected agents: an agent wired to a browser through a Model Context Protocol server, such as Playwright MCP, opens the page, reads the live DOM, and returns real CSS or XPath locators instead of guessed ones.
• Failure triage: an agent parses the testng-results.xml file in the test-output folder, groups failing methods by stack trace, and reports which failures share one root cause.

The limits are specific. An agent that has never seen the live DOM invents locators that compile and then throw NoSuchElementException at runtime. Generated waits often default to Thread.sleep instead of WebDriverWait, which is the standard source of flaky Selenium tests.

Treat generated TestNG code as a first draft. Run it once, replace every invented locator with one read from the real page, then commit. The same review rule applies to a full AI agent to generate Selenium Java tests, and the broader shift is covered in our guide to AI in test automation.

Key Takeaway: AI agents generate TestNG class skeletons and annotations reliably, but locators produced without reading the live DOM fail at runtime and must be verified against the real page.

Running the Script on a Cloud Selenium Grid

A couple changes in your code is all that you would need for running your Selenium test script on TestMu AI Selenium grid. Here we will take a look at a different example to help you demonstrate the TestMu AI Selenium grid.

We will be running a script of a simple To Do list app. In this list, our code will be marking 2 items as done, add a list item and will display the total count of pending items. You can find the below code on our GitHub repository as well.

import org.openqa.selenium.By;
import org.openqa.selenium.Platform;
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.remote.DesiredCapabilities;
import org.openqa.selenium.remote.RemoteWebDriver;
import org.testng.Assert;
import org.testng.annotations.AfterClass;
import org.testng.annotations.BeforeClass;
import org.testng.annotations.Test;
import java.net.MalformedURLException;
import java.net.URL;
 
public class TestNGTodo{
     public String username = "YOUR_USERNAME";
    public String authkey = "YOUR_ACCESS_KEY";
    public static RemoteWebDriver driver = null;
    public String gridURL = "@hub.lambdatest.com/wd/hub";
    boolean status = false;
  
    @BeforeClass
    public void setUp() throws Exception {
       DesiredCapabilities capabilities = new DesiredCapabilities();
        capabilities.setCapability("browserName", "chrome");
        capabilities.setCapability("version", "70.0");
        capabilities.setCapability("platform", "win10"); // If this cap isn't specified, it will just get the any available one
        capabilities.setCapability("build", "LambdaTestSampleApp");
        capabilities.setCapability("name", "LambdaTestJavaSample");
        capabilities.setCapability("network", true); // To enable network logs
        capabilities.setCapability("visual", true); // To enable step by step screenshot
        capabilities.setCapability("video", true); // To enable video recording
        capabilities.setCapability("console", true); // To capture console logs
        try {
            driver = new RemoteWebDriver(new URL("https://" + username + ":" + authkey + gridURL), capabilities);
        } catch (MalformedURLException e) {
            System.out.println("Invalid grid URL");
        } catch (Exception e) {
            System.out.println(e.getMessage());
        }
    }
  
    @Test
    public void testSimple() throws Exception {
       try {
              //Change it to production page
            driver.get("https://4dvanceboy.github.io/lambdatest/lambdasampleapp.html");
             
              //Let's mark done first two items in the list.
              driver.findElement(By.name("li1")).click();
            driver.findElement(By.name("li2")).click();
             
             // Let's add an item in the list.
              driver.findElement(By.id("sampletodotext")).sendKeys("Yey, Let's add it to list");
            driver.findElement(By.id("addbutton")).click();
             
              // Let's check that the item we added is added in the list.
            String enteredText = driver.findElementByXPath("/html/body/div/div/div/ul/li[6]/span").getText();
            if (enteredText.equals("Yey, Let's add it to list")) {
                status = true;
            }
        } catch (Exception e) {
            System.out.println(e.getMessage());
        }
    }
  
    @AfterClass
    public void tearDown() throws Exception {
       if (driver != null) {
            ((JavascriptExecutor) driver).executeScript("lambda-status=" + status);
            driver.quit();
        }
    }
}

If you look at the configurations selected for running the test. They are our desired capabilities and the code provided for those capabilities is fetched from TestMu AI Capabilities Generator.

The button which says Copy to clipboard will help you to copy all the code based on your selections in just a single click.

That’s all you need for running your first automation test script using Selenium with TestNG at TestMu AI.

Key Takeaway: A single remote TestNG run needs one DesiredCapabilities object holding the browser name, browser version and platform, passed to RemoteWebDriver with the grid hub URL.

A Minimal TestNG Test with Selenium 4

The class below is the shortest useful TestNG test for a browser today. It opens a page in Chrome, checks the title, and closes the browser, using three annotations: @BeforeTest for setup, @Test for the check, and @AfterTest for teardown. Selenium 4 downloads a matching ChromeDriver on its own, so there is no driver setup code and no WebDriverManager dependency.

Add Selenium next to TestNG in pom.xml (org.seleniumhq.selenium:selenium-java:4.49.0 and org.testng:testng:7.12.0), then create this class under src/test/java:

package demoTestNG;

import org.openqa.selenium.WebDriver;
import org.openqa.selenium.chrome.ChromeDriver;
import org.testng.Assert;
import org.testng.annotations.AfterTest;
import org.testng.annotations.BeforeTest;
import org.testng.annotations.Test;

public class FirstTestNGScript {
    private WebDriver driver;

    @BeforeTest
    public void setUp() {
        driver = new ChromeDriver();
        driver.manage().window().maximize();
    }

    @Test
    public void homePageTitleContainsBrand() {
        driver.get("https://www.testmuai.com/");
        String title = driver.getTitle();
        Assert.assertTrue(title.contains("TestMu"), "Unexpected title: " + title);
    }

    @AfterTest
    public void tearDown() {
        if (driver != null) {
            driver.quit();
        }
    }
}

To run it through a suite file instead of the IDE, add testng.xml at the project root and run mvn test -Dsurefire.suiteXmlFiles=testng.xml:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE suite SYSTEM "https://testng.org/testng-1.0.dtd">
<suite name="FirstTestNGSuite">
    <test name="HomePageTest">
        <classes>
            <class name="demoTestNG.FirstTestNGScript" />
        </classes>
    </test>
</suite>

@BeforeTest runs once before the test methods inside the <test> tag and @AfterTest once after them; use @BeforeMethod instead when every test needs a fresh browser. The console prints a summary line with total, passed, failed, and skipped counts, and test-output/index.html holds the HTML report.