ERP applications, like Oracle Cloud ERP and Salesforce, receive frequent updates to improve functionality. These updates disrupt testing as workflow changes impact existing test cases. With numerous workflows, it's impractical for testers to track and update all affected test cases.
Opkey's impact report analyzes and identifies processes affected by application updates. It compares test mining reports from old and new versions, highlighting changes and affected test objects. With a new ERP release, you can identify change impact by comparing your current testing process with the latest release.
Let’s understand this with a practical scenario.
During the quarterly release of the Oracle application, changes are made to objects in the financial module's receipt form. Testers use change impact analysis to identify affected test cases, adapting or removing them to align with the new release. This ensures testing efficiency and compatibility with the updated application version.
The Self-Heal button provides a one-click solution for repairing impacted test cases. Testers can select affected objects and use Self Heal to automatically repair associated components, ensuring seamless transitions between ERP releases and maintaining testing effectiveness.
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 option.
2. Click the + Impact button at the top to open the Create Discovery Report page on the right.
3. Add the report name, and select your ERP from the given options. Here, we are selecting the Oracle Fusion ERP.
3. 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 be creating an Impact report by comparing snapshots of Payables process in Oracle to identify its changes.4. Choose the milestone and user story of your testing project to link the impact report for project tracking. Once done, click Create.
5. Double-click on the report from the impact report dashboard.
6. In the middle panel, click on the "Show Attribute" icon to open the impacted element of the related object. Here, we are opening attributes of the Receipt process.
7. Here, we can see the forms object is impacted in the receipt process. In the Form tab on the right panel, we can see the color coded impacted object. Red color indicates the object is deleted. Yellow indicates the object is changed. Green indicates the object is newly added.
8. Let's click the dropdown at the top to select an impacted component. We are selecting the Manage receipt element.
9. We can see the delete element has been removed. Click the Self Heal button at the top to repair the impacted test cases due to this change.10. Select the impacted components through the checkbox and click the Heal button at the bottom.
11. Once the components are healed, click the Impact Analysis tab to create a test suite of healed impacted test cases.
12. Here, you can create a test suite of healed impacted test cases and execute them ensure they are repaired and working as intended.
13. You can also review impacted scenarios and associated test cases by selecting the Discovery Snapshot option from the dropdown in the middle panel
.
14. 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.
15. The toggle button in the middle screen enables you to view activities associated with an impacted scenario.
16. In the Similar Scenario tab at the top of the right panel, you can view similar scenario compared to the impacted scenarios. This will help you identify scenarios that may get impacted in future release due to similar changes in the objects.
This brings us to the end of 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
Feedback sent
We appreciate your effort and will try to fix the article