Checking exception message in JUnit - Framework Patterns

Framework Mode - Checking exception message

Folder Structure

src
└── test
    └── java
        └── com
            └── example
                ├── exceptions
                │   └── CustomException.java
                ├── utils
                │   └── ExceptionUtils.java
                └── tests
                    └── ExceptionMessageTest.java

Test Framework Layers

• Exception Classes: Custom exception definitions (e.g., CustomException.java).
• Utility Layer: Helper methods for exception handling and message extraction.
• Test Layer: JUnit test classes that verify exception types and messages.
• Configuration Layer: Settings for test environment and dependencies.

Configuration Patterns

• Use pom.xml or build.gradle to manage JUnit dependencies.
• Configure test runners to show full stack traces for exceptions.
• Use system properties or environment variables to toggle verbose exception logging if needed.
• Keep exception messages consistent and externalized if localization is required.

Test Reporting and CI/CD Integration

• JUnit reports show test pass/fail with exception message details on failure.
• Integrate with CI tools (Jenkins, GitHub Actions) to run tests on each commit.
• Failing tests with wrong exception messages are clearly reported in CI logs.
• Use plugins like Surefire or Gradle Test Logger for enhanced reporting.

Best Practices

• Use assertThrows to check both exception type and message in one step.
• Keep exception messages clear, concise, and meaningful for easier debugging.
• Test only expected exceptions; avoid catching generic exceptions in tests.
• Use constants or enums for expected messages to avoid typos in tests.
• Write tests that fail if the exception message changes unexpectedly to catch regressions.

Self Check

Where in this folder structure would you add a new test class to verify that a NullPointerException thrown by a utility method contains the correct message?

Key Result

Use JUnit's assertThrows to verify exception type and message clearly and reliably.