test-skip-discipline

Detect runtime-result-based test skips that mask system failures.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/terrene-foundation/kailash-coc-claude-rb --skill test-skip-discipline-terrene-foundation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-skip-discipline
Source: https://github.com/terrene-foundation/kailash-coc-claude-rb/tree/main/.claude/skills/test-skip-discipline
Command: npx skills add https://github.com/terrene-foundation/kailash-coc-claude-rb --skill test-skip-discipline-terrene-foundation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents test suites from going green while the system under test is actually broken by distinguishing between skips that are purely environmental and skips that absorb real runtime failures.

Core Features & Use Cases

  • Acceptable skip detection: Treats skips caused by preconditions like missing credentials, disabled feature flags, or unsupported platforms as valid gates that cannot execute the test path.
  • Blocked skip enforcement: Flags skips based on runtime outcomes (HTTP 5xx/429, upstream unreachable, response.ok failures, or any result-derived skip) as masking failures.
  • Operational guidance for triage: Provides detection greps for /redteam reviews and a clear FIX/RELAX/EXCEPTION resolution protocol to restore signal.

Quick Start

Ask the AI to review your tests for any test.skip or pytest.skip that depends on HTTP status, response flags, or upstream availability, and to rewrite the skips into assertions or retry-then-fail where appropriate.

Frequently Asked Questions about test-skip-discipline

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

FAQPage Schema
Why does test.skip mask integration test failures in CI?

Test.skip masks integration test failures when skips are triggered by runtime outcomes like HTTP 5xx or response.ok failures, causing broken systems to report as green. It distinguishes these from valid environmental precondition skips like missing credentials.

How do I stop Playwright tests from skipping on HTTP 429 rate limits?

To stop Playwright tests from skipping on HTTP 429 rate limits, you must rewrite skips into assertions or retry-then-fail logic. Blocking skips based on response status absorbs real runtime failures instead of testing them.

When is it acceptable to conditionally skip pytest tests?

It is acceptable to conditionally skip pytest tests when preconditions prevent execution entirely, such as missing credentials, disabled feature flags, or unsupported platforms. Skips based on runtime results or upstream availability are flagged as masking failures.

Does this test skip enforcement approach work with Rust harnesses?

Yes, this approach works with Rust harnesses, as well as Playwright and pytest. It specifically targets end-to-end and integration suites where conditional test skipping occurs, enforcing discipline across these testing environments.

What is the best way to triage hidden failures from masked test skips?

The best way to triage hidden failures from masked test skips is using a FIX/RELAX/EXCEPTION resolution protocol. Detection greps are provided for /redteam reviews to identify and restore signal from blocked skips.