skills.rest
fredericvilcot
fredericvilcotCOMMUNITY
Explore all skills by this author →
GitHub

test-craft

Implement Behavior-Driven Development testing principles with test doubles and edge case coverage.

13|Updated Jan 28, 2026
Search Tags:#testing#refactoring#integration testing#unit testing#test doubles#e2e testing#bdd
One-click install
npx skills add https://github.com/fredericvilcot/clean-claude --skill test-craft
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-craft
Source: https://github.com/fredericvilcot/clean-claude/tree/main/.claude/skills/test-craft
Command: npx skills add https://github.com/fredericvilcot/clean-claude --skill test-craft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers write better, more maintainable, and more effective tests by adhering to Behavior-Driven Development (BDD) principles and established testing methodologies.

Core Features & Use Cases

  • BDD Workflow Guidance: Provides a clear structure for defining and implementing tests based on behavior.
  • Test Structure Patterns: Demonstrates Arrange-Act-Assert (AAA) and Given-When-Then (GWT) for organizing test logic.
  • Test Pyramid Strategy: Explains the balance between unit, integration, and E2E tests.
  • Test Doubles & Factories: Guides on using stubs, mocks, spies, fakes, and factories for robust test data.
  • Edge Case Handling: Emphasizes testing error scenarios and boundary conditions.
  • Organization & Anti-Patterns: Offers best practices for file structure, configuration, and common pitfalls to avoid.

Quick Start

Review the provided documentation on Behavior-Driven Testing principles and apply them to the current codebase.

Frequently Asked Questions about test-craft

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

FAQPage Schema
How do I structure BDD tests using Given-When-Then patterns?▼

BDD testing structures test logic using Given-When-Then (GWT) or Arrange-Act-Assert (AAA) patterns to define behavior clearly and ensure maintainable, reliable test suites.

What is the right balance between unit, integration, and E2E tests?▼

The test pyramid strategy balances unit, integration, and E2E tests to optimize software quality assurance, ensuring comprehensive coverage without creating brittle test suites.

When should I use test doubles like stubs, mocks, spies, and fakes?▼

Use test doubles like stubs, mocks, spies, and fakes to isolate components during testing and leverage test factories for robust data generation across various testing scenarios.

How do I handle edge cases and error paths in integration testing?▼

Handle edge cases and error paths in integration testing by emphasizing boundary conditions and error scenarios, adhering to best practices to avoid common testing anti-patterns.

What are common testing anti-patterns to avoid for maintainable test suites?▼

Common testing anti-patterns to avoid include poor test organization, improper file structure, and mismanaged configuration, which reduce test suite reliability and maintainability.

Can I use test factories for data generation in unit testing?▼

Test factories can be used for data generation in unit testing to create robust test data, working alongside test doubles to ensure comprehensive edge case and error path coverage.

Related Skills

Explore More Software Engineering Skills→
dljsjrdljsjr

test-driven-development

Guide teams in applying TDD and BDD with a double-loop workflow.

Community
Advanced
LuminairPrimeLuminairPrime
1

pytest-coverage

Run pytest with coverage and generate annotated reports of untested lines.

Community
Intermediate
schalkneethlingschalkneethling
7

frontend-security

Audit frontend codebases for security vulnerabilities and anti-patterns.

Community
Basic
gztcodegztcode

test-driven-development

Enforce a RED-GREEN-REFACTOR cycle by writing tests before implementation in Python.

Community
Intermediate