Test Execution - Best Practices and Remedies for Common Errors

After performing test execution in Opkey you can view the results. The results provide a detailed overview of test execution status, date and time of execution, snapshots of executed steps, step details, Debug Info, and more. Test execution results help to analyze data, detect errors in the application before release, fix broken tests, and improve software quality. 

‍

Best Practices of test execution

1. Before executing a test case in Opkey, you have to install the execution Agent. Opkey execution agent is a test execution engine that helps to trigger test cases in your local Windows device. After installing the execution agent, configure it to make sure that it is compatible with your device. 

2. You can also execute test cases on web via Spock agent which is a cloud-based agent. The Spock agent is used if the Opkey local execution agent is unavailable.

3. Make sure the agent is up and running and the server status is set to connect.

1. Ensure that your plugin is installed and updated for the relevant test case. For example, for a test case for Oracle Fusion application, ensure that the Oracle Fusion plugin is installed.
2. While executing make sure the correct plugin is selected, and also make sure that the plugin is having an active license.
   
   
   
3. Ensure there are no syntax errors in your test case. For example, some test steps may require entering test data in a specific format such as entering date in DD-MM-YYYY format.
   
   
4. If the test case is having an empty data set, make sure to uncheck it from executing or skip empty data set option can be selected from the Advance Settings, on the Run Wizard to avoid any failure.
   
   
   
5. In order to make sure that the correct object is being picked up during the execution, the user can select the highlight object checkbox from the Advance Settings tab. This helps avoid assertion errors in test cases meant to verify the existence of some object or element on the test page.
   
   
   
6. Ensure you have a good internet bandwidth and any VPN connection is not blocking the execution.
7. Review the Debug Info tab for a failed test step. The tab contains specific details about what went wrong. Examine any screenshots captured at the time of failure for visual clues.
   
   
8. Re-run the test case to see if the failure is consistent or caused by an internet issue.

Also check details related to 

Getting System.IO.IOException in local Opkey environment while execution

1. Sometimes, the configurations in your application might get changed due to any new update or change. This leads to test cases failing and they need to be updated as per the application changes. In such a scenario, you can use the following process:
   a. Run impact analysis on your test instance with Opkey to create an impact report detailing the impacted test cases.
   
   
   b. Select the impacted object and use the Self Heal button to repair related test cases.
   
   
   c. Add the repaired test cases to a test suite in the impact analysis tab of the impact report and execute them again.