testing

Provides guidance for writing executable tests with a focus on simplicity and the

8|Updated Dec 16, 2008
One-click install
npx skills add https://github.com/sebnow/configs --skill testing-sebnow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing
Source: https://github.com/sebnow/configs/tree/main/home-manager/agentic/skills/testing
Command: npx skills add https://github.com/sebnow/configs --skill testing-sebnow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use when implementing automated tests. This Skill promotes empirical testing, adherence to the test pyramid, TDD practices, and rigorous concurrent testing to prevent flaky software.

Core Features & Use Cases

  • Establish fast, reliable, and deterministic tests that align with requirements.
  • Apply unit, integration, system, and chaos/resilience testing to validate component interactions and system behavior.
  • Follow a TDD workflow: Red, Green, Refactor, with strong emphasis on test-driven development and maintainability.

Quick Start

Start by writing a failing test, then implement only enough code to pass, and run tests with the race detector enabled.

Frequently Asked Questions about testing

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

FAQPage Schema
How do I write reliable unit tests that won't become flaky?

Reliable unit tests require strict determinism, fast execution, and clear quality standards. You should apply the test pyramid, use table-driven testing patterns, and ensure robust error handling to validate component interactions without introducing flakiness.

What is the test-driven development workflow for building new features?

The test-driven development workflow follows a Red, Green, Refactor cycle. You start by writing a failing test, implement only enough code to pass it, and then refactor for maintainability while keeping tests fast and deterministic.

How do I detect race conditions in concurrent system testing?

Detecting race conditions in concurrent system testing requires running tests with the race detector enabled. This enforces rigorous concurrent testing standards to catch data races and validate robust component interactions across threads.

What's the best way to structure integration testing for component interactions?

The best way to structure integration testing is to align tests with system requirements and apply the test pyramid. You validate component interactions by combining table-driven testing with rigorous checks for speed, determinism, and coverage.

When do I need property-based testing instead of standard unit tests?

You need property-based testing when standard unit tests cannot cover broad input variations effectively. It complements disciplined testing by empirically validating system behavior against specified requirements and ensuring robust error handling.

Does this testing approach work for chaos and resilience testing?

Yes, this approach explicitly supports chaos and resilience testing to validate system behavior. It applies structured guidelines to ensure tests remain fast, deterministic, and robust when validating component interactions under varying system conditions.