Parallel test configuration in JUnit - Framework Patterns

Framework Mode - Parallel test configuration

Folder Structure

project-root/
├── src/
│   ├── main/
│   │   └── java/
│   │       └── com/example/app/       # Application source code
│   └── test/
│       └── java/
│           └── com/example/tests/     # Test classes
│               ├── pages/              # Page Object classes
│               ├── utils/              # Utility classes (e.g., WebDriverFactory)
│               └── parallel/           # Parallel test configuration classes
├── resources/
│   └── test.properties                 # Test configuration files
├── pom.xml                            # Maven build file with dependencies and plugins
└── junit-platform.properties          # JUnit 5 configuration file for parallel execution
    

Test Framework Layers

• Driver Layer: WebDriver setup and management, often via a factory class to create thread-safe driver instances.
• Page Objects: Classes representing UI pages with methods to interact with elements, promoting reuse and maintainability.
• Test Classes: JUnit test classes containing test methods annotated with @Test, designed to run independently.
• Parallel Configuration: JUnit 5 configuration files and annotations that enable and control parallel test execution.
• Utilities: Helper classes for common tasks like reading config, logging, and synchronization.
• Configuration Files: Properties files and JUnit platform config files to manage environment variables, browser types, and parallelism settings.

Configuration Patterns

To enable parallel test execution in JUnit 5, use the junit-platform.properties file with settings like:

junit.jupiter.execution.parallel.enabled = true
junit.jupiter.execution.parallel.mode.default = concurrent
junit.jupiter.execution.parallel.config.strategy = fixed
junit.jupiter.execution.parallel.config.fixed.parallelism = 4
    

Use pom.xml to include dependencies and configure Surefire or Failsafe plugins to run tests in parallel during build.

Manage environment variables and browser types via test.properties or system properties, accessed in tests or driver factory.

Test Reporting and CI/CD Integration

• Use Maven Surefire or Failsafe plugin reports to get XML and HTML test reports after parallel runs.
• Integrate with CI/CD tools like Jenkins, GitHub Actions, or GitLab CI to run tests in parallel on multiple agents or containers.
• Configure CI pipelines to collect and archive test reports for easy review.
• Use JUnit 5's built-in reporting and third-party tools like Allure for detailed parallel test reports.

Best Practices for Parallel Test Configuration

1. Isolate Tests: Ensure tests do not share state or data to avoid flaky results when running in parallel.
2. Thread-safe WebDriver: Use ThreadLocal or factory patterns to provide each test thread its own WebDriver instance.
3. Configure Parallelism Wisely: Set parallelism level based on machine resources to avoid overload.
4. Use JUnit 5 Native Support: Prefer JUnit 5's built-in parallel execution over external tools for simplicity and reliability.
5. Separate Slow Tests: Group slow or resource-heavy tests separately to optimize overall test suite runtime.

Self Check

Where in this folder structure would you add a new WebDriver factory class that supports thread-safe driver instances for parallel tests?

Key Result

Use JUnit 5's native parallel execution with thread-safe WebDriver instances and proper configuration for reliable parallel test runs.

Practice

1. What is the main purpose of configuring parallel test execution in JUnit?

easy

A. To disable all tests temporarily

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

C. To run multiple tests at the same time and save testing time

D. To automatically fix failing tests

Solution

1. Step 1: Understand parallel test execution

   Parallel test execution means running tests simultaneously instead of one by one.

2. Step 2: Identify the benefit

   Running tests at the same time saves overall testing time.

3. Final Answer:

   To run multiple tests at the same time and save testing time -> Option C

4. Quick Check:

   Parallel tests = faster testing [OK]

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

Common Mistakes:

• Thinking parallel means disabling tests
• Confusing parallel with sequential execution
• Assuming parallel fixes test failures

2. Which annotation enables parallel execution of tests in JUnit 5?

easy

A. @Execution(ExecutionMode.CONCURRENT)

B. @RunWith(ParallelRunner.class)

C. @ParallelTest

D. @ConcurrentExecution

Solution

1. Step 1: Recall JUnit 5 parallel test annotation

   JUnit 5 uses @Execution with ExecutionMode.CONCURRENT to run tests in parallel.

2. Step 2: Check other options

   @RunWith is from JUnit 4, and @ParallelTest or @ConcurrentExecution do not exist in JUnit 5.

