nw-bdd-methodology

仓库创建 2026年2月13日最近提交 1 个月前SkillHot 收录 22 天前

▸ 精选理由

把BDD实践落地为可执行场景和示例，适合构建可维护的验收测试。

这个 Skill 做什么

提供BDD场景写法、反模式与pytest-bdd实现的验收测试设计指南。

给出可落地的 BDD 场景写法、反模式和 pytest-bdd 的实现建议，教你用 Given-When-Then 把业务验收变成可执行测试。适合做 acceptance tests、从用户视角驱动开发（Outside-In）或想把测试当作活文档时使用。重点是让场景既可读又可跑，避免实现细节污染验收层。

▸ 展开 SKILL.md 英文原文

BDD patterns for acceptance test design - Given-When-Then structure, scenario writing rules, pytest-bdd implementation, anti-patterns, and living documentation

开发编程BDD验收测试场景驱动通用

586

Stars

Forks

仓库内 Skill

+16

7 日增星

安装 / 使用

给你的 Agent 一句话（通用）

帮我安装这个 skill：https://raw.githubusercontent.com/nWave-ai/nWave/main/nWave/skills/nw-bdd-methodology/SKILL.md

或 curl 直取 SKILL.md

curl -fsSL "https://raw.githubusercontent.com/nWave-ai/nWave/main/nWave/skills/nw-bdd-methodology/SKILL.md"

SKILL.MD 节选查看完整文件 ↗

# BDD Methodology for Acceptance Test Design

## Core Philosophy

Test units of behavior, not units of code. Acceptance tests validate business outcomes through public interfaces, decoupled from implementation.

## Outside-In Double-Loop TDD

The acceptance-designer creates the outer loop of Outside-In TDD. Development starts from user perspective, drives inward.

**Outer loop (acceptance/BDD)**: Hours to days | User perspective, business language | Defines "done" | Scenarios describe user goals and observable outcomes, not internals | Failing outer-loop test is the starting signal for implementation

**Inner loop (unit/TDD)**: Minutes | Developer perspective, technical terms | Software-craf

via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有