Single assertion per test debate in JUnit - Framework Patterns

Framework Mode - Single assertion per test debate

Folder Structure

src/
└── test/
    └── java/
        └── com/
            └── example/
                ├── pages/
                │   └── LoginPage.java
                ├── tests/
                │   └── LoginTests.java
                ├── utils/
                │   └── TestUtils.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: Contains JUnit test classes with test methods and assertions.
• Utilities: Helper methods for common tasks like waits, data generation.
• Configuration: Holds environment settings, credentials, browser options.

Configuration Patterns

• Use TestConfig.java to load environment variables (e.g., dev, staging, prod).
• Use system properties or config files to select browser type (Chrome, Firefox).
• Store sensitive data like credentials securely, e.g., environment variables or encrypted files.
• Allow easy switching of test environments without code changes.

Test Reporting and CI/CD Integration

• Use JUnit's built-in reports for pass/fail results.
• Integrate with CI tools like Jenkins or GitHub Actions to run tests on code changes.
• Generate HTML or XML reports for detailed test results.
• Fail fast on assertion failure to save time.

Framework Design Principles

1. Clear Test Purpose: Each test should verify one behavior or scenario clearly.
2. Single Assertion Debate: Prefer one assertion per test for clarity, but multiple related assertions are acceptable if they test one logical outcome.
3. Readable Tests: Use descriptive test method names and comments to explain intent.
4. Reusable Page Objects: Keep UI interaction code separate from tests.
5. Fail Fast: Stop test execution on first failure to avoid misleading results.

Self Check

Where would you add a new test method that verifies the login error message appears when invalid credentials are used?

Key Result

Organize tests with clear layers and prefer one assertion per test for clarity, balancing practicality in JUnit frameworks.