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
Your team is building a new e-commerce platform for a mid-sized retailer that currently only has a physical store presence. The business stakeholders have expressed concern about cart abandonment rates they've observed in competitor analysis and want to ensure their checkout process is intuitive and reliable.
The product manager has gathered requirements from customer interviews indicating that users want clear confirmation of their actions, transparent pricing, and the ability to modify their cart during checkout. The QA team has identified that previous digital projects suffered from unclear acceptance criteria that led to rework during testing phases.
Create the following deliverables:
The feature file should cover the core checkout scenarios that a business stakeholder could review and understand without technical knowledge.
The following files are provided as inputs. Extract them before beginning.
=============== FILE: inputs/business-requirements.md ===============