Test parallelization in CI in Selenium Java

Introduction

Test parallelization helps run many tests at the same time. This makes testing faster and saves time in Continuous Integration (CI).

You want to check many parts of a website quickly after code changes.

Your test suite is large and takes too long to finish.

You want to get fast feedback from your CI system.

You have multiple browsers or devices to test at once.

You want to use your computer or cloud resources efficiently.

Syntax

Selenium Java

public class TestClass {
    @Test
    public void testMethod() {
        // test steps here
    }
}

// In TestNG XML:
<suite name="Suite" parallel="tests" thread-count="3">
    <test name="Test1">
        <classes>
            <class name="TestClass" />
        </classes>
    </test>
    <test name="Test2">
        <classes>
            <class name="TestClass" />
        </classes>
    </test>
</suite>

Use TestNG XML file to configure parallel tests in CI.

Set parallel attribute to tests, methods, or classes depending on your need.

Examples

This runs two test classes in parallel as separate tests.

Selenium Java

<suite name="Suite" parallel="tests" thread-count="2">
    <test name="Test1">
        <classes>
            <class name="TestClass1" />
        </classes>
    </test>
    <test name="Test2">
        <classes>
            <class name="TestClass2" />
        </classes>
    </test>
</suite>

This runs test methods inside one class in parallel.

Selenium Java

<suite name="Suite" parallel="methods" thread-count="3">
    <test name="Test">
        <classes>
            <class name="TestClass" />
        </classes>
    </test>
</suite>

Sample Program

This test class runs two tests in parallel using TestNG. Each test opens a browser, checks a search engine title, and closes the browser.

Selenium Java

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

public class ParallelTest {
    private ThreadLocal<WebDriver> driver = new ThreadLocal<WebDriver>();

    @BeforeMethod
    public void setup() {
        driver.set(new ChromeDriver());
    }

    @Test
    public void testGoogle() {
        driver.get().get("https://www.google.com");
        Assert.assertTrue(driver.get().getTitle().contains("Google"));
        System.out.println("Google test passed");
    }

    @Test
    public void testBing() {
        driver.get().get("https://www.bing.com");
        Assert.assertTrue(driver.get().getTitle().contains("Bing"));
        System.out.println("Bing test passed");
    }

    @AfterMethod
    public void teardown() {
        if (driver.get() != null) {
            driver.get().quit();
        }
        driver.remove();
    }
}

// TestNG XML configuration:
// <suite name="Suite" parallel="methods" thread-count="2">
//     <test name="ParallelTests">
//         <classes>
//             <class name="ParallelTest" />
//         </classes>
//     </test>
// </suite>

Important Notes

Make sure your tests do not share data or browser instances when running in parallel.

Configure your CI tool (like Jenkins or GitHub Actions) to run tests with the TestNG XML file.

Use thread-safe WebDriver instances to avoid conflicts.

Summary

Test parallelization runs tests at the same time to save time.

Use TestNG XML to set parallel execution and thread count.

Ensure tests are independent to avoid errors when running in parallel.

Practice

1. What is the main benefit of running tests in parallel in a CI environment?

easy

A. It increases the number of test cases by duplicating them.

B. It ensures tests run in a specific order to avoid failures.

C. It reduces the total test execution time by running tests simultaneously.

D. It disables tests that are flaky to improve stability.

Solution

1. Step 1: Understand parallel test execution

   Parallel execution means running multiple tests at the same time instead of one after another.

2. Step 2: Identify the benefit in CI

   Running tests simultaneously saves time, making the feedback faster in continuous integration.

3. Final Answer:

   It reduces the total test execution time by running tests simultaneously. -> Option C

4. Quick Check:

   Parallel tests = faster execution [OK]

Hint: Parallel tests run together to save time [OK]

Common Mistakes:

• Thinking parallel means tests run in order
• Believing parallel increases test count
• Assuming parallel disables flaky tests

2. Which TestNG XML attribute correctly enables parallel test execution?

