fix-skipped-tests

Detect and remediate skipped tests across unit and integration suites.

6|1|Updated Apr 26, 2025

Search Tags:#qa #unit-testing #tests #test-automation #skip #test-todo

Ready to run

npx skills add https://github.com/edobry/minsky --skill fix-skipped-tests

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fix-skipped-tests
Source: https://github.com/edobry/minsky/tree/main/.claude/skills/fix-skipped-tests
Command: npx skills add https://github.com/edobry/minsky --skill fix-skipped-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintains a healthy test suite by eliminating skipped and placeholder tests, ensuring every test either passes or is removed.

Core Features & Use Cases

Identify skipped tests across the suite (test.skip, it.skip, describe.skip) and placeholders (test.todo, it.todo) and flag their impact.
Investigate the reason for each skip and classify into real operations, integration complexity, legacy code, or excessive complexity.
Fix or delete: mock external deps, break tests into smaller units, or remove obsolete tests, then re-run to ensure zero skipped tests.

Quick Start

Run the fixer on your test suite to locate all skipped or placeholder tests and remediate them.

Frequently Asked Questions about fix-skipped-tests

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I find and fix skipped tests in my codebase?▼

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.

What does a zero-tolerance policy for skipped tests mean?▼

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.

How do I handle test.todo and placeholder assertions in my unit tests?▼

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.

Can I apply a zero-skipped-tests policy across both unit and integration test suites?▼

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.

When should I delete a skipped test instead of fixing it?▼

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.