@Execution annotation in JUnit - Framework Patterns

Framework Mode - @Execution annotation

Folder Structure for JUnit Test Framework

src/
├── main/
│   └── java/
│       └── com/example/app/       # Application source code
└── test/
    └── java/
        └── com/example/app/tests/ # Test classes
            ├── pages/              # Page Object classes
            ├── utils/              # Utility classes (e.g., waits, helpers)
            ├── config/             # Test configuration classes
            └── tests/              # Test classes using @Execution

Test Framework Layers

• Driver Layer: Manages WebDriver setup and teardown for browser automation.
• Page Objects: Encapsulate UI elements and actions for each page.
• Test Classes: Contain test methods annotated with JUnit annotations including @Execution to control parallel or sequential execution.
• Utilities: Helper methods for waits, assertions, and common actions.
• Configuration: Manage environment variables, browser settings, and credentials.

Configuration Patterns

• Environment Profiles: Use Java system properties or config files (e.g., application.properties) to switch between test environments.
• Browser Settings: Parameterize browser type and version via system properties or config classes.
• Credentials Management: Store sensitive data securely outside source code, inject via environment variables or encrypted files.
• JUnit Configuration: Use @Execution annotation at class or method level to specify parallel or sequential execution mode.

Test Reporting and CI/CD Integration

• Integrate JUnit reports with CI tools like Jenkins or GitHub Actions for automated test runs.
• Use plugins (e.g., Surefire, Allure) to generate readable HTML reports showing test results and execution order.
• Configure CI pipelines to run tests in parallel or sequentially based on @Execution annotation settings.
• Fail fast or retry strategies can be configured in CI based on test outcomes.

Best Practices for Using @Execution Annotation

1. Use @Execution(ExecutionMode.CONCURRENT) to speed up test suites by running tests in parallel when tests are independent.
2. Use @Execution(ExecutionMode.SAME_THREAD) for tests that share state or require sequential execution to avoid flaky results.
3. Apply @Execution at the class level to control all tests in that class or at method level for fine-grained control.
4. Ensure thread safety in tests and page objects when running in parallel to prevent race conditions.
5. Combine @Execution with proper setup and teardown methods to isolate tests.

Self Check Question

Where in this folder structure would you add a new test class that uses @Execution(ExecutionMode.CONCURRENT) to run tests in parallel?

Key Result

Use @Execution annotation in JUnit tests to control parallel or sequential execution for efficient and reliable test runs.