Parallel execution configuration in Selenium Java

Introduction

Parallel execution lets you run multiple tests at the same time. This saves time and helps find problems faster.

You want to test your website on different browsers at once.

You have many test cases and want to finish testing quickly.

You want to check how your app works when many users use it simultaneously.

You want to use your computer's full power to run tests faster.

Syntax

Selenium Java

In TestNG XML file:

<suite name="SuiteName" parallel="tests" thread-count="3">
  <test name="Test1">
    <classes>
      <class name="com.example.TestClass1"/>
    </classes>
  </test>
  <test name="Test2">
    <classes>
      <class name="com.example.TestClass2"/>
    </classes>
  </test>
  <test name="Test3">
    <classes>
      <class name="com.example.TestClass3"/>
    </classes>
  </test>
</suite>

The parallel attribute can be set to tests, classes, or methods to control what runs in parallel.

The thread-count sets how many threads (tests) run at the same time.

Examples

This runs two tests in parallel, each test can have multiple classes.

Selenium Java

<suite name="Suite" parallel="tests" thread-count="2">
  <test name="TestA">
    <classes>
      <class name="com.example.TestA"/>
    </classes>
  </test>
  <test name="TestB">
    <classes>
      <class name="com.example.TestB"/>
    </classes>
  </test>
</suite>

This runs three classes in parallel inside one test.

Selenium Java

<suite name="Suite" parallel="classes" thread-count="3">
  <test name="Test">
    <classes>
      <class name="com.example.Test1"/>
      <class name="com.example.Test2"/>
      <class name="com.example.Test3"/>
    </classes>
  </test>
</suite>

This runs test methods inside one class in parallel.

Selenium Java

<suite name="Suite" parallel="methods" thread-count="4">
  <test name="Test">
    <classes>
      <class name="com.example.TestClass"/>
    </classes>
  </test>
</suite>

Sample Program

This Java test class uses TestNG to run two tests in parallel if configured in the TestNG XML file with parallel="methods" and thread-count="2". Each test opens a browser, checks the page title, and prints a success message.

Selenium Java

package com.example;

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

public class ParallelTest {
    WebDriver driver;

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

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

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

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

Important Notes

Make sure your tests do not share data that can cause conflicts when running in parallel.

Use thread-safe WebDriver instances to avoid errors.

Configure your TestNG XML file correctly to enable parallel execution.

Summary

Parallel execution runs tests at the same time to save time.

Set parallel and thread-count in TestNG XML to control parallelism.

Write tests that can run independently without sharing data.

Practice

1. What is the main purpose of configuring parallel execution in Selenium with TestNG?

easy

A. To run multiple tests at the same time and save execution time

B. To run tests one after another in a fixed order

C. To increase the number of test cases manually

D. To disable test execution temporarily

Solution

1. Step 1: Understand parallel execution concept

   Parallel execution means running tests simultaneously instead of sequentially.

2. Step 2: Identify the benefit of parallel execution

   Running tests at the same time saves overall test execution time.

3. Final Answer:

   To run multiple tests at the same time and save execution time -> Option A

4. Quick Check:

   Parallel execution = run tests simultaneously [OK]

Hint: Parallel means running tests together to save time [OK]

Common Mistakes:

• Thinking parallel means running tests one by one
• Confusing parallel execution with increasing test count
• Assuming parallel disables tests

2. Which XML attribute correctly sets the number of threads for parallel execution in TestNG?

easy

A. thread-count

B. parallel-count

C. max-threads

D. execution-threads

Solution

1. Step 1: Recall TestNG XML attributes for parallelism

   TestNG uses thread-count to specify how many threads run tests in parallel.

2. Step 2: Verify other options are incorrect

   Attributes like parallel-count, max-threads, and execution-threads are not valid TestNG attributes.

3. Final Answer:

   thread-count -> Option A

4. Quick Check:

   Thread count = number of parallel threads [OK]

Hint: Use thread-count to set parallel threads in TestNG XML [OK]

Common Mistakes:

• Using wrong attribute names like parallel-count
• Confusing thread-count with parallel attribute
• Misspelling thread-count

3. Given this TestNG XML snippet, how many tests will run in parallel?

<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. All 4 tests run in parallel

B. 3 tests run in parallel, 1 waits

C. Only 1 test runs at a time

D. 2 tests run in parallel, 2 wait

Solution

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

   parallel="tests" means tests run in parallel. thread-count="3" limits max parallel threads to 3.

2. Step 2: Apply thread-count to number of tests

   There are 4 tests but only 3 threads, so 3 tests run simultaneously and 1 waits.

3. Final Answer:

   3 tests run in parallel, 1 waits -> Option B

4. Quick Check:

   thread-count limits parallel tests to 3 [OK]

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

Common Mistakes:

• Assuming all tests run parallel ignoring thread-count
• Confusing parallel="tests" with parallel="methods"
• Ignoring that thread-count caps parallelism

4. You configured parallel="methods" and thread-count="2" in TestNG XML, but tests still run sequentially. What is the likely cause?

medium

A. TestNG does not support parallel execution

B. thread-count must be set to 1 for parallel methods

C. Test methods share state and are not thread-safe

D. parallel attribute should be set to "tests" for methods

Solution

1. Step 1: Understand parallel methods and thread safety

   parallel="methods" runs test methods in parallel only if they are thread-safe and independent.

2. Step 2: Identify cause of sequential execution

   If tests share data or state, TestNG runs them sequentially to avoid conflicts.

3. Final Answer:

   Test methods share state and are not thread-safe -> Option C

4. Quick Check:

   Shared state blocks parallel method execution [OK]

Hint: Ensure test methods are independent for parallel execution [OK]

Common Mistakes:

• Setting thread-count to 1 disables parallelism
• Using wrong parallel attribute value
• Believing TestNG lacks parallel support

5. You want to run test classes in parallel but ensure each class uses its own WebDriver instance to avoid conflicts. Which TestNG XML configuration is best?

hard

A. <suite name="Suite" parallel="instances" thread-count="4">

B. <suite name="Suite" parallel="tests" thread-count="4">

C. <suite name="Suite" parallel="methods" thread-count="4">

D. <suite name="Suite" parallel="classes" thread-count="4">

Solution

1. Step 1: Understand parallel modes in TestNG

   parallel="classes" runs test classes in parallel, isolating each class's WebDriver instance.

2. Step 2: Match requirement to configuration

   Running classes in parallel with thread-count=4 allows 4 classes to run simultaneously, each with its own driver.

3. Final Answer:

   <suite name="Suite" parallel="classes" thread-count="4"> -> Option D

4. Quick Check:

   parallel="classes" isolates WebDriver per class [OK]

Hint: Use parallel="classes" for separate WebDriver per class [OK]

Common Mistakes:

• Using parallel="methods" causing shared driver issues
• Choosing parallel="tests" which runs test tags, not classes
• Using parallel="instances" which is less common and may confuse