skills.rest
antoinersw
antoinerswCOMMUNITY
Explore all skills by this author →
GitHub

test-craft

Codify BDD and test-pyramid guidelines for unit, integration, and E2E tests.

Updated Apr 12, 2026
Search Tags:#testing#qa#bdd#unit-testing#integration-testing#e2e-testing#test-pyramid
One-click install
npx skills add https://github.com/antoinersw/pbi-versioning --skill test-craft-antoinersw
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-craft
Source: https://github.com/antoinersw/pbi-versioning/tree/main/.claude/skills/test-craft
Command: npx skills add https://github.com/antoinersw/pbi-versioning --skill test-craft-antoinersw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Modern software testing often suffers from flaky, inconsistent tests and unclear guidance on how to structure test suites. This Skill provides a disciplined, craft-focused approach to testing using BDD, AAA/GWT structures, and a practical test pyramid to ensure maintainable quality.

Core Features & Use Cases

  • BDD-driven workflow: Outline Behavior-Driven Design steps (Describe, Implement, Verify, Refactor) to align development and testing.
  • Test Pyramid guidance: Guidance on distributing tests across unit, integration, and E2E layers with real-world samples and anti-patterns.
  • Test doubles, factories & data: Techniques for stubs, mocks, spies, and test data factories for deterministic tests.

Use Case

Imagine a software team migrating from ad-hoc tests to a disciplined suite for a web app, reducing flakiness and accelerating delivery.

Quick Start

Create an initial acceptance test that defines the desired behavior, then iteratively add isolating unit tests and clear test doubles to verify each feature.

Frequently Asked Questions about test-craft

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

FAQPage Schema
How do I reduce flaky tests in my software test suite?▼

To reduce flaky tests, apply BDD-driven workflows with explicit AAA/GWT structures and use test doubles like stubs and spies for deterministic results. This approach isolates behavior verification and prevents inconsistent outcomes.

What is the test pyramid and how do I distribute unit, integration, and E2E tests?▼

The test pyramid distributes automated tests across unit, integration, and E2E layers to ensure maintainable quality. Apply more unit tests at the base, fewer integration tests in the middle, and minimal E2E tests at the top to optimize execution speed.

How do I structure tests using BDD and Given-When-Then?▼

Structure tests using BDD by outlining Behavior-Driven Design steps: Describe the desired behavior, Implement the code, Verify with isolating unit tests, and Refactor. This workflow aligns development with testing through clear Given-When-Then specifications.

When should I use test doubles and factories in integration testing?▼

Use test doubles like mocks and spies, alongside data factories, during integration testing to isolate dependencies and generate consistent test data. This prevents external side effects and ensures your tests remain deterministic.

What are common testing anti-patterns for a web application?▼

Common testing anti-patterns include over-reliance on slow E2E tests, improperly isolated integration tests, and misconfigured test doubles. Following test pyramid guidance and BDD structures helps avoid these issues and reduces overall flakiness.

Related Skills

Explore More Software Engineering Skills→
pingwupingwu
12

test-first-development

Generate BDD/Gherkin feature files and TDD test scaffolding before coding.

Community
Intermediate
BarryrnBarryrn

testing

Codify a scalable testing strategy across unit, integration, and E2E layers.

Community
Basic
Omar-ObandoOmar-Obando
44

testing-strategy

Design testing strategies with coverage targets and CI/CD quality gates.

Community
Intermediate
pacphipacphi
6

test-automation-strategy

Design test automation frameworks with pyramid distribution and CI/CD integration.

Community
Advanced