test-fixing

Fix failing tests by mandating classification of failure causes, cross-referencing with documentation, and documenting fix reasoning. This structured process ensures fixes address the root cause and align with specifications, preventing superficial test modifications.

Classifying test failures in a CI/CD pipeline involves categorizing them as implementation bugs, test errors, mock configuration issues, or infrastructure problems. This classification guides the appropriate fix and maintains code integrity within the development workflow.

Ensure test fixes align with project specifications by mandating cross-referencing with documentation before making any code changes. This verifies that fixes address the root cause of failures and match the original requirements.

Modifying tests to pass without checking documentation causes regressions because superficial changes often ignore the root cause. This anti-pattern bypasses specification verification, leading to fixes that compromise code integrity and mask underlying implementation bugs.

Document the reasoning behind a test modification immediately after classifying the failure cause and verifying the specification. Explicit documentation of fix reasoning is required to maintain clarity within the development workflow and prevent future regressions.