How a silent Maven config change can drop tests while keeping CI green

A developer building a Spring Boot demo discovered that adding an include filter to Maven's Surefire plugin caused one of two test classes to stop running entirely, while the build still passed with exit code 0. Because Maven only checks whether the tests it ran passed, a missing test class produces no error, no red build, and no malformed report. Standard CI tools and JUnit reporters cannot detect an absent report unless they know which reports were expected in the first place. The author tested Exevra, a tool that records a baseline of expected test report files and fails the workflow if any are missing on a subsequent run. The experiment highlights that changes to test-execution scope can silently shrink a test suite, and making such changes an explicit, reviewable contract is one way to close that gap.