deep-test

Prunes redundant tests and detects critical coverage gaps through multi-phase test suite auditing.

Updated Jan 2, 2025
One-click install
npx skills add https://github.com/mcinnisd/gymbro --skill deep-test-mcinnisd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deep-test
Source: https://github.com/mcinnisd/gymbro/tree/main/.agents/skills/deep-test
Command: npx skills add https://github.com/mcinnisd/gymbro --skill deep-test-mcinnisd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Test suites accumulate bloated, tautological, and over-mocked tests that slow feedback loops while leaving critical seams like auth isolation and error paths untested. This Skill performs a dual-mandate audit that deletes low-value tests and identifies or fixes genuine coverage gaps. ## Core Features & Use Cases - Test Bloat Pruning: Deletes fake E2E tests, tautological mock assertions, and duplicate flow tests to keep the suite fast and high-signal. - Critical Gap Detection: Identifies untested public seams such as multi-tenant isolation, negative auth paths, and widget action round-trips. - Dynamic Execution & Issue Filing: Runs pytest and TypeScript checks, presents a human-reviewed health report, then files tracked GitHub issues via gh issue create. - Use Case: Run it before a release to consolidate a slow test suite, verify auth isolation across endpoints, and automatically ticket remaining gaps for implementation. ## Quick Start Ask the agent to run a deep test audit that prunes redundant tests, executes the suite, and files issues for any critical coverage gaps it finds.

Frequently Asked Questions about deep-test

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

FAQPage Schema
How do I reduce test suite bloat without losing coverage?

Delete tautological tests that only assert mocks were called, fake E2E tests that are fully mocked, and duplicate flow tests covering identical endpoints. Consolidate repeated sequences into parameterized fixtures while keeping tests that target public domain boundaries.

How to find critical testing gaps in a Flask backend?

Audit public seams rather than internals: check multi-tenant isolation across all endpoints, negative auth paths like expired JWTs and duplicate registrations, and full round-trips from API payload to database mutation. Run pytest with MOCK_DB enabled to verify behavior.

What makes a test tautological and worth deleting?

A tautological test mocks the function under test and merely asserts the mock was called, verifying nothing about real behavior. Tests asserting internal keys of mock classes or static dictionary strings also fall into this category.

Does this workflow require human approval before filing issues?

Yes, the workflow pauses after presenting a test health and net reduction report. GitHub issues are only created via gh issue create after the human confirms the proposed deletions, fixes, and tickets.

When should I not delete a heavily mocked test?

Keep mocked tests when they verify realistic failure paths such as rate limits, timeouts, or malformed inputs that are hard to reproduce live. Replace them only when a real vertical tracer-bullet test can cover the same public seam.