Home • Corporate • Contacts •

TETware White Paper

Products

Solutions

Information

Datasheet

Documentation

FAQ

Knowledgebase

You are here: TETworks > White Papers > Scenarios

Introduction

As with many terms, scenario means different things to different people in the world of software testing. In TETware we use test scenarios to tell the test case controller which test cases to process and how to process them. The scenarios are stored in a scenario file. The file may contain one or more scenarios, and they may be cross-referenced. The file is written is a simple, but powerful, scenario language.

The scenario language is used to define the scenarios. Each scenario consists of a scenario name, the first word in a scenario, that may be followed by scenario elements. These elements may be simple elements or directives. Comments may also be included to describe the test scenarios and their purpose.

Simple Elements

• the scenario information line, this is text enclosed in double quotes which is printed to the journal file.  It may then be picked up by a report writer or written to a database.
  
• The test case name, with an optional list of invocable components which gives the user the flexibility to select only certain tests from a group of tests
  
• A referenced scenario name, so we can call another scenario from within a scenario.
  
• Include file name, which contains the test case names and the scenario information lines to they don't have to be entered into every scenario file, and a single change will update all our scenarios.
  

Directives

Scenario directives effect the way in which the simple elements are processed by the test case controller.  A directive may have the simple element attached to it, or alternatively if an element is not attached to it subsequent elements will be processed within the scope of the directive until a matching end directive is reached.

Example

The scenario language provides the user with a great deal of flexibility in defining test scenarios, for example, take two instances of a timed loop execute in parallel. In each loop a single test case is chosen at random from the list of test cases. Each loop is repeated until its execution time has exceeded 300 seconds.

This scenario may be defined as follows:

all

:parallel,2;timed_loop,300;random:ˆscen1

scen1

/ts/tc1
/ts/tc2
/ts/tc3

all

:parallel,2;timed_loop,300;random:
/ts/tc1
/ts/tc2
/ts/tc3
:endrandom;endtimed_loop;endparallel:

all

:parallel,2:
:timed_loop,300:
:random:
/ts/tc1
/ts/tc2
/ts/tc3
:endrandom:
:endtimed_loop:
:endparallel:

The different versions of this scenario shown here illustrate how the same scenario may be written with or without the use of directive groups.

When TETware processes this scenario in execute mode, two instances of the timed loop are initiated at the same time. Each timed loop instance iterates until 300 seconds have expired. During each iteration of each loop instance, a single test case is selected at random from the list and executed.

The way in which TETware processes this scenario may be represented by the following diagram:

Conclusion

Reference

For more information please see Chapter 4 of the TETware Programmers Guide.  Click here to download a copy.