...
Other workflows can be designed and used in the same manner as this one. Create workflow inputs for any options you want to expose to the yaml file. Map the workflow inputs into plugin inputs as groovy values. Activate the workflow. Fill in the values in the yaml file, referencing the workflow input codes.
Prefix the name of your workflow with the one of these values to get When you choose a workflow name, consider including one of the values from the workflow prefix table
Workflow Inputs
Workflow inputs specified in the yaml configuration directly correspond with the inputs as seen in the workflow definition.
...
TEST_INSTANCE is a special workflow input. It’s available values are filtered by the workflow name using the table below.
Anchor | ||||
---|---|---|---|---|
|
If your workflow contains (case insensitively) | Test Instances will be filtered to type |
---|---|
soapui | SOAP_UI |
postman | POSTMAN |
junit | JUNIT |
testng | TEST_NG |
hpt | HP_UFT |
apifortress | API_FORTRESS |
automationany | AUTOMATION_ANYWHERE |
cucumber | CUCUMBER |
jmeter | APACHE_JMETER |
oats | OATS |
salesforce | SALESFORCE |
tricentis | TRICENTIS |
utpl | UTPLSQL |
...