testing

Guide test-first development with TDD cycles and test-type selection.

14|7|Updated Dec 4, 2025
One-click install
npx skills add https://github.com/aj-geddes/unicorn-team --skill testing-aj-geddes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing
Source: https://github.com/aj-geddes/unicorn-team/tree/main/skills/testing
Command: npx skills add https://github.com/aj-geddes/unicorn-team --skill testing-aj-geddes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Guides teams in adopting test-first development and robust testing strategies by outlining how to write tests, choose test types, and organize test artifacts.

Core Features & Use Cases

  • TDD cycle guidance (RED-GREEN-REFACTOR) to drive design with tests.
  • Test-type selection and structure guidance for unit, integration, and end-to-end testing.
  • Mocking and coverage best practices, anti-patterns, and pragmatic workflows to improve reliability.
  • Anti-pattern awareness and actionable improvement paths for legacy or flaky tests.

Quick Start

Write a failing test for a new feature and follow it with the minimal implementation to pass.

Frequently Asked Questions about testing

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

FAQPage Schema
How do I start test-driven development for a new feature?

To start test-driven development, write a failing test for a new feature and follow it with the minimal implementation to pass. This RED-GREEN-REFACTOR cycle drives design with tests and prevents brittle code.

When should I choose unit testing versus end-to-end testing?

Unit testing versus end-to-end testing selection depends on your robust testing strategy. The Skill provides test-type selection and structure guidance to organize test artifacts and improve reliability across software projects of all sizes.

What are the best practices for mocking to prevent flaky tests?

Mocking best practices to prevent flaky tests involve applying pragmatic workflows and avoiding anti-patterns. The Skill enforces guardrails for mocking patterns and test structure to enable safe refactoring and boost coverage reliability.

How do I improve code coverage across an existing codebase?

To improve code coverage across an existing codebase, apply coverage-oriented workflows and actionable improvement paths for legacy tests. The Skill outlines strategies to boost coverage and prevent brittle tests during refactoring.

Does this testing strategy work for large software projects?

Yes, this testing strategy works for large software projects of all sizes. It applies test-first development guardrails and coverage-oriented workflows to scale robust testing across teams without introducing flaky test anti-patterns.

Why are my unit tests brittle after refactoring?

Unit tests become brittle after refactoring when mocking decisions and test structure lack proper guardrails. The Skill provides anti-pattern awareness and coverage best practices to enable safe refactoring and prevent test fragility.