skills.rest
jmreicha
jmreichaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

testing

Guide teams to choose TDD or BDD based on change scope.

3|1|Updated Dec 17, 2013
Search Tags:#workflow#testing#TDD#red-green-refactor#BDD#given-when-then
One-click install
npx skills add https://github.com/jmreicha/configs --skill testing-jmreicha
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: testing
Source: https://github.com/jmreicha/configs/tree/main/skills/testing
Command: npx skills add https://github.com/jmreicha/configs --skill testing-jmreicha

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides when and how to use Test Driven Development (TDD) and Behavior Driven Development (BDD), and how to switch between them while iterating quickly.

Core Features & Use Cases

  • Help teams decide between TDD and BDD based on scope and stakeholder needs.
  • Provide a repeatable workflow for switching between TDD and BDD during feature development and refactoring.
  • Align tests with both internal behavior and user-visible workflows to speed feedback and ensure acceptance criteria.

Quick Start

Use the Testing skill to determine whether to start with a TDD Red-Green-Refactor loop or a BDD Given-When-Then scenario for a new feature.

Frequently Asked Questions about testing

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

FAQPage Schema
How do I choose between TDD and BDD for a new feature?▼

Choosing between TDD and BDD depends on change scope and stakeholder needs. Use TDD Red-Green-Refactor for internal logic, or BDD Given-When-Then scenarios to align tests with user-visible behavior and accelerate feedback.

What is the best way to switch between TDD and BDD during refactoring?▼

To switch between TDD and BDD during refactoring, apply a repeatable workflow that transitions from Red-Green-Refactor loops to Given-When-Then scenarios. This aligns internal logic validation with user-visible behavior as requirements shift.

When do I need BDD Given-When-Then scenarios instead of TDD?▼

You need BDD Given-When-Then scenarios when validating user-visible behavior and ensuring acceptance criteria are met. TDD Red-Green-Refactor loops are better suited for iterating quickly on internal logic during feature development.

Can I use TDD Red-Green-Refactor loops for bug fixes and shifting requirements?▼

Yes, you can use TDD Red-Green-Refactor loops for bug fixes and refactoring when requirements shift. This approach enforces fast feedback cycles while iterating on internal logic and adapting to changing feature scopes.

Does this testing workflow support both internal logic and user-visible behavior?▼

Yes, this testing workflow supports both internal logic and user-visible behavior. It guides teams to select and apply TDD or BDD based on change scope, aligning tests with both aspects to speed feedback and ensure acceptance criteria are satisfied.

What are the limitations of switching between TDD and BDD during feature development?▼

Switching between TDD and BDD requires aligning test strategies with change scope and stakeholder needs. Limitations arise when requirements shift rapidly, requiring a repeatable workflow to maintain fast feedback loops across internal logic and user-visible behavior without disrupting development.

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
YunosukeYoshinoYunosukeYoshino

tdd-workflow

Enforce red-green-refactor loops and prevent skipped tests in unit test workflows.

Community
Intermediate
takusaotometakusaotome
5

tdd-developer

Guide Test-Driven Development through red-green-refactor cycles with failing tests and minimal code.

Community
Intermediate
RyoMurakami1983RyoMurakami1983
2

tdd-standard-practice

Standardize a Test-Driven Development workflow using test lists and the Red-Green-Refactor cycle.

Community
Advanced