testing-standards

Enforce behavior-driven development and repository-defined test harnesses across unit, integration, and feature tests.

2|Updated May 18, 2022
One-click install
npx skills add https://github.com/alexfalkowski/bin --skill testing-standards-alexfalkowski
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing-standards
Source: https://github.com/alexfalkowski/bin/tree/main/skills/testing-standards
Command: npx skills add https://github.com/alexfalkowski/bin --skill testing-standards-alexfalkowski

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the lack of consistency and quality in testing by enforcing a behavior-focused, outside-in design approach that prevents cryptic, implementation-coupled, or redundant tests.

Core Features & Use Cases

  • Behavior-First Design: Mandates TDD or BDD workflows that prioritize caller-facing contracts over internal implementation details.
  • Standardized Stop Gates: Provides strict, non-negotiable rules for test boundary selection, harness usage, and red-green-refactor cycles.
  • Use Case: When refactoring a complex service, use this Skill to ensure that tests validate the public API behavior rather than internal method calls, ensuring the test suite remains robust against internal code changes.

Quick Start

Use the testing-standards skill to guide the development of a new feature by identifying the dominant test harness and establishing a red-first TDD cycle.

Frequently Asked Questions about testing-standards

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

FAQPage Schema
How do I enforce behavior-driven test standards in my software engineering workflow?

Behavior-driven test standards are enforced by mandating outside-in design approaches that prioritize caller-facing contracts over internal implementation details. This method prevents cryptic, implementation-coupled tests and maintains high-quality suites.

What is the best way to maintain test suite quality during code refactoring?

To maintain test suite quality during code refactoring, validate public API behavior rather than internal method calls. This practice keeps tests robust against internal code changes and prevents redundant failures.

How do I implement a strict red-green-refactor cycle for unit and integration testing?

Implement a strict red-green-refactor cycle by establishing a red-first TDD workflow and identifying your dominant test harness. This requires alignment with established test boundaries and rigorous refactoring assessments.

Does behavior-driven development work with existing test harnesses across different programming languages?

Behavior-driven development works across diverse language environments by enforcing strict adherence to repository-defined test harnesses. It applies to unit, integration, and feature testing to standardize software testing practices.

Why does my test suite break when refactoring internal implementation details?

Test suites break during refactoring when tests are coupled to internal implementation details rather than caller-facing contracts. Enforcing behavior-first design prevents this by validating public API behavior independently of internal methods.