You maintain test configurations in the test configuration editor.
A test configuration contains a reference to a test script. It can contain a reference to one system data container and references to several test data containers, but need not have any.
You can download a test configuration as an XML file.
The test configuration references the import part of the data interface of the test script. You can enter test data manually to create variants. Additionally, you can use variants from the test data containers that you reference.
There is at least one default variant called ECATTDEFAULT. This contains parameter values that are used if the corresponding values in the variants are not filled and no corresponding values exist in the default variant of the relevant test data containers.
The diagram shows how a test configuration can reference fields in two test data containers, TDC1 and TDC2. The references are not direct, but are made through aliases. <NAME> is the name of the parameter in the test data container. <VARIANT> is the name of the variant in the test data container. The easiest way to create a variant is to attach a variant from a test data container. Only the parameters that match by name are appended. However, you can build up variants from several different test data containers. Not all options have the “same name” restriction.
References to a value in a test data container are usually displayed in the form <name> ( <alias> , <variant> ). You can toggle between this form and the actual value by using . From the above example, P4(A2, Var1) would be displayed as 6.
As with test data containers, variants can be stored as external variants in TXT or XML files. Use Edit ® Variants ® Upload and Edit ® Variants ® Download to respectively upload and download the variants. For more information, see External Test Data (External Variants).
You can choose to simulate the version selection process. This enables you test that the versioning data is correct by seeing which version is selected for the specified target system. For more information, see Version Management for Test Scripts.
Objects referenced from the test configuration might also be used in other objects. You can find out what is used where before editing the referenced objects. For more information, see Where-Used List.