The Execute Subprocess step lets you call a subprocess test case as a single step.
This step is used to call a subprocess and receive the outputs. This step is commonly used when a specific function is performed in numerous test cases. For example, if a specific validation always works the same way, you can create a validation subprocess and can add it to different test cases.
For more information, see Building Subprocesses.
Complete the following fields:
Select the subprocess from the pull-down menu.
When the parameters have nested properties, fully expand the properties before sending to the subprocess.
Select to forward cookies to the subprocess.
Get the HTTP cookies from the subprocess.
Specifies the action to take or the step to go to if the test fails because of an environment error.
Default: Abort the test.
The documentation that was entered into the Documentation area of the subprocess is displayed.
The Parameters to Subprocess panel contains a list of the parameters that the subprocess requires. These keys and values must be present in your current test case. Edit the Value column as necessary to supply the correct values.
The Result Properties panel lists all the properties that are produced in the subprocess. Select the properties to be returned from the subprocess. These properties are used in your test case. You are not limited to a single return value.
When this step runs, it appears to run as a single step. The Interactive Test Run (ITR) utility shows the events that fired while the step ran. The short name of the events combines the name of the current step and the name of the subprocess step where the event was fired..
If an assertion is triggered in the subprocess, then the appropriate event appears in the Test Events tab of the Interactive Test Run (ITR) utility.
The default Execute Subprocess step uses the following convention: Subprocess subprocessname. You can change step names at any time.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|