@CsvSource for inline CSV data in JUnit - Framework Patterns

Framework Mode - @CsvSource for inline CSV data

Folder Structure

src/
└── test/
    └── java/
        └── com/
            └── example/
                ├── tests/
                │   └── CalculatorParameterizedTest.java
                ├── pages/
                │   └── CalculatorPage.java
                ├── utils/
                │   └── TestUtils.java
                └── config/
                    └── TestConfig.java

Test Framework Layers

• Test Classes: Contain test methods using @CsvSource for inline CSV data-driven tests (e.g., CalculatorParameterizedTest.java).
• Page Objects: Encapsulate UI interactions (e.g., CalculatorPage.java).
• Utilities: Helper methods and reusable code (e.g., TestUtils.java).
• Configuration: Environment and test settings (e.g., TestConfig.java).

Configuration Patterns

• Environment Properties: Use TestConfig.java or application.properties to manage URLs, credentials, and environment-specific data.
• Browser Settings: Configure browser type and options via system properties or config files.
• Test Data: Inline CSV data is embedded directly in test methods using @CsvSource, avoiding external files for simple datasets.
• Profiles: Use Maven or Gradle profiles to switch environments if needed.

Test Reporting and CI/CD Integration

• JUnit Reports: Use built-in JUnit XML reports for test results.
• CI/CD Integration: Integrate with Jenkins, GitHub Actions, or GitLab CI to run tests on each commit.
• Enhanced Reporting: Use plugins like Surefire or Allure for detailed reports with test parameters shown.
• Fail Fast: Configure CI to stop on failures or continue based on project needs.

Best Practices

1. Use @CsvSource for Small Data Sets: Inline CSV is perfect for simple, small sets of test data to keep tests readable.
2. Keep Test Data Clear: Use descriptive values and avoid complex escaping in CSV strings.
3. Combine with ParameterizedTest: Always pair @CsvSource with @ParameterizedTest for clean data-driven tests.
4. Separate Concerns: Keep test logic in test classes and UI interactions in page objects.
5. Use Descriptive Test Names: Use name attribute in @ParameterizedTest to show input values in reports.

Self Check

Where would you add a new test method that uses @CsvSource to test login credentials in this framework structure?

Key Result

Use @CsvSource with @ParameterizedTest in test classes for inline CSV data-driven testing.