tdd
Develops with TDD driven by BDD scenarios (Given/When/Then), writing only the functional, regression and unit tests that protect real behavior. Use when implementing a feature, fixing a bug, or when asked for tests, TDD, BDD, regression tests or coverage.
- License 许可
- GPL-3.0
- 最近更新
- 2026-11-12
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- tdd
- description
- Develops with TDD driven by BDD scenarios (Given/When/Then), writing only the functional, regression and unit tests that protect real behavior. Use when implementing a feature, fixing a bug, or when asked for tests, TDD, BDD, regression tests or coverage.
02 资源文件 2
- 参考文档references/examples.md1.8 KB
- 参考文档references/writing.md1.1 KB
03 SKILL.md 正文
Scenario-driven TDD
Every test protects a behavior someone would notice if it broke. A few right tests are worth more than many obvious ones.
1. List the scenarios before the code
Scenario: <behavior, in the words of whoever uses it>
Given <initial state>
When <action>
Then <observable result>
If the requirements or the plan already list the scenarios, use those. Otherwise cover only the main path, the boundary of each rule (the value that passes and the one that fails) and each error the user sees, and for a new or ambiguous task show the list to the user before going on. For a bug, the scenario is the bug.
2. Pick one level per scenario
- Functional (default): through the public entry point (CLI, API, exported function).
- Unit: pure logic with many branches, where a functional test cannot reach.
- Regression: every fixed bug gets a test that failed before the fix.
3. Red, green, refactor
One scenario at a time:
- Write the test and run it. It must fail for the expected reason (an assertion, not a compile error). If it passes on the first run, review it.
- Write the least code that makes it pass.
- Refactor with the suite green and run it again.
Never change an existing test just to make it pass. If the expected behavior changed, say so.
4. Write the test
Every test must have three blocks, in this order and once each:
// Given (setup) prepare the state
// When (run) one single action
// Then (assert) check the observable result
Tests must be simple: no if, loops or logic of their own, little setup and a
single action. If a test does not fit that (huge setup, many mocks, several
actions), the problem is usually the code: propose simplifying the design
(see the design-principles skill) instead of complicating the test.
Before writing, read references/writing.md (rules and what not to test)
and references/examples.md (examples per language).
Follow the project's test conventions (AGENTS.md, CLAUDE.md, existing
tests). Do not add a BDD framework if the project does not use one.
When done
Run the whole suite and answer in a few lines: scenarios covered and at which level, what you chose not to test and why, and the suite result.
04 同仓库更多 Skills
{name=null}
Describe what {name} does and when the agent should use it
security-audit
Audits code for exploitable security problems (injection, broken access control, leaked secrets, unsafe input handling, vulnerable dependencies) and reports only verified findings with severity and fix. Use when asked for a security review or audit, before a release, or when a change touches authentication, permissions, secrets, user input, file paths, commands or network calls.
requirements
Turns a request or idea into clear, testable requirements, with scope, user stories and Given/When/Then acceptance criteria. Use when starting a new feature or project, when a request is vague, or when asked for requirements, user stories, acceptance criteria or a feature spec.
refactoring
Restructures existing code without changing its behavior, in small steps with the tests green after each one. Use when asked to refactor, clean up, simplify, rename, extract, move or reorganize code, or to work on items recorded as "Refactor later".
implementation-plan
Turns requirements into a short implementation plan of small, verifiable steps, each with the files it touches and the test scenarios it covers. Use after requirements are clear and before coding, or when asked to plan, break down or estimate a change.
git-workflow
Creates branches, small Conventional Commits and pull request descriptions, safely. Use when committing, writing a commit message, creating a branch, pushing, opening or describing a pull request, or resolving a merge conflict.