Test parallelization in CI in Selenium Java - Framework Patterns

Framework Mode - Test parallelization in CI

Folder Structure

selenium-java-project/
├── src/
│   └── test/
│       └── java/
│           ├── pages/           # Page Object classes
│           ├── tests/           # Test classes
│           ├── utils/           # Utility classes (e.g., WebDriverFactory)
│           └── listeners/       # TestNG listeners for reporting
├── testng.xml                  # TestNG suite configuration for parallel runs
├── pom.xml                     # Maven build and dependency management
└── ci/
    └── Jenkinsfile             # CI pipeline script with parallel stages

Test Framework Layers

• Driver Layer: WebDriverFactory manages browser instances, supports thread-safe parallel execution.
• Page Objects: Encapsulate UI elements and actions for reusability and maintainability.
• Tests: Test classes using TestNG annotations, designed to run independently for parallel execution.
• Utilities: Helper classes for common functions like waits, logging, and data handling.
• Listeners: TestNG listeners capture test events and generate reports.
• Configuration: testng.xml defines parallel execution strategy and thread count.

Configuration Patterns

• testng.xml: Defines test suites and sets parallel="methods" or parallel="classes" with thread-count to enable parallel test execution.
• WebDriverFactory: Uses ThreadLocal<WebDriver> to provide isolated browser instances per thread.
• Environment Properties: Use property files or system variables to select environment (dev, staging, prod) and browser type.
• CI Pipeline: Jenkinsfile or similar config triggers tests with parallel stages or parallel test execution enabled.
• Credentials: Securely stored in environment variables or CI secrets, injected at runtime.

Test Reporting and CI/CD Integration

• TestNG Reports: Default HTML reports generated after test runs showing pass/fail status per test method.
• Allure or Extent Reports: Enhanced reporting with screenshots, logs, and history support.
• CI Integration: Jenkins or other CI tools run tests in parallel, collect reports, and mark build status accordingly.
• Parallel Logs: Use thread-safe logging to avoid mixed logs from parallel tests.
• Post-build Actions: Archive reports and send notifications (email, Slack) based on test results.

Best Practices for Test Parallelization in CI

1. Isolate Tests: Ensure tests do not share state or data to avoid flaky results when run in parallel.
2. Use ThreadLocal WebDriver: Provide separate browser instances per thread to prevent interference.
3. Configure Parallelism in testng.xml: Control parallel execution granularity and thread count carefully to balance speed and resource use.
4. Manage Test Data: Use unique or independent test data sets per test to avoid conflicts.
5. Integrate with CI Properly: Configure CI pipelines to run tests in parallel and collect reports reliably.

Self Check

Where in this folder structure would you add a new Page Object class for the Login page?

Key Result

Use TestNG with ThreadLocal WebDriver and testng.xml parallel settings to run Selenium Java tests in parallel within CI pipelines.

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