How does this differ from a standard test runner?

While a test runner simply executes tests to check for passes or fails, this skill audits the logical quality and bug-catching capability of the tests themselves.

Can this skill help find missing edge cases?

Yes, Phase 5 of the process is dedicated to discovering missing corner cases in input validation, state transitions, and integration points.

What is considered a 'RED' flag in this analysis?

Red flags include tautological tests that pass by definition, mock-testing that bypasses production logic, and 'line-hitters' that execute code without assertions.

Why does the skill require reading production code first?

Reading production code is mandatory to verify that the test actually exercises the intended logic and that assertions are meaningful relative to the actual behavior.

Testing Quality Analysis

Name: Testing Quality Analysis
Author: Veraticus

byVeraticus

Security & Testing

Audits test suites with SRE-level scrutiny to identify tautological tests, coverage gaming, and ineffective assertions.

About

The Testing Quality Analysis skill provides a rigorous framework for evaluating the true effectiveness of a codebase's test suite beyond simple coverage metrics. By adopting a skeptical 'SRE-level' mindset, it systematically identifies tests that provide false confidence, such as 'line-hitters' that execute code without meaningful assertions or 'mock-testing' that ignores production logic. This skill forces a line-by-line justification of test validity, ensuring your suite catches real bugs and covers critical edge cases rather than just satisfying vanity metrics.

Key Features

Production Code Verification: Mandates reading implementation logic before assessing test validity.
Corner Case Discovery: Systematically maps out missing edge cases for input validation and state management.
Tautology Detection: Identifies tests that pass by definition or simply duplicate implementation logic.
Rigid Categorization: Classifies tests as RED, YELLOW, or GREEN based on bug-catching potential.
SRE-Level Scrutiny: Evaluates tests with a skeptical mindset to uncover false confidence.
0 GitHub stars

Use Cases

Strengthening regression testing before performing major architectural refactoring.
Assessing test suite reliability during onboarding to unfamiliar or legacy codebases.
Auditing codebases where production bugs persist despite high reported test coverage.

About

Key Features

Production Code Verification: Mandates reading implementation logic before assessing test validity.
Corner Case Discovery: Systematically maps out missing edge cases for input validation and state management.
Tautology Detection: Identifies tests that pass by definition or simply duplicate implementation logic.
Rigid Categorization: Classifies tests as RED, YELLOW, or GREEN based on bug-catching potential.
SRE-Level Scrutiny: Evaluates tests with a skeptical mindset to uncover false confidence.
0 GitHub stars

Use Cases

Strengthening regression testing before performing major architectural refactoring.
Assessing test suite reliability during onboarding to unfamiliar or legacy codebases.
Auditing codebases where production bugs persist despite high reported test coverage.