detecting-test-theater

Name: detecting-test-theater
Availability: InStock
Author: walsh-investment

Scan a repository's test suite and report low-value tests using eight test theater patterns.

Updated Sep 1, 2025

Search Tags:#testing #patterns #quality-assurance #scan #pattern-library #repository-analysis #test-theater

Ready to run

npx skills add https://github.com/walsh-investment/clean-slate-import --skill detecting-test-theater

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: detecting-test-theater
Source: https://github.com/walsh-investment/clean-slate-import/tree/main/.claude/skills/detecting-test-theater
Command: npx skills add https://github.com/walsh-investment/clean-slate-import --skill detecting-test-theater

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scans repositories to identify tests that pass but fail to verify real behavior, helping teams raise test quality and reduce risk.

Core Features & Use Cases

Scans a repository's test suite and applies eight test-theater heuristics to surface low-value or misleading tests.
Generates a prioritized findings report with file paths, line references, severity ratings, and remediation suggestions.
Loads the shared pattern library from references/pattern-library.md to ensure consistent detection and guidance.

Quick Start

Scan the current workspace for problematic tests.

Frequently Asked Questions about detecting-test-theater

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

FAQPage Schema

What are test theater patterns in software testing?▼

Test theater patterns are eight specific heuristics used to identify low-value or misleading tests that pass without verifying real behavior. Scanning a repository with these patterns surfaces hollow tests, reducing quality risk.

How do I scan my repository for hollow or misleading tests?▼

To scan for misleading tests, load the pattern library from references/pattern-library.md and analyze test files while excluding non-test utilities. This generates a prioritized findings report with file paths, line references, and severity ratings.

How can I find tests that pass but do not actually verify behavior?▼

Finding tests that pass without verifying behavior requires applying the eight test theater heuristics to your test suite. This process identifies hollow tests and outputs a prioritized findings report with remediation guidance.

Does this test quality scan work on any repository or workspace?▼

The test quality scan operates on a single repository or workspace. It loads the shared pattern library to ensure consistent detection and guidance across the analyzed test suite files.

What is included in the test theater findings report?▼

The findings report includes file paths, line references, severity ratings, explanations of detected test theater patterns, and remediation suggestions. It is prioritized to help teams systematically raise test quality.

How to exclude non-test utility files when scanning for low-value tests?▼

To exclude non-test utility files when scanning for low-value tests, the detection logic filters out non-test utilities during file scanning. This ensures the eight test theater heuristics apply only to actual test suite files.