A scenario represents an acceptance test.

A scenario should represent an end user's expectation of the behavior of the application. Thus, it should focus on the intent (what is to be achieved) as opposed to the mechanics (how to achieve it). Scenarios are intended to be long-lived test assets. Hence, it is important to write scenarios without coupling them to the user interface of the application under test. A good way to express the intent would be to describe the requirements or goals of the test, rather than expressing, say, UI level interactions.

If you are using user stories for development, then a user story would typically be associated with one or more Twist scenarios. A logical piece of functionality can be associated with one or more scenarios.

A scenario typically has two types of elements

• A Business Workflow
• A Business Rules Tables