Self Healing feature of Opkey's Test Discovery

ERP applications like Oracle Cloud ERP and Salesforce receive frequent updates to enhance functionality. These updates can disrupt testing since changes in workflows affect existing test cases. Due to the numerous workflows involved, it is impractical for testers to track and update all impacted test cases. 

Opkey's impact report identifies processes affected by application updates by comparing test mining reports from old and new versions. This highlights changes and impacted test objects, allowing you to assess the change impact with each new ERP release. 

Let’s understand this with a practical scenario. 

During Salesforce application releases or updates, changes are applied to objects within its modules. Testers perform change impact analysis to identify impacted test cases, adjusting or eliminating them to align with the new release. This approach ensures efficient testing and compatibility with the updated application version. 

The Self-Heal button offers a quick solution to repair impacted test cases, automatically fixing affected components and ensuring smooth transitions between ERP releases. 

Now, let's explore how to generate an impact report and understand its features. 

1. Hover over the Impact section and click on the Impact Report option. 
 
 

 

 

2. Click the + Impact button at the top to create a new Impact Report. 

 

 

 

3. Add the report name and select your ERP from the given options. Here, we are selecting Salesforce. 


 

4. The Compare Snapshots option compares snapshot reports of any process in your application. The Release Snapshot option lets you compare your current ERP version with the latest ERP release. Here, we will create an Impact report by comparing snapshots of Lead to Opportunity in Salesforce to identify the changes after an application updateSelect the snapshots to be compared and click the Create button. 

 

 


The created report can be seen in the dashboard. Double-click on it to open. 

 

Here, we are opening attributes of the Asset Process. In the middle panel, click on the "Show Attribute" icon to open the impacted element of the related object. 

 

 


Here, we can see the form object is impacted in the Asset process. In the Forms tab on the right panel, we can see the color-coded impacted object. Red color indicates that the object is deleted. Yellow indicates the object is changed. Green indicates the object is newly added. 


 


Let's click the dropdown at the top to select an impacted componentHere, we’ll select All. 

 

 


We can see the deleted element has been removed.  


 


Click the Self Heal button at the top to repair the impacted test cases due to this change. 

 

 

 

Select the impacted components through the checkbox and click the Heal button at the bottom 

 

 


Once the components are healed, a message will be displayed at the bottom.  

 

 


Click the Impact Analysis tab to create a test suite of healed impacted test cases.  


 


You can also review impacted scenarios and associated test cases by selecting the Discovery Snapshot option from the dropdown in the middle panel. 

 

 


Zoom in to the middle screen to see details of impacted scenarios associated with any object. You can also view impacted test cases associated with a scenario on the right panel. 

 

 

 

 

The toggle button in the middle screen enables you to view activities associated with an impacted scenario. 

 

 

In the Similar Scenario tab at the top of the right panel, you can view similar scenarios compared to the impacted scenarios. This will help you identify scenarios that may get impacted in future releases due to similar changes in the objects. (In this report there were no similar scenarios found, hence it is blank).  

 

 

With this, we end this article. 

 

 

 

 

 

 

 

 

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article