easy

A.

B.

C.

D.

Solution

1. Step 1: Recall TestNG XML syntax for parallelism

   The correct attribute to enable parallel execution is 'parallel' with values like 'methods', 'tests', or 'classes'.

2. Step 2: Identify correct thread count attribute

   The attribute 'thread-count' sets how many threads run in parallel.

3. Final Answer:

   <suite parallel="methods" thread-count="4"> -> Option B

4. Quick Check:

   parallel + thread-count = correct syntax [OK]

Hint: Use parallel and thread-count attributes in TestNG XML [OK]

Common Mistakes:

• Using non-existent attributes like runParallel
• Confusing thread-count with threads
• Using order="sequential" disables parallelism

3. Given this TestNG XML snippet, what is the maximum number of tests running at the same time?

<suite name="Suite" parallel="tests" thread-count="3">
  <test name="Test1">...</test>
  <test name="Test2">...</test>
  <test name="Test3">...</test>
  <test name="Test4">...</test>
</suite>

medium

A. 3 tests run simultaneously

B. 4 tests run simultaneously

C. 1 test runs at a time

D. 2 tests run simultaneously

Solution

1. Step 1: Understand parallel="tests" meaning

   Setting parallel="tests" means TestNG runs multiple <test> tags at the same time.

2. Step 2: Check thread-count value

   thread-count="3" limits the number of simultaneous threads to 3, so max 3 tests run together.

3. Final Answer:

   3 tests run simultaneously -> Option A

4. Quick Check:

   parallel=tests + thread-count=3 means 3 parallel tests [OK]

Hint: thread-count limits max parallel tests [OK]

Common Mistakes:

• Assuming all tests run at once ignoring thread-count
• Confusing parallel="methods" with parallel="tests"
• Thinking thread-count is ignored

4. You configured TestNG with parallel="methods" and thread-count="2". Your tests share a static WebDriver instance. What problem will most likely occur?

medium

A. Tests will fail due to WebDriver conflicts from shared instance.

B. Tests will run faster without any issues.

C. Tests will run sequentially ignoring parallel settings.

D. Tests will create multiple WebDriver instances automatically.

Solution

1. Step 1: Understand parallel methods with shared static WebDriver

   Parallel methods run at the same time, but sharing a static WebDriver means all tests use the same browser instance.

2. Step 2: Identify concurrency issues

   Sharing one WebDriver causes conflicts like commands overlapping, leading to test failures.

3. Final Answer:

   Tests will fail due to WebDriver conflicts from shared instance. -> Option A

4. Quick Check:

   Shared static WebDriver + parallel = conflicts [OK]

Hint: Avoid shared static WebDriver in parallel tests [OK]

Common Mistakes:

• Assuming shared WebDriver works fine in parallel
• Thinking parallel disables shared resource conflicts
• Believing TestNG creates separate WebDriver automatically

5. You want to run your Selenium tests in parallel in CI using TestNG. Your suite has 5 test classes, each with 3 test methods. You want to run all methods in parallel but limit total threads to 6. Which TestNG XML configuration is correct?

hard

A.

B.

C.

D.

Solution

1. Step 1: Identify parallel="methods" for running all test methods in parallel

   To run all methods in parallel, use parallel="methods" in the suite tag.

2. Step 2: Set thread-count="6" to limit total threads

   thread-count="6" limits the number of simultaneous threads to 6, matching the requirement.

3. Step 3: Confirm classes are inside a single <test> tag

   All classes are grouped under one <test> tag, so methods from all classes run in parallel within the thread limit.

4. Final Answer:

   <suite parallel="methods" thread-count="6"> -> Option D

5. Quick Check:

   parallel="methods" + thread-count="6" + single <test> [OK]

Hint: Use parallel="methods" with thread-count to control concurrency [OK]

Common Mistakes:

• Using parallel="classes" runs classes in parallel, not methods
• Using thread-count too high ignores limit
• Splitting classes into multiple tests changes parallel behavior