Fix nested test class failure detection and version bump to 1.15.

[sid2700]

Summary

Fixes a bug where test failures in JUnit 5 @Nested inner classes were not retried by the supertest plugin.

Root cause: Surefire 3.x reports nested class test cases inside the outer class's XML report, but uses the @DisplayName (e.g., "AddNumbers Method Tests") as the classname attribute instead of the FQCN. The plugin was building a retry command like -Dtest=OuterClass#nestedMethod*, but surefire's -Dtest filter cannot locate methods that only exist inside nested classes when filtering by the outer class name — resulting in Tests run: 0 on retry.

Fix:

• SurefireReportParser now detects nested class failures by comparing testcase/@classname against testsuite/@name
• When a nested class test fails, the entire outer class is rerun without method filtering (-Dtest=OuterClass instead of -Dtest=OuterClass#method*), since surefire has no way to target individual methods inside nested classes
• Adds a null check for testcase child nodes to prevent NPE on test cases with no failure/error elements
• createRerunCommand uses getOuterClassName() to correctly track nested class reports (from other surefire versions that generate separate $-prefixed XMLs) against allTestClasses, which excludes inner classes via **/*$*

Version bumped to 1.15.

Test plan

• Added NestedInnerTest.xml test fixture matching real surefire 3.5.4 output format (nested class tests with display name as classname)
• Added createRerunCommandWithNestedTestClassFailure test verifying entire outer class is rerun
• Added testGetOuterClassName unit test
• Existing tests continue to pass (17/17)

[francispereira]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.