testing-rules

Enforce black-box testing and 12-category test taxonomy compliance.

3|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/Doumajnik/template --skill testing-rules-doumajnik
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing-rules
Source: https://github.com/Doumajnik/template/tree/main/.github/skills/testing-rules
Command: npx skills add https://github.com/Doumajnik/template --skill testing-rules-doumajnik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates inconsistent, low-quality test suites that create false confidence and miss critical production bugs, reducing costly outages and rework caused by inadequate testing coverage.

Core Features & Use Cases

  • Black-box testing enforcement: Blocks test writers from accessing source code to prevent tests that mirror implementation blind spots and miss edge cases.
  • 12-category test taxonomy: Mandates comprehensive coverage of happy paths, boundary values, adversarial inputs, error contracts, and more for every function.
  • Test quality gates: Enforces strong assertions, mutation testing targets, and AAA layout to eliminate weak, false-positive tests.
  • Use Case: A team building a new payment processing feature uses this Skill to ensure their tests catch edge cases like invalid currency inputs and concurrent transaction conflicts, avoiding costly financial errors.

Quick Start

Apply the testing-rules skill to audit your existing test suite for a user authentication module and identify missing boundary and adversarial test cases.

Frequently Asked Questions about testing-rules

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

FAQPage Schema
How do I enforce consistent unit testing standards across my software engineering team?

You can enforce consistent unit testing standards by applying a 12-category test taxonomy that mandates coverage of happy paths, boundary values, and error contracts for every function. This eliminates weak test suites and catches critical production bugs early.

What is black-box testing enforcement and how does it improve test quality?

Black-box testing enforcement blocks test writers from accessing source code to prevent tests that mirror implementation blind spots. By isolating test authoring from internal logic, it ensures tests validate external behavior and catch missed edge cases.

How do I audit an existing test suite for missing boundary and adversarial test cases?

You can audit an existing test suite by validating it against a 12-category test taxonomy that checks for boundary values, adversarial inputs, and error contracts. This identifies missing edge case coverage and validates your test quality gates.

Does this testing approach work for integration test design and test infrastructure setup?

Yes, this testing approach applies to all test authoring and review workflows, including integration test design, test infrastructure setup, and test strategy planning. It enforces quality gates and adversarial test case coverage for any software project.

Why do my unit tests pass but still miss critical production bugs?

Unit tests pass but miss production bugs because weak assertions and low coverage create false confidence. Applying test quality gates that enforce AAA layout, mutation testing targets, and adversarial input coverage eliminates false positives and catches edge cases.