testing-discipline

Enforce TDD workflows, mocking strategies, and test structure quality.

Updated Mar 2, 2026
One-click install
npx skills add https://github.com/maestria-co/ai-playbook --skill testing-discipline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing-discipline
Source: https://github.com/maestria-co/ai-playbook/tree/main/skills/testing-discipline
Command: npx skills add https://github.com/maestria-co/ai-playbook --skill testing-discipline

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tests that exist but don't catch bugs are worse than no tests — they create false confidence. This skill focuses on test quality over test quantity: TDD workflow, test structure, mocking strategy, anti-patterns, and when coverage numbers lie. Use alongside writing-tests for the full testing workflow.

Core Features & Use Cases

  • TDD workflow and test structure
  • Mocking strategy and anti-patterns
  • Coverage guidance and quality gates across unit/integration tests

Quick Start

Write a failing test before implementing the code to make it pass, ensuring tests stay green and maintainable.

Frequently Asked Questions about testing-discipline

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

FAQPage Schema
How do I fix brittle tests and avoid common mocking anti-patterns?

Fix brittle tests by enforcing disciplined test structure and applying proper mocking strategies. This approach identifies test anti-patterns during test reviews to ensure tests remain maintainable and catch real bugs.

What is the best way to structure tests for a red-green-refactor TDD workflow?

Structure tests for the red-green-refactor TDD workflow by writing a failing test before implementing code, ensuring clear test naming and proper test structure to guide development and maintainability.

Why does high test coverage create false confidence in my software project?

High test coverage creates false confidence when tests are brittle or fail to catch bugs. Applying coverage guidance and quality gates shifts focus from test quantity to test quality, avoiding false security.

Can I use disciplined testing strategies for both unit and integration tests?

Yes, disciplined testing strategies apply to both unit and integration tests. Applying coverage guidance and quality gates across your test suite ensures proper mocking and clear structure at every testing level.

When should I refactor my test suite to improve test quality?

Refactor your test suite to improve test quality during test reviews and test-suite maintenance. Identifying anti-patterns and enforcing disciplined TDD prevents false confidence and ensures tests stay green and maintainable.