Test parallelization in CI in Selenium Java - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use test parallelization in CI?

Which of the following is the main benefit of running Selenium tests in parallel during Continuous Integration (CI)?

A It ensures tests run only on the latest browser version.

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

C It guarantees that tests will never fail due to timing issues.

D It automatically fixes flaky tests by retrying them.

💡 Hint

Think about how running multiple tests at the same time affects the overall testing process duration.

Parallelization allows multiple tests to run at once, which speeds up the total testing time. Other options describe benefits that are not guaranteed by parallelization.

❓ Predict Output

intermediate

Output of parallel test execution setup in TestNG

Given the following TestNG XML configuration snippet for parallel test execution, what will be the total number of threads used?

Selenium Java

<suite name="ParallelSuite" parallel="tests" thread-count="3">
  <test name="Test1">
    <classes>
      <class name="tests.LoginTest"/>
    </classes>
  </test>
  <test name="Test2">
    <classes>
      <class name="tests.SearchTest"/>
    </classes>
  </test>
  <test name="Test3">
    <classes>
      <class name="tests.CartTest"/>
    </classes>
  </test>
</suite>

A 6 threads, 2 per test class

B 1 thread, tests run sequentially

C 3 threads, one for each test

D 9 threads, 3 per test class

💡 Hint

Look at the 'parallel' attribute and 'thread-count' in the suite tag.

Setting parallel="tests" with thread-count="3" means TestNG will run up to 3 tests in parallel, one thread per test.

🔧 Debug

advanced

Identify the cause of flaky tests in parallel Selenium runs

In a Selenium test suite running in parallel on CI, tests intermittently fail with 'ElementNotInteractableException'. What is the most likely cause?

A Tests share the same WebDriver instance causing interference.

B The test code uses explicit waits properly.

C The browser version is outdated and incompatible.

D The CI server has insufficient disk space.

💡 Hint

Consider what happens if multiple tests try to control the same browser session at once.

Sharing a single WebDriver instance across parallel tests causes conflicts and flaky failures. Each test should have its own WebDriver instance.

❓ assertion

advanced

Correct assertion for verifying parallel test completion

Which assertion correctly verifies that all parallel Selenium tests have completed successfully in a CI environment?

Selenium Java

List<TestResult> results = testExecutor.getAllResults();
// Choose the correct assertion below

A assertNull(results);

B assertEquals(results.size(), 0);

C assertFalse(results.stream().anyMatch(r -> r.isSuccess()));

D assertTrue(results.stream().allMatch(r -> r.isSuccess()));

💡 Hint

Think about how to check that every test result indicates success.

Option D checks that all test results are successful. Other options check for empty or null results, which are incorrect.

❓ framework

expert

Best practice for thread-safe WebDriver in parallel tests

In a Selenium Java framework running tests in parallel on CI, which approach ensures thread-safe WebDriver usage?

A Use ThreadLocal<WebDriver> to store a separate WebDriver instance per thread.

B Create a single static WebDriver instance shared by all tests.

C Instantiate WebDriver once in a @BeforeClass method for all tests.

D Use a global WebDriver variable without synchronization.

💡 Hint

Consider how to isolate WebDriver instances per test thread safely.

ThreadLocal allows each thread to have its own WebDriver instance, preventing conflicts in parallel runs. Sharing a static or global instance causes interference.

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