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.