unit-test-quality

Identify and eliminate useless unit tests using execution and behavior filters.

8|2|Updated Feb 9, 2026

Search Tags:#anti-patterns #pytest #jest #quality #unit-testing #test-review

Ready to run

npx skills add https://github.com/mikeparcewski/wicked-garden --skill unit-test-quality

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: unit-test-quality
Source: https://github.com/mikeparcewski/wicked-garden/tree/main/skills/engineering/unit-test-quality
Command: npx skills add https://github.com/mikeparcewski/wicked-garden --skill unit-test-quality

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

A test suite can accumulate low-value unit tests that pass but fail to protect behavior, bloating the suite and slowing feedback. This skill provides two complementary thought-experiment filters (execution + behavior), a pre-write self-check, a taxonomy of seven recurring anti-patterns, and a one-line decision rule per pattern to help prune non-value tests.

Core Features & Use Cases

Two complementary filters (execution check and behavior check) to distinguish tests that exercise the SUT from those that merely verify input wiring.
A pre-write self-check and a seven-anti-pattern taxonomy to guide test design, review, and refactoring across languages and frameworks.
Use during test-writing, test-review, and regression audits to improve confidence and reduce maintenance burden.

Quick Start

Apply the pre-write self-check before writing or reviewing a unit test.

Frequently Asked Questions about unit-test-quality

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

FAQPage Schema

What makes a unit test useless and how do I identify it?▼

A useless unit test passes but fails to protect behavior. Identify it by applying execution and behavior filters to verify the test actually exercises the system under test and delivers value.

How do I review unit tests for anti-patterns in pytest and jest?▼

Review unit tests by applying a seven-anti-pattern taxonomy to catch tautological, assertion-free, implementation-mirror, framework-retest, constant-verification, sleep-coupled, and exception-swallowing tests across pytest, jest, and junit suites.

Can I use this unit test quality approach across different testing frameworks?▼

Yes, the approach is language-agnostic. You can apply the pre-write self-check and anti-pattern rules across pytest, jest, and junit test suites in real projects including feature modules, bug fixes, and regression tests.

How do I run a pre-write self-check before creating unit tests?▼

Run a pre-write self-check by applying two complementary thought-experiment filters to distinguish tests that exercise the system under test from those that merely verify input wiring before writing code.

What's the best way to eliminate tautological and assertion-free tests?▼

The best way is to use a one-line decision rule per pattern within a seven-anti-pattern taxonomy to guide refactoring and prune non-value tests like tautological and assertion-free tests from your suite.

Why does my test suite pass but still has low-value unit tests?▼

Your suite passes but has low-value unit tests because tests may merely verify input wiring or retest the framework. Applying execution and behavior filters during regression audits helps prune these non-value tests.