Guides Behavior-Driven Development from discovery conversations to Gherkin scenarios and pytest-bdd or behave automation.
npx skills add https://github.com/Yassimba/loom --skill bdd-yassimba
Please help me install this Agent Skill. Skill: bdd Source: https://github.com/Yassimba/loom/tree/main/skills/bdd Command: npx skills add https://github.com/Yassimba/loom --skill bdd-yassimba
High-intent search queries and answers about installing and using this skill.
Write each scenario as Given context, one When event, and a Then asserting an observable outcome, using domain language with real names, amounts, and dates. Keep scenarios to 3-5 steps, independent of each other, and free of URLs, selectors, or class names.
Choose based on who writes the Gherkin. If developers write it and domain experts review, use pytest-bdd so scenarios run inside the existing pytest suite. If the business writes feature files themselves, use behave, where feature files are the standalone entry point.
A .feature file with no binding silently runs zero tests in pytest-bdd. You must bind scenarios with scenarios() or @scenario in a test module, then confirm the collected test count grew with pytest --collect-only -q.
An undefined step usually means a matcher mismatch: a typo in the step text or placeholder, the wrong keyword decorator, or a use_step_matcher switch earlier in the file. Steps must also live under features/steps/ to be loaded.
Skip Gherkin when the behavior is scaffolding, framework glue, or an implementation still finding its shape. If a scenario reads as a natural-language translation of a technical test, rewrite it in business terms or use a plain pytest test instead.
EnigmaWUGuide Example Mapping workshops to decompose User Stories into Business Rules, Examples, and Questions.
zenobi-usEnforce Test-Driven Development with failing tests before implementation.
ab300819Guides writing and reviewing tests with assertion, coverage, and mutation quality rules.
dhntWrite regression-focused unit tests for uncovered code behaviors.
