Parallel execution configuration in Selenium Java - Framework Patterns

Framework Mode - Parallel execution configuration

Folder Structure for Selenium Java Framework with Parallel Execution

src/
├── main/
│   └── java/
│       └── com/example/project/
│           ├── pages/           # Page Object classes
│           ├── utils/           # Utility classes (e.g., WebDriverFactory, WaitHelpers)
│           └── config/          # Configuration classes
└── test/
    └── java/
        └── com/example/project/tests/  # Test classes
resources/
├── testng.xml               # TestNG suite configuration for parallel execution
├── config.properties        # Environment and browser settings
└── log4j2.xml               # Logging configuration

Test Framework Layers

• Driver Layer: WebDriverFactory manages browser drivers and supports parallel sessions.
• Page Objects: Classes representing web pages with methods to interact with UI elements.
• Test Layer: Test classes using TestNG annotations to define test methods and suites.
• Utilities: Helper classes for waits, logging, data reading, and thread-safe WebDriver management.
• Configuration: Properties files and classes to manage environment variables, browser types, and parallel settings.

Configuration Patterns for Parallel Execution

• TestNG XML: Use parallel="methods" or parallel="tests" with thread-count to run tests in parallel.
• Thread-safe WebDriver: Use ThreadLocal<WebDriver> to ensure each thread has its own WebDriver instance.
• Properties File: Store environment URLs, browser types, and credentials in config.properties.
• WebDriverFactory: Create WebDriver instances based on browser type and manage lifecycle per thread.
• Test Listeners: Implement listeners to handle setup and teardown for parallel tests.

<!-- Example snippet from testng.xml -->
<suite name="ParallelSuite" parallel="methods" thread-count="4">
    <test name="ChromeTests">
        <classes>
            <class name="com.example.project.tests.LoginTest"/>
        </classes>
    </test>
</suite>

Test Reporting and CI/CD Integration

• TestNG Reports: Built-in HTML and XML reports generated after test execution.
• Allure Reporting: Integrate Allure for detailed, user-friendly reports with screenshots and logs.
• CI/CD Integration: Configure Jenkins/GitHub Actions to run tests in parallel using Maven commands and publish reports.
• Logs: Use thread-safe logging (e.g., Log4j2) to capture logs per test thread.
• Artifacts: Store test reports and logs as build artifacts for review.

Best Practices for Parallel Execution Framework

1. Use ThreadLocal WebDriver: Prevent WebDriver conflicts by isolating driver instances per thread.
2. Keep Tests Independent: Avoid shared state or dependencies between tests to ensure reliable parallel runs.
3. Limit Thread Count: Set thread count based on machine resources to avoid overload.
4. Use Explicit Waits: Avoid flaky tests by waiting for elements properly instead of fixed delays.
5. Clean Up Properly: Quit WebDriver instances in @AfterMethod to free resources after each test.

Self Check

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

Key Result

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

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