Troubleshoting guide for Performance Testing issues

Scenario 1

Issue: The Opkey keyword OracleLT_ThinkTime not capturing the set desired wait time in the load testing test case.

The issue arises when the Opkey keyword OracleLT_ThinkTime is not added in the performance steps before the block whose time tracking needs to be done

Solution: Select a block for which the waiting time needs to be tracked. Search for the Opkey keyword OracleLT_ThinkTime and add it at the beginning of the block.

On the added step, click on the Set Data button.

Edit the data of the step, add the required minimum and maximum values, and save it.

The system will then pick a value within this range and wait for that time.

Scenario 2 -

Issue – Oracle EBS-specific Opkey keywords, OracleLT_StartTransaction and OracleLT_EndTransaction not returning the response time results taken to perform the selected steps.

Solution:

After recording the test steps on the Oracle EBS application, save them in a test case. To add the Opkey keywords OracleLT_StartTransaction and OracleLT_EndTransaction, you will have to switch to view its performance steps.

Click on the Open Performance Steps tab on the recorded test case to view its performance steps.

Expand the steps to view the generated performance steps.

Search for the Opkey keyword OracleLT_StartTransaction and add at the point you want to begin viewing the response time of the steps

Now add the next Opkey keyword as OracleLT_EndTransaction at the point you want to stop reviewing the response time of the steps

Now click to Save the test steps.

The keywords will function when added to the performance steps.

Scenario 3

Issue: Executions for Performance test failing

The saved performance steps are not getting executed/showing an error in the logs when executed.

Solution: After all the data has been saved, Select "Run Performance Test" to run it as a performance test.

Enter the details in the Run Wizard and then execute. The executions will happen seamlessly.