Test-Skip Discipline

What problem does it solve?

It stops test suites from staying green by incorrectly using skip conditions that mask failures—especially when the system-under-test is actually broken but the test reports “skipped” instead of “failed.”

Core Features & Use Cases

• Distinguishes acceptable skips vs BLOCKED skips: Treats skips as valid only when the test cannot execute due to environment preconditions (e.g., missing credentials, feature flags off, platform mismatch), and flags skips as BLOCKED when they depend on runtime outcomes (e.g., HTTP 5xx/429, upstream degraded/unreachable, response.ok being false).
• Provides concrete anti-patterns and remediation guidance: Uses examples across Playwright/pytest/Rust to show how to replace runtime-result skips with assertions or retry-then-fail flows.
• Supports consistent detection via grep protocol: Offers ready-to-run search patterns to find skip misuse across test codebases and triage findings as FIX, RELAX, or EXCEPTION.

Quick Start

Use this skill to audit your Playwright/pytest/Rust tests for any skip statements tied to response status or upstream behavior, and replace them with environment-gated skips or assertions (or retry-then-fail for rate limits).