JUnit 5 Root Cause Analysis
1. Capture the Failure
- Capture the failing class, method, stack trace, and environment details.
- Reproduce the failure as narrowly as possible.
- Separate symptom from suspected cause.
2. Classify the Failure
- Check for assertion mismatch.
- Check for fixture leakage or ordering issues.
- Check for environment mismatch.
- Check for timing, randomness, file system, locale, or time zone issues.
- Check for a real production bug.
3. Report the Diagnosis
- State the most likely root cause.
- State the evidence supporting that conclusion.
- State the smallest safe next fix.
- State any remaining uncertainty explicitly.