Organising test execution

SQS-TEST^®/Professional Test Process Automation is designed to control test preparation and execution, and to archive and manage the test results. Tests are organised by executing flow-specific test scripts (jobs), which are generated from test procedures.

SQS-TEST^®/Professional Test Process Automation can be used as the basis for an individual test sys-tem, in which different tools are integrated into a uniform interface. The tester can combine and modify standard flows individually. With the aid of the test procedures, complex test scenarios can be systematically organised, whose separate levels are executed by currently generated jobs.

A test procedure controls a test run to test a test object in its entire flow, for example by:

• Supplying test files with inputs
• Loading test files in the test environment
• Starting the program to be tested
• Starting a Capture/Replay tool with the test file for dialogue inputs
• Saving and archiving the test results
• Supplying test files with inputs
• Comparing test results and attendant target result files
• Saving and archiving the comparison results
• Quitting all jobs and programs
• Deleting all temporary files.

To enable clear and flexible structuring of these separate actions, a test procedure consists of a hierarchically structured sequence of tasks, jobs and steps. A task normally defines a partial goal of the test flow, e.g. test preparation, test execution, test archiving. Within a task, several jobs can be defined. They describe the actions to be carried out successively in order to complete this task, e.g. loading, executing, saving test data. A job consists in turn of one or more steps. A single step is defined in terms of concrete, executable instructions, making use of templates.

These templates contain reusable, standardised instructions (script templates). These are written in the script language that can be executed on the target computer. Individual adjustments can be defined using parameters, whereby values are allocated to the variables used in the templates. These can be stored in separate documents, e.g. in the form of a value chart for variables. Variables can not only be allocated a value in the procedure, they can alternatively be defined as input variables; in this case the value is entered directly before the test script is executed. The control instructions in the procedure for structuring the test flow are defined in a higher, target system independent language. Limited processes, for example (#IF, #FOREACH,...) are possible. From the test procedures an executable test script (job) for each job order is generated for the relevant target system; with the aid of this test script the test processes are automatically executed on the target computer. The information required by the tester can be displayed during execution. Information on the jobs executed, or currently being executed, can be viewed using Job Control.

SQS-TEST^®/Professional Distributed Test Environment - controlling tests in heterogeneous environments
SQS-TEST^®/Professional Distributed Test Environment (DTE) is an extension of SQS-TEST^®/Professional Test Process Automation. SQS-TEST^®/Professional DTE is a tool for automated testing of distributed applications, including applications in heterogeneous client-server systems. It enables a network-wide automatic and coordinated flow control of test procedures using specific sub-jobs (tasks) for the different target computers.

The scope of supply of SQS-TEST^®/Professional includes a sub-functionality that allows execution and checking of sub-jobs on the SQS-TEST^®/Professional server (local tasks). The components required for the execution of sub-jobs on other computers can be purchased additionally for the different target systems.