java-test-updater

To fix failing JUnit tests after refactoring Java code, you must first distinguish between compilation errors and assertion failures. This skill guides you through applying mechanical fixes for compilation errors while providing a framework to triage assertion failures based on their root cause.

The best way to update Java tests without masking regressions is to avoid auto-updating tests that correctly identify new bugs. This skill triages assertion failures to differentiate intentional behavior changes and over-mocked internals from genuine regressions, ensuring tests are updated appropriately based on the root cause.

JUnit tests often fail during correct implementation changes due to over-coupled test structures tightly bound to implementation details. This skill helps identify and address over-mocked internals, allowing you to update assertions safely when behavior has intentionally changed without breaking the test framework.

Yes, you can use this skill to handle compilation errors in your Java test suite. It guides users through mechanical fixes for compilation errors in Java projects following code modifications, separating these structural issues from assertion failures to ensure a clear test maintenance workflow.

You should not auto-update failing JUnit assertions when the failure represents a genuine regression caused by new bugs. This skill emphasizes preventing the accidental masking of bugs by ensuring tests are updated appropriately based on the root cause of their failure rather than blindly overwriting assertions.