User stories
In agile teams, requirements are usually expressed as user stories: short descriptions of the value a user needs. The common format is: 'As a [role], I want [action], so that [benefit]'.
Como cliente registrado,
quiero restablecer mi contraseña por correo,
para recuperar el acceso si la olvido.User story example
Acceptance criteria (Gherkin)
Acceptance criteria define when a story is 'done'. A widely used format is Gherkin: Given (context) / When (action) / Then (expected result). These criteria are a goldmine for QA: each one is almost a test case.
Dado que estoy en la pantalla de login
Y he solicitado restablecer mi contraseña
Cuando introduzco un correo registrado
Entonces recibo un email con un enlace de restablecimientoAcceptance criterion in Gherkin style
What structure does Gherkin follow?
In a Gherkin acceptance criterion, what does the 'Then' clause express?