Design and review BDD integration tests with Given/When/Then scenarios.
npx skills add https://github.com/popoffvg/dotfiles --skill bdd-tests
Please help me install this Agent Skill. Skill: bdd-tests Source: https://github.com/popoffvg/dotfiles/tree/main/skills/bdd-tests Command: npx skills add https://github.com/popoffvg/dotfiles --skill bdd-tests
Provides a structured guide to design and review integration and end-to-end tests using Behavior-Driven Development (BDD), ensuring scenario clarity, repeatability, and language-agnostic applicability.
Draft a new Given/When/Then scenario for your service, focusing on isolation, clear outcomes, and explicit assertions.
High-intent search queries and answers about installing and using this skill.
BDD testing structures integration and end-to-end tests using Given/When/Then scenarios to define clear acceptance criteria. This notation isolates test steps, maps scenarios to concrete implementations, and ensures deterministic verification across services without relying on implementation details.
To write deterministic BDD test scenarios for asynchronous services, structure steps using Given/When/Then notation while applying asynchronous patterns and test isolation. This ensures repeatable end-to-end tests by enforcing explicit assertions and avoiding anti-patterns like relying on implementation details or shared state.
Yes, you can use BDD scenarios for integration testing across different programming languages. This approach is language-agnostic, focusing on behavior-driven development principles like test isolation, clear assertions, and step notation to verify services independently of specific implementation details or frameworks.
Common BDD testing anti-patterns in e2e tests include leaking implementation details into scenarios, failing to enforce test isolation, and writing non-deterministic steps. Avoid these by structuring Given/When/Then scenarios with explicit assertions, clear acceptance criteria, and isolated verification across all services.
Choose BDD scenarios over standard automated testing when you need structured, behavior-driven validation for complex integration and e2e tests. BDD provides clear acceptance criteria, scenario repeatability, and language-agnostic applicability, making it ideal for teams requiring isolated, deterministic test verification across multiple services.
LucasMalessaCreate isolated git worktrees with automated setup and baseline test verification.
wuzinongTransform user stories and acceptance criteria into executable Gherkin BDD scenarios.
Imad-OuteDesign BDD-style acceptance test suites from user-defined criteria.
LusciiOrganize Gherkin feature files for Terraform modules into docs/features with kebab-case naming.
