Refactoring Test Suites

What problem does it solve?

This Skill standardizes and cleans up messy test suites by applying project-wide conventions for test naming, structure, parameterization, and classification to improve CI reliability and developer readability across languages.

Core Features & Use Cases

• Standardize behavioral test naming: Rename tests to describe outcomes rather than implementation details (e.g., test_should_X_when_Y, test_rejects_X_when_Y).
• Decompose multi-assert tests: Split tests with multiple branches into atomic units with single assertions and concise summaries.
• Parameterize repeated logic: Consolidate duplicate test structures into parameterized cases (e.g., @pytest.mark.parametrize in Python) and move shared setup to fixtures.
• Classify and relocate tests: Move files into tests/unit/ or tests/features/ and update runners/imports.
• Eliminate vanity tests: Remove tests that do not verify meaningful behavior; document rationale.
• Tag and annotate tests: Add metadata tags like @unit or @integration and normalize inline comments.

Quick Start

Example: Run the Refactoring Test Suites skill on a messy PyTest project to rename tests, split atomic cases, parameterize inputs, and relocate files while applying tags for clear classification.