Just as Test-Driven Development (TDD) goes from a failing test, to a passing test, to refactoring,
scenario development proceeds the same way.
We pick a scenario, then implement the fixtures just enough to see the scenario fail.
Then we implement the desired behavior, either via TDD or by implementing it directly.
When the scenario passes, we can refactor more, then tackle the next scenario, until the story is done.
This "two-level" style (using both scenarios and TDD)
is often called Acceptance-Test Driven Development
it is a common (but not mandatory) approach to BDD.
||use this markup:
(Supported languages: java, cpp, csharp, c, python.)
|a method or class name