Test Workbench Concepts

The Test Workbench is implemented according to certain concepts and strategies, which are described below.

The Test Case

Test Cases are the core of all testing activities. A Test Case describes an sequence, the consists of one or multiple actions (test steps), a reference to the necessary prerequisites for execution the test and monitoring the expected results.

For simplicity reasons prerequisites and preparation activities are entered as Test Cases in the Test Workbench. A special flag helps to distinguish these Test Cases from others. Such Test Cases are then linked to the succeeding Test Cases, indicating that they depend on them.

The Test Scenario

A Test Scenario describes the execution of a sequence of tasks which are to be tested. Within the Test Workbench a Scenario is made of a sequence of Test Cases. This provides re-usability of the already defined in already defined Test Cases

The Test Case Set

In comparison to a Scenario a Test Case Set may consist of list of any Test Cases, which are not within a specific sequence.

Test Strategy

Due to the special architecture of the Test Workbench, which allows it to keep general information and test execution specific information separate, all Test Cases and Scenarios remain reusable, independent where and how often they have been referred to in test executions

The copy functions the Test Workbench allow the user to use Campaigns, Scenarios and Test Cases as templates or re-use directly.

The simplicity of the Test Workbench enables the user to concatenate Test Cases, to extended test sequences, allows it to describe Test Cases as very simple, short execution steps, which in turn make, in case of an error a one to one relationship between error report and Test Case possible, which is a major requirement of the Test Strategy.

Campaign

A (Test-)Campaign serves as a planing and administration tool for the execution of test runs. The Campaign brings the individual Test Scenarios and the Tester together. Within the Campaign Manager the test execution, once planned and opened for execution, enables the test manager to track the progress of the individual testing phase. depending on the size and amount of work in the project the Test Campaign can stretch across different distances. For big projects the individual development phases or cycles can be managed within a Test Campaign. For small releases a single Campaign may be sufficient.