Testing BDD

Overview

Use this skill to encode requirement intent as executable behavior scenarios that product, QA, and engineering can all review.

Scope Boundaries

• Use when behavior semantics need alignment across stakeholders before or during implementation.
• Typical requests:
  • Turn ambiguous requirements into Given-When-Then scenarios.
  • Align PO, QA, and engineering on acceptance behavior.
  • Define executable acceptance evidence before release.
• Do not use when:
  • The primary task is load/performance benchmark design (performance-*).
  • The task is operational monitoring/alert policy (observability-*).

Inputs

• Requirement candidates and acceptance concerns
• Domain language and business rules
• Existing test policy and release constraints