Refactoring Test Suites

Test naming conventions like `test_should_X_when_Y` describe outcomes instead of implementation details. This Skill renames tests across your suite to enforce behavioral naming patterns, improving readability and making test intent immediately clear to developers reviewing the codebase.

Multi-assert tests obscure which assertion failed and make debugging harder. Decomposing tests into atomic units with single assertions isolates failures, simplifies CI diagnostics, and ensures each test verifies one behavior, reducing maintenance friction.

Yes. Parameterization via `@pytest.mark.parametrize` and similar language mechanisms consolidates repeated test structures into single cases with multiple inputs, reducing duplication, improving maintainability, and making the test suite faster to read and modify.

This Skill relocates tests into conventional directories like `tests/unit/` or `tests/features/`, tags tests with metadata like `@unit` or `@integration`, and updates imports and CI runners accordingly, ensuring consistent discovery and execution across your project.

Vanity tests that don't validate real behavior bloat your suite and create maintenance overhead. This Skill identifies and removes them while documenting the rationale, keeping your test suite focused on coverage that matters to reliability.