fix-skipped-tests

Locate skipped unit and integration tests by scanning for markers like test.skip, it.skip, describe.skip, and test.todo, then remediate them by mocking external dependencies, breaking down complex tests, or deleting obsolete test cases.

A zero-tolerance policy for skipped tests means every test must either pass or be removed from the suite. This eliminates placeholder assertions and test.todo markers to ensure reliable, comprehensive test coverage results.

Handle test.todo and placeholder assertions by investigating the skip reason, classifying it as integration complexity or legacy code, and then either implementing the test logic, mocking external dependencies, or deleting the obsolete test entirely.

Yes, you can apply a zero-skipped-tests policy across both unit and integration test suites. The process requires tooling to detect skip markers like describe.skip across all suites, categorize reasons, and enforce remediation to ensure reliable test results.

You should delete a skipped test instead of fixing it when the test is obsolete or covers legacy code that no longer applies. If mocking external dependencies or breaking tests into smaller units is not feasible, removal enforces the zero-skipped-tests policy.