Test a Rest Execution to Identify failing TAR tests in Developer Studio tool¶
Execute Connected TAR feature is to facilitate, developers to test their changes against the affected TAR scripts at the development time. Product application developers who do the changes to application code, which might affect the existing TAR scripts due to their changes. This feature is for developers to test their changes in advance in Developer Studio tool before they merge the change into repository.
Test A Rest Configuration¶
- Developer needs to configure TAR environment details in the project properties. First developer needs to add the TAR database under the "Oracle Databases" and click “OK”.
- Open the project properties and under the "Test-A-Rest". Developer should complete below fields before executing.
· TestARest.exe Path
· Test server
· TAR database that added previously (in order to select the TAR database, the developer needs to add the specific TAR database through the "Oracle Databases" panel, first)
Generate and Deploy to TAR Environment¶
In order to Execute Connected TAR Scripts option, developer should deploy the changed files to the specific TAR database.
Invoke File deployment to the TAR server¶
- From the code editor -> RMB and select “Generate and Deploy to TAR Environment”
- From the navigator -> RMB and select “Generate and Deploy to TAR Environment”
Generate and Deploy to TAR Environment Output¶
The status of the deployment of files to the TAR database will be displayed in the “Deployment Summary” panel.
Execution of "Execute Connected TAR Scripts"¶
After the deployment of changed file to the TAR server, developer would be able to run the TAR tests.
Invoke Execute Connected TAR Scripts¶
- From the code editor -> RMB and select “Execute Connected TAR Scripts”
- From the navigator -> RMB and select “Execute Connected TAR Scripts”
Execute Connected TAR Scripts Output¶
The test summary per file will be displayed in the “TAR Execution Summary” panel. For each individual file, the TAR execution log panel will be created separately. Clicking on the hyperlinks will take developer to the respective log folder, log file and the created temporary test collection (.MKD file).
