Documenting user scenarios and measuring/testing
- by Rimian
Please forgive me as I don't quite remember the exact terms for what I am talking about... hence my question.
Recently I worked on a large Agile team where I encountered a method of defining user scenarios (much like user stories).
These scenarios were a few very basic short sentences with keywords and a structure that could be understood by humans (especially project managers) and could also be coded against using some Java Framework (for verifying tests).
The exact structure of this mini language used keywords like "when" and "and" or "if" which was how the framework parsed and verified the result. The purpose of this framework was to interface between management and the acceptance testing framework. So essentially management could write the tests themselves using English.
The scenario went something like this:
"When a user visits URL
and
User clicks on X
Something happens (that can be measured)"
Can anyone help me remember exactly what I am talking about?
Many thanks
