SOAtest tests for automated testing are associated with the SOAtest Test Executor component type. These tests are executed after provisioning and custom health checks are completed.
A single SOAtest Test Executor can run any number of test scenarios. Only one SOAtest Test Executor can be added to a single system or environment.
Configuring a SOAtest Test Executor
To configure a SOAtest Test Executor:
Ensure that your environment has a SOAtest Test Executor component. SOAtest Test Executor components are added at the system level. Only one SOAtest Test Executor component can be added per system; once you add it, it will be removed from the Component Types (palette) tray. It does not need to be connected to other components.
At the environment level, create a new Component Instance for the SOAtest Test Executor.
In the Test Scenarios wizard page, enter a name and (optional) description for this component.
In the lower part of the page, specify which test scenarios you want to run, in what order, and with what variables and data sources. To add a scenario, use the test scenario selector, which lets you add specific scenarios or all scenarios on a particular SOAtest server. You can use the search bar to filter the list contents. The search functionality covers .tst names as well as associated metadata (environment variables, environment names, data sources, etc.). Note that the same test scenario can be added multiple times with different data groups and/or variable settings.
Configuration Tips
Specifying test execution settings: The Execute tests setting determines in what order test scenarios are sent to SOAtest and whether they are run sequentially or in parallel.
- Alphabetical sends test scenarios in alphabetical order and executes them sequentially.
- Ordered sends test scenarios in the order specified here and executes them sequentially. You can reorder tests by dragging and dropping them to the desired positions. This option also generates a separate report for each test scenario.
- Parallel sends the test scenarios unordered and executes them in parallel. How many test scenarios can be run in parallel depends on the number and capability of SOAtest servers in use. See Deploying the SOAtest and Virtualize Server WAR File for more information.
Configuring additional options: To see additional configurable options for a test scenario (such as data groups you can activate or SOAtest environment variables you can modify), click the arrow to the right of that scenario’s name.
Specifying test variable mappings: If a test scenario has variable sets defined, they will automatically be configured to use the existing values. Alternatively, you can specify literal values, use the values of variables defined in CTP, or use whatever value is active in the .tst at the time of the test. If you want to modify the variable mapping for this test job, see Configuring Variable Mappings.
Specifying data groups: Specify which of the available data sets you want to be active for each test scenario with data groups.
Specifying environments: By default, each scenario will be added with the variables from the active variable set (also known as a SOAtest environment). If you want to control what set of variable set is added with each scenario, hover over the .tst name, click the Environments link that appears...
then click the Add link for the variable set(s) you want to add.
The green ball icon marks the variable set that is currently active for the given test scenario (on the SOAtest server).
- In the Variables page, confirm that all variables are set as expected, then click Finish.
- This variable mapping table lists all variables associated with this component instance—including any variables previously associated with this component and any variables that will be added to represent SOAtest .tst environment variables (as set in the previous wizard page). For details, see Working with Variables.
- If you want to change a variable value, check Override, then specify the new value in the text field.
Launching Tests Upon Provisioning
If an environment includes a SOAtest Test Executor, the associated tests will be executed as the final step in the provisioning process (after any customized health checks are executed). Test scenarios within the same component instance will run in parallel if they are hosted on separate SOAtest servers.
Provisioning without Launching Tests
If you want to provision a test environment without running any of the tests associated with the SOAtest Test Executor, set the SOAtest Test Executor component to No Selection before the environment is provisioned.
If you want to disable text execution for all subsequent environment provisionings, you can remove the SOAtest Test Executor from the environment.
