How to Create TestNG.xml File in Eclipse

The Test Class Used in This Demo

The demo needs a TestNG project with one test class. If you do not have one yet, the TestNG project in Eclipse chapter walks through the Eclipse wizard, and the TestNG Maven dependency chapter covers the pom.xml route. The class below is what the testng.xml file will point at.

Write a Test

A new test class will be added as per the details provided in Step 2. You may notice the red marks in the test class. Hover the mouse over the error line, for example, on @Test annotation. Once the annotation is added, the errors will disappear.

• Make the necessary changes in the class, like updating the test method name and writing the code in the respective @Test, @Before, and @After annotations.
• To run the tests, right-click on the class name > Run As > TestNG Test.

The tests will be executed using TestNG, and the results will be shown in the console window at the bottom.

Subscribe to the TestMu AI YouTube Channel and stay updated with the latest video tutorials on Selenium Java.

Demo: How to Create a TestNG.xml File in Eclipse?

In the above section, we set up a TestNG.xml file and executed tests using TestNG. Now, let’s look at how to create a TestNG.xml file in Eclipse.

There are two methods to create a TestNG.xml file:

Method 1:

• Right-click on the project folder, and towards the bottom of the list, select TestNG and then Convert to TestNG.

• A screen like the one below would appear. Click on Next.

• The next window that pops up will have the refactored source code after you click Finish.

• A new addition to your project directory will be displayed, named as testng.xml.

• Double-click on testng.xml to open the XML file, which looks like the one below.

Method 2:

• Right-click on New, and select File.

• Enter the following file name testng.xml, and then click on Finish.

This is what a basic TestNG.xml file looks like.

You have your very first TestNG.xml file ready. Now you know how to create a TestNG.xml file in Eclipse. Let’s leverage this TestNG.xml file to run automated tests using automation testing tools like Selenium. If you want to dig further and explore the true capabilities of Selenium, check out this guide on what is Selenium.

Running a TestNG.xml File

The hierarchy of an XML file goes like this- first <suite> tag, second <test> tag, and lastly, <classes> tag. You can give any name to the <suite> and <test> tags, but you have to be careful while naming classes since it combines the package and test name.

Since the suite is the topmost hierarchy, this is where multiple test classes can be placed. Let’s understand with the help of an example. For the test scenarios below, we have created two Java classes wherein both tests will run on the TestMu AI eCommerce Playground website.

Test Scenario 1:

• Check the title of the TestMu AI eCommerce Playground website.

Test Scenario 2:

• Start by searching for the product iphone from the home page.
• Verify that the search results page correctly displays the title Search – iphone to ensure you are on the right page.

Implementation:

The following code will help implement test scenarios 1 and 2. The EcommercePlayGroundTests class has both test methods to implement the test scenarios.

There are two additional methods in the class. The first one is the setup() method, which will run before any test runs and help set up the WebDriver and start the Chrome browser. The second tearDown() method will gracefully close the WebDriver session.

In case you want to know more about WebDriver, you can go through this tutorial on what is Selenium WebDriver.

public class EcommercePlaygroundTests {
   private WebDriver driver;
  
   @BeforeTest
   public void setup() {
       driver = new ChromeDriver();
       driver.manage().window().maximize();
       driver.manage().timeouts().implicitlyWait(Duration.ofSeconds(20));
   }


   @Test
   public void testCheckTitle() {
       driver.get("https://ecommerce-playground.lambdatest.io/");
       final String title = driver.getTitle();
       assertEquals(title, "Your Store");
   }

   @Test
   public void testSearchForProduct() {
       driver.get("https://ecommerce-playground.lambdatest.io/");
       WebElement searchBox = driver.findElement(By.name("search"));
       searchBox.sendKeys("iphone");

       WebElement searchBtn = driver.findElement(By.cssSelector("button.type-text"));
       searchBtn.click();

       String pageTitle = driver.findElement(By.cssSelector("#product-search h1")).getText();
       assertEquals(pageTitle, "Search - iphone");
   }

