use deputy
Direct the execution of the following block of action lines to a specified deputy controller.
| Name | Description | Type | Modifier |
|---|---|---|---|
| name | Name of the deputy controller machine (previously established with the connect deputy action). | String | None |
| parallel | (Optional) Mode in which the deputy is to run. Allowable values:
| String | None |
None
This action may be used within the following project items: test modules and user-defined actions.
machine port timeout name
connect deputy 192.168.167.79 53600 5 Deputy 1
connect deputy 192.168.167.116 53600 5 Deputy 2
 
name parallel
use deputy Deputy 1 yes
 
text
report Test run on machine 1
 
name parallel
use deputy Deputy 2 yes
 
text
report Test run on machine 2
 
use lead
 
wait for all deputies
 
name
disconnect deputy Deputy 1
 
disconnect deputy Deputy 2
- The block of action lines following use deputy is lower-bounded by the next use lead or use deputy action. The block is executed exclusively on the machine specified in the name argument.
- This action supports the <ignore> modifier. If the string
<ignore>is present as the value of any of the arguments, or any argument contains an expression that evaluates to<ignore>, the action is skipped during execution. - Parallel execution (parallel = yes) allows the lead controller to continue executing lines (below the block of action lines associated with the use deputy action) concurrently with the deputy. Serial execution (parallel = no) forces the lead controller to wait for the deputy to complete its execution of the block of action lines submitted to it.
- Note that database actions are not supported on machines operating as deputies.
Tel:
Email: