Test suites (testng.xml) in Selenium Java - Build an Automation Script

Run multiple test classes using TestNG suite XML

Preconditions (3)

Step 1: Create a testng.xml file that includes both LoginTest and SearchTest classes

Step 2: Run the testng.xml suite file using TestNG

Step 3: Observe that both test classes run in the order defined in the XML

Step 4: Verify that all tests in both classes pass

✅ Expected Result: Both LoginTest and SearchTest classes run successfully when executing the testng.xml suite file, and all tests pass.

Automation Requirements - TestNG with Selenium WebDriver

Assertions Needed:

Verify that tests in LoginTest pass

Verify that tests in SearchTest pass

Best Practices:

Use descriptive testng.xml with clear suite and test names

Use fully qualified class names in testng.xml

Keep test classes independent

Use TestNG annotations properly

Run suite via TestNG runner

Automated Solution

Selenium Java

package tests;

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

public class LoginTest {
    WebDriver driver;

    @BeforeClass
    public void setup() {
        driver = new ChromeDriver();
        driver.get("https://example.com/login");
    }

    @Test
    public void testValidLogin() {
        driver.findElement(By.id("email")).sendKeys("[e-mail]");
        driver.findElement(By.id("password")).sendKeys("Password123");
        driver.findElement(By.id("loginButton")).click();
        String currentUrl = driver.getCurrentUrl();
        Assert.assertTrue(currentUrl.contains("dashboard"), "User should be redirected to dashboard");
    }

    @AfterClass
    public void teardown() {
        driver.quit();
    }
}

package tests;

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

public class SearchTest {
    WebDriver driver;

    @BeforeClass
    public void setup() {
        driver = new ChromeDriver();
        driver.get("https://example.com");
    }

    @Test
    public void testSearchFunctionality() {
        driver.findElement(By.id("searchBox")).sendKeys("Selenium");
        driver.findElement(By.id("searchButton")).click();
        String resultsText = driver.findElement(By.id("results")).getText();
        Assert.assertTrue(resultsText.contains("Selenium"), "Search results should contain 'Selenium'");
    }

    @AfterClass
    public void teardown() {
        driver.quit();
    }
}

/* testng.xml file content */

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE suite SYSTEM "https://testng.org/testng-1.0.dtd">
<suite name="ExampleSuite">
    <test name="LoginAndSearchTests">
        <classes>
            <class name="tests.LoginTest"/>
            <class name="tests.SearchTest"/>
        </classes>
    </test>
</suite>

The solution includes two test classes: LoginTest and SearchTest. Each class uses Selenium WebDriver to open a browser and perform actions on the web page.

Each test class has a @BeforeClass method to set up the browser and navigate to the starting URL, a @Test method to perform the test and assert expected behavior, and an @AfterClass method to close the browser.

The testng.xml file defines a suite named ExampleSuite with one test named LoginAndSearchTests. It includes both test classes by their fully qualified names.

Running the testng.xml file with TestNG will execute both test classes in the order listed, verifying that all tests pass.

Common Mistakes - 4 Pitfalls

Using relative class names without package in testng.xml

Not closing the browser in @AfterClass

Running test classes individually instead of via testng.xml suite

Hardcoding URLs or test data inside test methods without flexibility

Bonus Challenge

Now add data-driven testing to LoginTest with 3 different sets of valid credentials

Show Hint

Practice

1. What is the main purpose of the testng.xml file in Selenium testing?

easy

A. To write the Selenium WebDriver code

B. To store test data like usernames and passwords

C. To group and organize test classes and methods to run together

D. To generate HTML reports after test execution

Solution

1. Step 1: Understand the role of testng.xml

   The testng.xml file is used to define which tests to run and how to organize them.

2. Step 2: Identify the main purpose

   It groups test classes and methods so they can be run together as a suite.

3. Final Answer:

   To group and organize test classes and methods to run together -> Option C

4. Quick Check:

   Test suite grouping = To group and organize test classes and methods to run together [OK]

Hint: Remember: testng.xml organizes tests to run as a group [OK]

Common Mistakes:

• Confusing testng.xml with test code files
• Thinking testng.xml stores test data
• Assuming testng.xml generates reports

2. Which of the following is the correct way to define a test suite in testng.xml?

easy

A.

B.

C.

D.

Solution

1. Step 1: Recall the correct XML structure for TestNG suites

   The root element is <suite>, inside it we define <test>, then <classes> and <class>.

2. Step 2: Match the options with correct structure

   correctly follows this order and syntax.

3. Final Answer:

   <suite name="MySuite"><test name="Test1"><classes><class name="TestClass"/></classes></test></suite> -> Option A

4. Quick Check:

   Suite > Test > Classes > Class = [OK]

Hint: Remember XML order: suite > test > classes > class [OK]

Common Mistakes:

• Swapping <suite> and <test> tags
• Placing <class> directly under <suite>
• Using wrong tag names or attributes

3. Given the following testng.xml snippet, what tests will run?

<suite name="Suite1" parallel="tests" thread-count="2">
  <test name="TestA">
    <classes>
      <class name="tests.LoginTest"/>
    </classes>
  </test>
  <test name="TestB">
    <classes>
      <class name="tests.PaymentTest"/>
    </classes>
  </test>
</suite>

medium

A. No tests run due to missing methods tag

B. Both LoginTest and PaymentTest run in parallel as separate tests

C. Tests run sequentially, LoginTest then PaymentTest

D. Only LoginTest runs because it is first

Solution

1. Step 1: Analyze the parallel attribute in <suite>

   The attribute parallel="tests" means each <test> runs in parallel threads.

2. Step 2: Identify the tests defined

   There are two tests: TestA with LoginTest class and TestB with PaymentTest class.

3. Final Answer:

   Both LoginTest and PaymentTest run in parallel as separate tests -> Option B

4. Quick Check:

   parallel="tests" runs tests simultaneously = Both LoginTest and PaymentTest run in parallel as separate tests [OK]

Hint: parallel="tests" runs each <test> in parallel [OK]

Common Mistakes:

• Assuming tests run sequentially despite parallel attribute
• Thinking <methods> tag is mandatory to run tests
• Confusing parallel="tests" with parallel="classes"

4. You have this testng.xml file but tests are not running:

<suite name="Suite1">
  <test name="Test1">
    <class name="TestClass">
    </class>
  </test>
</suite>

What is the likely problem?

medium

A. The <suite> tag must include thread-count

B. The <test> tag is missing the parallel attribute

C. The class name must include the package name

D. The <class> tag should be self-closing or empty, not with separate open and close tags

Solution

1. Step 1: Check the <class> tag syntax

   In TestNG XML, <class> should be self-closing like <class name="TestClass"/> or empty without content.

2. Step 2: Identify the error in the given XML

   The given XML uses separate open and close tags for <class> which is invalid and causes tests not to run.

3. Final Answer:

   The <class> tag should be self-closing or empty, not with separate open and close tags -> Option D

4. Quick Check:

   Use self-closing <class> tag = The <class> tag should be self-closing or empty, not with separate open and close tags [OK]

Hint: Use self-closing tag in testng.xml [OK]

Common Mistakes:

• Adding parallel attribute thinking it fixes syntax
• Forgetting package name but that doesn't stop tests
• Assuming thread-count is mandatory

5. You want to run two test classes LoginTest and PaymentTest in parallel but limit total threads to 1 in testng.xml. Which configuration achieves this?

hard

A.

B.

C.

D.

Solution

1. Step 1: Understand parallel and thread-count attributes

   Setting parallel="classes" runs test classes in parallel, and thread-count="1" limits to one thread, so classes run one at a time.

2. Step 2: Check options for matching configuration

   sets parallel to classes and thread-count to 1, matching the requirement.

3. Final Answer:

   Option A configuration runs classes in parallel but limits threads to 1 -> Option A

4. Quick Check:

   parallel="classes" + thread-count=1 = [OK]

Hint: parallel="classes" with thread-count=1 runs classes sequentially [OK]

Common Mistakes:

• Using parallel="tests" with thread-count > 1 runs multiple threads
• Omitting parallel attribute runs tests sequentially
• Confusing parallel="methods" with classes