Write and maintain Behavior-Driven Development tests with Gherkin and Cucumber. Use when defining acceptance scenarios, writing feature files, implementing step definitions, running Three Amigos sessions, or diagnosing BDD test quality issues. Keywords: bdd, gherkin, cucumber, given when then, feature files, step definitions, acceptance criteria, three amigos, example mapping.
Does it follow best practices?
Evaluation — 96%
↑ 1.04xAgent success when using this tile
Validation for skill structure
A fintech startup is developing user account management features and needs to create a robust BDD test suite. They've had issues in the past with flaky tests that fail unpredictably and scenarios that work individually but fail when run together as a suite.
The team needs to ensure their test scenarios can run in any order, in parallel, and independently without affecting each other. They want to prevent the technical debt that comes from interdependent tests and ensure reliable CI/CD pipeline execution.
Create the following deliverables:
Create scenarios that demonstrate proper independence and structure.
The following files are provided as inputs. Extract them before beginning.
=============== FILE: inputs/requirements.md ===============