A variable set (called an "environment" in SOAtest) is a collection of variables that can be referenced within fields of your test scenario. For example, you might want to have the WSDL, host, and port point to different values for different test environments. When you specify these settings with variables (rather than hard-coding them in the tests), it is much easier to reuse the same test scenario across multiple environments.
If a .tst uses variable sets, you can specify how they are set within a specific Environment Manager component instance or test job. For example, you can have a single component instance or test job run the same .tst multiple times— each time with different variable settings.
|Active from .tst
|Uses whatever value is active for the test scenario (on the SOAtest server) at the time of test execution.
|Uses the literal value specified in the text field.
|Uses the selected variable from the current Environment Manager environment. Not applicable to test jobs.
|Uses the variable specified in an Environment Manager component—either the one you are creating/editing here, or another one in the same environment. Not applicable to test jobs.
If Component (this) is selected, a new component instance variable will be created and used to determine the variable value. This way, you can use Environment Manager variables to set SOAtest environment variables—without going to the SOAtest UI. One variable will be created for each unique variable/value pair. For instance, if you have 6 test scenarios that use the WSDL SOAtest variable, and they are all set to the same WSDL value, one component instance variable will be created. If 2 of those test scenarios use one WSDL value and 4 others each use a different WSDL value, 5 component instance variables will be created: WSDL, WSDL_1, WSDL_2, WSDL_3, and WSDL_4.
For details on defining variables at the system, environment, component, or component instance level, see Working with Variables.
Confirming Variable Values
This section applies when you are adding SOAtest Test Executor components or custom health checks to an environment; it is not applicable to defining test jobs for on-demand execution.
In the Variables wizard page, you are presented an aggregation of all variables associated with the component instance—including the ones that were added to represent SOAtest environment variables (as described above).
If you want to change a variable value, check Override, then specify the new value in the text field.