Unit testing concept in JUnit - Framework Patterns

Framework Mode - Unit testing concept

Folder Structure

project-root/
├── src/
│   ├── main/
│   │   └── java/
│   │       └── com/
│   │           └── example/
│   │               └── app/
│   │                   └── Calculator.java
│   └── test/
│       └── java/
│           └── com/
│               └── example/
│                   └── app/
│                       └── CalculatorTest.java
├── pom.xml
└── README.md
    

This is a typical Maven project structure for JUnit unit tests. Production code is under src/main/java. Test code is under src/test/java.

Test Framework Layers

• Production Code Layer: Contains the actual classes and methods to be tested (e.g., Calculator.java).
• Test Layer: Contains JUnit test classes with test methods that verify small units of code (e.g., CalculatorTest.java).
• Utilities Layer: Helper classes or methods for common test tasks (optional in simple unit tests).
• Configuration Layer: Handles test settings like test profiles or environment variables.

Configuration Patterns

Unit tests usually run in a simple environment, but configuration can include:

• Build Tool Config: Use pom.xml to add JUnit dependency and configure test execution.
• Test Profiles: Use Maven profiles or system properties to switch configurations if needed.
• Mocking Setup: Configure mocking frameworks (like Mockito) if tests need to isolate units.

<dependency>
  <groupId>org.junit.jupiter</groupId>
  <artifactId>junit-jupiter</artifactId>
  <version>5.9.3</version>
  <scope>test</scope>
</dependency>
    

Test Reporting and CI/CD Integration

• JUnit Reports: Maven Surefire plugin generates XML and HTML reports after test runs.
• CI/CD Integration: Configure Jenkins, GitHub Actions, or GitLab CI to run tests on each commit.
• Fail Fast: Tests fail quickly if a unit test fails, preventing broken code from progressing.
• Code Coverage: Integrate tools like JaCoCo to measure how much code is tested.

Best Practices for Unit Testing Framework

1. Isolate Tests: Each test should test one small piece of code independently.
2. Use Descriptive Names: Test method names should clearly say what they check.
3. Keep Tests Fast: Unit tests should run quickly to encourage frequent runs.
4. Arrange-Act-Assert Pattern: Structure tests with setup, action, and verification steps.
5. Use Assertions Properly: Assert expected results clearly to catch errors early.

Self Check

Where in this folder structure would you add a new unit test class for a new feature called StringUtils?

Key Result

Organize unit tests under src/test/java mirroring production code, use JUnit for isolated, fast, and clear tests with proper configuration and reporting.