Dashboard > GreenPepper Open Documentation Refactoring > ... > 5. Scenario specification > Scenario definition
  GreenPepper Open Documentation Refactoring Log In View a printable version of the current page.  
  Scenario definition
Added by Francois Denommee, last edited by Francois Denommee on Nov 24, 2009  (view change)
Labels: 
(None)

Definition

DEFINITION

The ScenarioInterpreter is used to express interactions with the system under development that must be performed in a particular order. This form of specification provides information about the business flow.

When a sequence of action is executed, confirms that each action has successfully been performed.


Scenario Identification of the set of rule
Action 1
Action 2
...
Action i

  • As for all other interpreters, the first row of the ScenarioInterpreter specifies the name of the interpreter and the name of the sequence of actions to be tested. What makes the ScenarioInterpreter particular is that it only have to be defined once for all the sequences of actions expressed in a page. Obviously, the ScenarioInterpreter must be define before any sequence of actions.
  • The ScenarioInterpreter may also be expressed in Bullet List form or Number List form.

Coloring

will visually show the test result by coloring a complete row or words inside the row:

GREEN

When the action has been executed successfully, color the row or words inside the row in green.

RED

If the action execution has failed, color the the row or words inside the row in red.

YELLOW

If the system encounters an execution error, the row is colored yellow and provides information about the error.

GRAY

When the action has been executed successfully, will display the returned value in gray.

DEMONSTRATION LICENSE - This Confluence site is for demonstration purposes only. Evaluate Confluence today.
Powered by Atlassian Confluence, the Enterprise Wiki. (Version: 2.4.3 Build:#705 Mar 21, 2007) - Bug/feature request - Contact Administrators