yweb-test-quality

To identify tautological or shallow pytest tests, review the test suite for authenticity by checking if tests only cover happy paths or mirror implementation details. This skill flags false positives and guides refactoring to ensure tests validate actual behavior.

The best way to debug a failing pytest test is using a diagnose-then-code-fix workflow to triage the failure. This approach systematically determines whether the failure indicates a code bug or an issue with the test itself.

Your test passes but fails to catch bugs because it likely contains implementation-driven or happy path assertions that create false positives. Reviewing test authenticity helps eliminate these shallow tests and ensures assertions validate real logic.

To review pytest tests for authenticity before merging, evaluate the suite to eliminate happy path, shallow, implementation-driven, or tautological tests. This ensures robust code by preventing fake tests from masking real failures.

You need failure analysis for pytest test failures when diagnosing whether a failure indicates a bug in the code or an issue with the test itself. This triage prevents wasted effort on incorrect fixes during debugging.