nw-bdd-methodology

Coordinate acceptance testing with Given-When-Then scenarios in pytest-bdd.

Updated Apr 15, 2026

Search Tags:#bdd #antipatterns #acceptance-testing #living-documentation #outside-in #pytest-bdd #scenario-writing

Ready to run

npx skills add https://github.com/StudentCristian/nWave-github --skill nw-bdd-methodology

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: nw-bdd-methodology
Source: https://github.com/StudentCristian/nWave-github/tree/main/.github/skills/nw-bdd-methodology
Command: npx skills add https://github.com/StudentCristian/nWave-github --skill nw-bdd-methodology

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Aligns teams on business goals by using BDD patterns to specify acceptance criteria in Given-When-Then language, decoupled from implementation details.

Core Features & Use Cases

Outer-loop Outside-In TDD guidance to drive tests from user outcomes.
Structured Given-When-Then scenarios with clear rules and anti-pattern avoidance.
Pytest-bdd implementation guidance and living documentation to keep tests aligned with business needs.

Quick Start

Start by writing a simple Given-When-Then scenario in pytest-bdd that captures a real user goal.

Frequently Asked Questions about nw-bdd-methodology

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

FAQPage Schema

How do I write acceptance tests using Given-When-Then scenarios in pytest-bdd?▼

To write acceptance tests in pytest-bdd, you define Given-When-Then scenarios that capture real user goals, ensuring structured scenario design and clear rules that decouple test logic from implementation details. This approach aligns tests directly with business needs.

What are common BDD anti-patterns to avoid when structuring acceptance scenarios?▼

Common BDD anti-patterns emerge when scenarios couple tightly to implementation details rather than observable outcomes. Disciplined BDD guidance helps avoid these pitfalls by enforcing business-focused Given-When-Then language and clear scenario rules that maintain living documentation.

What is outside-in TDD and how does it drive outer-loop acceptance testing?▼

Outside-in TDD drives outer-loop acceptance testing by starting from user outcomes and working inward. This methodology uses business-focused BDD patterns to specify observable acceptance criteria, ensuring that tests remain aligned with overarching business goals throughout development.

Can I use BDD living documentation to organize pytest-bdd test scenarios?▼

Yes, you can use BDD living documentation to organize pytest-bdd scenarios. By applying structured Given-When-Then rules and business-focused patterns, the methodology keeps your acceptance tests aligned with business needs and maintains clear, observable documentation.

Does BDD methodology work for both inner and outer loop testing workflows?▼

Yes, this BDD methodology applies to both inner and outer loop workflows. It coordinates acceptance testing by applying Given-When-Then patterns across the entire development cycle, ensuring observable outcomes and living documentation remain consistent throughout.

When should I not use Given-When-Then patterns for acceptance testing?▼

You should avoid Given-When-Then patterns when tests cannot be decoupled from implementation details or when scenarios fail to capture real user goals. If your testing lacks clear business outcomes, applying BDD anti-pattern guidance becomes ineffective for living documentation.