   @AfterTest
   public void tearDown() {
       driver.quit();
   }

}

The testCheckTitle() method will implement the Test Scenario 1, whereas the testSearchForProduct() method will implement the Test Scenario 2.

Test Execution:

Let’s create the TestNG.xml file with the name testng-demo.xml and update both test method names to execute the tests.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd">
<suite name="Testng.xml demo">
   <test name="LambdaTest e-commerce playground tests" parallel =”methods”>
       <classes>
           <class name="io.github.mfaisalkhatri.testngxmldemo.EcommercePlaygroundTests">
               <methods>
                   <include name="testCheckTitle"/>
                   <include name="testSearchForProduct"/>
               </methods>
           </class>
       </classes>
   </test>
</suite>

In the TestNG.xml file above, there are 2 test methods that have the <include> tag and belong to the EcommercePlaygroundTests class. When this file is executed, both tests will run in parallel in the order in which they are updated.

First, the testCheckTitle() method will run, next the testSearchForProduct() method will be run. To run the tests methods in parallel, we need to update the parallel = “methods” tag in the <test> tagline.

To run the project using the XML file, right-click on the testng.xml file and select Run As > TestNG Suite.

This will execute and run both of the tests using testng.xml with a simple click. Following is the test execution result displayed in the console.

Parallel Testing Using TestNG.xml File

Now that you have executed your TestNG.xml file successfully. As mentioned earlier, this file helps running tests in parallel. So, it is important to note the changes you need to make in the TestNG.xml to perform automation testing. However, configuring hundreds of browsers and operating systems in your nodes doesn’t look feasible enough.

Instead, you can leverage a cloud grid offered by TestMu AI. It is an AI-powered test orchestration and execution platform that lets developers and testers perform Selenium automation testing with TestNG on over 3000+ real browsers and operating systems online. That way, you only need to focus on writing better Selenium automation scripts without worrying about test infrastructure needs.

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

Let’s use the same test scenario we implemented in the earlier section of the blog, where we searched for a product on the TestMu AI eCommerce Playground website. Earlier, we ran the tests on the local Chrome browser.

Test Scenario:

• Start by searching for the product iphone from the home page.
• Verify that the search results page correctly displays the title Search – iphone to ensure you are on the right page.

Implementation:

A new test class, Base.java, has been created to take care of all the configurations related to running tests on the TestMu AI cloud grid. It will also take care of starting and closing the browsers.

The values for the browser name, version, and platform name will be provided on runtime using the testng.xml file.

The setup() method will update the browser, its version, and platform name as the values are set using the @Parameters annotation in TestNG.

public class Base {

   RemoteWebDriver driver;
   String status = "failed";

   @BeforeTest
   @Parameters({"browser", "browserVersion", "platform"})
   public void setup(String browser, String browserVersion, String platform) {
       final String userName = System.getenv("LT_USERNAME") == null ? "LT_USERNAME" : System.getenv("LT_USERNAME");
       final String accessKey = System.getenv("LT_ACCESS_KEY") == null ? "LT_ACCESS_KEY" : System.getenv("LT_ACCESS_KEY");
       final String gridUrl = "@hub.lambdatest.com/wd/hub";

       if (browser.equalsIgnoreCase("chrome")) {
           try {
               this.driver = new RemoteWebDriver(new URL("http://" + userName + ":" + accessKey + gridUrl), getChromOptions(browser, browserVersion, platform));

           } catch (final MalformedURLException e) {
               System.out.println("Could not start the chrome browser on LambdaTest cloud grid");
           }
       } else if (browser.equalsIgnoreCase("firefox")) {
           try {
               this.driver = new RemoteWebDriver(new URL("http://" + userName + ":" + accessKey + gridUrl), getFirefoxOptions(browser, browserVersion, platform));

           } catch (final MalformedURLException e) {
               System.out.println("Could not start the firefox browser on LambdaTest cloud grid");
           }
       }

       this.driver.manage().timeouts().implicitlyWait(Duration.ofSeconds(20));
   }

