Expertise > Tools > SQS-TEST®/Professional > Test Data Definition

Test Data Definition



Generating executable test data

The goal of Test Data Definition is to generate executable test data such as complete input data for a dialogue or master data files.

With SQS-TEST®/Professional there are three ways to provide test data:

  • They can be imported
  • They can be pre-generated and completed from test cases compiled with Test Case Specification
  • They can be generated manually.

General requirements of test data are:

  • Only as much data as necessary, but as little as possible, should be generated,
  • The data should be complete if possible, i.e. all requirements of the inputs (test cases) in all data structures should be covered.

To create a single test data file, a value must be generated for every element of a data structure, for example for all input fields of an input dialogue and the data fields of a master data file.
Which values must be generated for each element is determined from the previously defined requirements of the test data (test cases.)

If in a data field the inputs "y", "Y", "j" and "J" are to have the same effect, at least one of these inputs must be generated in order to test whether the effect is achieved.

In the case of a possible input of "0-9", it may for example make sense to choose threshold values of "0" and "9", plus a value which lies between 0 and 9. For an error test, wrong inputs (eg. "x" or "-6") can also be taken.

To reduce manual work when recording the input values, there are a series of options available in SQS-TEST®/Professional to allocate values.

Global value allocation
Certain data can be the same in all test files, eg. names or place details. For such elements, the content can be globally preset once (and rewritten locally as required).

Value allocation using references
By means of referencing, elements can take on the values of other elements.
(In this way, master data, such as details on a person, for example, can be filed consistently with dialogue inputs; this is required, for example, if a test involves simulating inputs that access already existing master data.)

Value allocation using variables
Values can be allocated using global, explicitly defined variables. If, for example, an index is used, an element (eg. a counter field) can be assigned successively changed values in the test data.
(In this way, you can generate a code number, for example, for consecutive files - for instance, for a list of participants.)

Value allocation through expressions
Expressions can include values, references and variables as well as a wide range of mathematical calculations.
(Thus, for example, values can be generated in output fields that are calculated from the values of various different input fields.)

Direct, local value allocation
With regard to critical input elements, the values are normally entered directly and locally.
Manual allocation for a specific case (so-called test data combination) overwrites an existing global value allocation.

After the specified values have been allocated, the test data combinations are allocated to the test cases.

A test data combination can consist of one or several test files for structures; the required inputs are combined in such as way as to minimise the number of test data (files). The files belonging to a test data combination can be processed contiguously.

If test data are to be made available for test execution, the test data combinations are allocated to test runs. After that, the test data are supplied physically in the required format.

To execute the input of the test data automatically on the data interface, you can export them to what is known as a Capture/Replay tool that simulates the inputs in the application. This occurs using test procedures controlled by SQS-TEST®/Professional.