Generating Impact Reports on Test Discovery

The Test Discovery Impact Report evaluates the effects of new releases or patch upgrades on your current tests. It categorizes the differences between old and new sessions into distinct forms, codes, DB fields, etc. enabling clear identification of changes. 

This aids in pinpointing specific areas for testing, saving time and costs associated with performing regression tests for each code modification. It also has a self-heal button to heal impacted test cases with a single click.

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

1. Click on the Add Impact option.

2. Enter relevant details on the right panel. Select the two snapshots to be compared and click Create.



3. It will generate the report with a unique ID. Click on the report you want to open. 

4. The report allows you to spot changes in fields, forms, or objects within your ERP application post a release or patch upgrade. These modifications could influence relevant test cases, and the report aids in identifying which cases require revision.

5. The Self Heal button is used to automatically update the affected test cases with the new objects to ensure that your test cases are valid post-upgrade.


6. The Impact Analysis tab allows you to choose test cases, add them to the test suite, and execute them. Access this functionality by clicking the Impact Analysis tab adjacent to the Forms tab.

7. Click the Create Test Suite button. In the test suite window, click the Run button to execute the added test case.

8. Following test case execution, the reports validate whether the impact has been addressed via self-healing or not. This process replaces affected test cases with new ones that work effectively with the updated application.

9. The reports additionally detail the changes made to the application and their effects on test cases. This insight assists in refining the self-healing process and preventing future failures.

You've reached the end of this article and are now well-prepared to generate Impact Reports. 

Ready to dive deeper? Check out the next article: Using ConfigOps for Oracle.

Explore, experiment, and achieve your testing goals on Opkey!

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 atleast one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article