runScript (Oats)
- Karl Henselin
- Perepa Sai Sri Mukhi
Executes an OATS Functional or Load Testing script.
Test Instance Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
runScript Executable Path |
| Yes | Oracle Application Test Suite run script file name (.sh or .bat) with full Path. |
Inputs
Input Name | Input Code | Required | Description |
|---|---|---|---|
Script Project File |
| Yes | Script project file (jwg file) with path. Relative paths will be relative to the |
Arguments |
| No | Arguments to pass to the test. (e.g. -browser.type FireFox) |
Artifacts
This operation consumes .jwg Oracle ATS test artifacts, if available.
Endpoint Selection
This operation delegates endpoint selection to the workflow developer. The workflow editor will default the selection to "All", which selects all available endpoints associated to the Target.Â
Selecting a specific resource will result in selection of endpoints associated to the Target which have that resource defined.
Endpoint Execution
This operation delegates endpoint execution to the workflow developer. The workflow editor will default to "Any", which will execute on any one of the selected endpoints, which will be randomly picked from selected endpoints or a specific endpoint where previous step may have executed. Changing this value to "All" to will result in execution on all selected endpoints.
Special Considerations
This plugin supports Functional and Load Testing scripts. Functional Testing (Browser/GUI Automation) can bring up challenges specifically when executed via Cygwin (SSH). In our testing, we have seen success when Cygwin SSHD and Oracle ATS services are setup as shown below. (Log on as; Local System account with Allow service to interact with desktop checked)
Â
- style