3. Final Answer:

   @Execution(ExecutionMode.CONCURRENT) -> Option A

4. Quick Check:

   @Execution(CONCURRENT) enables parallel tests [OK]

Hint: Use @Execution(ExecutionMode.CONCURRENT) for parallel tests [OK]

Common Mistakes:

• Using JUnit 4 annotations in JUnit 5
• Assuming @ParallelTest exists
• Confusing annotation names

3. Given the following JUnit 5 test class, what will be the output when tests run with @Execution(ExecutionMode.CONCURRENT)?

import org.junit.jupiter.api.*;
import org.junit.jupiter.api.parallel.Execution;
import org.junit.jupiter.api.parallel.ExecutionMode;

@TestInstance(TestInstance.Lifecycle.PER_CLASS)
@Execution(ExecutionMode.CONCURRENT)
public class SampleTest {

    @Test
    void testA() throws InterruptedException {
        Thread.sleep(100);
        System.out.println("Test A completed");
    }

    @Test
    void testB() {
        System.out.println("Test B completed");
    }
}

medium

A. Test A completed
Test B completed (always in this order)

B. Test B completed
Test A completed (order may vary due to concurrency)

C. Compilation error due to @Execution usage

D. Tests run sequentially ignoring @Execution

Solution

1. Step 1: Understand @Execution(ExecutionMode.CONCURRENT)

   This annotation runs tests in parallel, so testA and testB start at the same time.

2. Step 2: Analyze test behavior

   testA sleeps 100ms before printing, testB prints immediately. So testB likely prints first, but order can vary.

3. Final Answer:

   Test B completed Test A completed (order may vary due to concurrency) -> Option B

4. Quick Check:

   Parallel tests print order varies [OK]

Hint: Sleep delays show concurrency by changing print order [OK]

Common Mistakes:

• Assuming tests run sequentially despite @Execution
• Expecting fixed print order
• Thinking @Execution causes compile errors

4. You configured @Execution(ExecutionMode.CONCURRENT) but tests fail intermittently due to shared data. What is the best fix?

medium

A. Make tests independent by avoiding shared mutable state

B. Remove @Execution and run tests sequentially

C. Add Thread.sleep() to all tests

D. Use @Disabled on all tests

Solution

1. Step 1: Identify cause of intermittent failures

   Shared mutable data causes race conditions when tests run in parallel.

2. Step 2: Apply best practice for parallel tests

   Tests must be independent and avoid shared mutable state to run safely in parallel.

3. Final Answer:

   Make tests independent by avoiding shared mutable state -> Option A

4. Quick Check:

   Independent tests avoid parallel conflicts [OK]

Hint: Avoid shared data for stable parallel tests [OK]

Common Mistakes:

• Just removing parallel execution instead of fixing tests
• Adding sleeps does not fix race conditions
• Disabling tests hides the problem

5. You want to run tests in parallel but only within each test class, not across classes. Which configuration achieves this in JUnit 5?

hard

A. Annotate test classes with @Execution(ExecutionMode.SAME_THREAD)

B. Use @Execution(ExecutionMode.CONCURRENT) on each test method only

C. Set junit.jupiter.execution.parallel.enabled to false

D. Set junit.jupiter.execution.parallel.mode.default to concurrent and junit.jupiter.execution.parallel.mode.classes.default to same_thread

Solution

1. Step 1: Understand JUnit 5 parallel config properties

   Property junit.jupiter.execution.parallel.mode.default controls method-level parallelism; junit.jupiter.execution.parallel.mode.classes.default controls class-level parallelism.

2. Step 2: Configure methods parallel, classes sequential

   Setting methods to concurrent and classes to same_thread runs tests in parallel within classes but not across classes.

3. Final Answer:

   Set junit.jupiter.execution.parallel.mode.default to concurrent and junit.jupiter.execution.parallel.mode.classes.default to same_thread -> Option D

4. Quick Check:

   Methods parallel + classes sequential = parallel in class only [OK]

Hint: Configure method and class parallel modes separately [OK]

Common Mistakes:

• Assuming @Execution on methods controls class-level parallelism
• Disabling parallel execution entirely
• Using SAME_THREAD on classes disables all parallelism