Verification times (times, never, atLeast) in JUnit - Framework Patterns

Framework Mode - Verification times (times, never, atLeast)

Folder Structure

src/
└── test/
    └── java/
        └── com/
            └── example/
                ├── pages/
                │   └── LoginPage.java
                ├── tests/
                │   └── LoginTest.java
                ├── utils/
                │   └── VerificationUtils.java
                └── config/
                    └── TestConfig.java
    

Test Framework Layers

• Driver Layer: Manages WebDriver setup and teardown for browser control.
• Page Objects: Encapsulate UI elements and actions (e.g., LoginPage.java).
• Tests: Contain JUnit test classes with test methods using verification times.
• Utilities: Helper classes like VerificationUtils for reusable verification methods.
• Configuration: Holds environment settings, browser options, and credentials.

Configuration Patterns

Use TestConfig.java to manage environment variables and browser settings.

Example:

public class TestConfig {
    public static final String BASE_URL = System.getProperty("baseUrl", "https://example.com");
    public static final String BROWSER = System.getProperty("browser", "chrome");
    public static final String USERNAME = System.getProperty("username", "testuser");
    public static final String PASSWORD = System.getProperty("password", "password123");
}
    

Pass these properties via command line or CI environment variables for flexibility.

Test Reporting and CI/CD Integration

• Use JUnit's built-in reports or integrate with tools like Surefire plugin for Maven.
• Generate HTML reports with plugins like Allure for better visualization.
• Integrate tests in CI/CD pipelines (e.g., Jenkins, GitHub Actions) to run on each commit.
• Fail tests if verification times conditions (times, never, atLeast) are not met.

Best Practices for Verification Times in JUnit

1. Use Verification Times Explicitly: Clearly specify how many times a method should be called using times(n), never(), or atLeast(n) to avoid flaky tests.
2. Keep Verifications Close to Actions: Verify interactions immediately after the action to improve readability and debugging.
3. Use Mocks and Spies Properly: Use Mockito mocks/spies to track method calls for verification times.
4. Fail Fast on Verification Errors: Let tests fail immediately if verification times do not match expectations to catch issues early.
5. Document Verification Intent: Comment why a certain number of calls is expected to help future maintainers.

Self Check

Where in this folder structure would you add a new verification method to check that a button click happens at least twice?

Key Result

Use explicit verification times (times, never, atLeast) in JUnit tests with Mockito to ensure correct method call counts.