   private ChromeOptions getChromOptions(String browser, String browserVersion, String platform) {
       var browserOptions = new ChromeOptions();
       browserOptions.setPlatformName(platform);
       browserOptions.setBrowserVersion(browserVersion);
       browserOptions.setCapability("LT:Options", getLtOptions());

       return browserOptions;
   }

   private FirefoxOptions getFirefoxOptions(String browser, String browserVersion, String platform) {
       var browserOptions = new FirefoxOptions();
       browserOptions.setPlatformName(platform);
       browserOptions.setBrowserVersion(browserVersion);
       browserOptions.setCapability("LT:Options", getLtOptions());

       return browserOptions;
   }

   private HashMap<String, Object> getLtOptions() {
       final var ltOptions = new HashMap<String, Object>();
       ltOptions.put("project", "Selenium ECommerce playground website");
       ltOptions.put("build", "LambdaTest Ecommerce Website tests");
       ltOptions.put("name", "Search for a product test");
       ltOptions.put("w3c", true);
       ltOptions.put("visual", true);
       ltOptions.put("w3c", true);
       ltOptions.put("plugin", "java-testNG");
       return ltOptions;
   }

   @AfterTest
   public void tearDown() {
       this.driver.executeScript("lambda-status=" + this.status);
       this.driver.quit();
   }

}

The capabilities required for configuration can be set using the TestMu AI Automation Capabilities Generator.

Code Walkthrough:

The getLtOptions() method will set the required capabilities in the test scripts.

Next, a new test class ECommercePlaygroundTestsOnCloud, has been created to implement the test scenario and extend the Base class.

public class ECommercePlaygroundTestsOnCloud extends Base{

   @Test
   public void testSearchForProduct() {
       driver.get("https://ecommerce-playground.lambdatest.io/");
       WebElement searchBox = driver.findElement(By.name("search"));
       searchBox.sendKeys("iphone");

       WebElement searchBtn = driver.findElement(By.cssSelector("button.type-text"));
       searchBtn.click();

       String pageTitle = driver.findElement(By.cssSelector("#product-search h1")).getText();
       assertEquals(pageTitle, "Search - iphone");

       status = "passed";
   }
}

The testSearchForProduct() method will search for the product iphone from the website’s home page. After loading the search page, it will check that the page title equals Search- iphone.

If everything works fine, the status variable will be updated to passed.

Test Execution:

Let’s create a new TestNG.xml file and name it as testng-parallel.xml. That will help to perform Selenium testing on two different browsers and platforms in parallel.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd">
<suite name="Testng.xml demo" parallel="tests">
   <test name="LambdaTest e-commerce playground tests on Windows 10 - Chrome">
       <parameter name="browser" value="chrome"/>
       <parameter name="browserVersion" value="125"/>
       <parameter name="platform" value="Windows 10"/>
       <classes>
           <class name="io.github.mfaisalkhatri.testngxmldemo.ECommercePlaygroundTestsOnCloud">
               <methods>
                   <include name="testSearchForProduct"/>
               </methods>
           </class>
       </classes>
   </test>
   <test name="LambdaTest e-commerce playground tests on macOS Sonoma - Firefox">
       <parameter name="browser" value="firefox"/>
       <parameter name="browserVersion" value="126"/>
       <parameter name="platform" value="macOS Sonoma"/>
       <classes>
           <class name="io.github.mfaisalkhatri.testngxmldemo.ECommercePlaygroundTestsOnCloud">
               <methods>
                   <include name="testSearchForProduct"/>
               </methods>
           </class>
       </classes>
   </test>
</suite>

The parallel = “tests” will execute both tests in parallel.

The details of the test execution can be found on the TestMu AI Web Automation Dashboard.