Impact Analysis for Veeva application


Test Discovery mines your ERP application’s configuration logs and existing test cases to outline its configurations, data, activities, and shows areas lacking test coverage in a Snapshot report. It also suggests test cases to address these gaps. 

 

This information assists in making informed business decisions, such as: 

  • Identifying missed testing scenarios. 
  • Prioritizing test cases that need attention to maximize test coverage. 

 

After mining your ERP instance, Discovery creates a test mining snapshot. We can create snapshots for our different versions of our application and compare them to create an Impact analysis report. The impact report gives details on impacted objects and the related test cases by comparing the old application version with its new updated version. It also has a self-heal feature to fix impacted objects and their test cases. 

Let's see how to generate snapshots and then how to compare them to create an impact analysis report.

 

1. To add a snapshot, log in to your Opkey account, hover over the ‘Discovery’ tab on the left panel, and click on the Snapshot option. 

 

 


2. Click on + Snapshot button and add a new instance. 
 
 

 

 

3. A new page opens on the right, here, add details such as name of Snapshot report and choose your ERP for test mining from the given option. 

Here we are selecting Veeva Vault application.  

Click the + instance icon adjacent to the Instance field. 

 

 


4. Next, add credentials of your ERP environment and create its instance on Opkey. Test discovery will use this instance to connect with your ERP environment and mine your testing process.  

 
Here, add the name and URL of your ERP instance in the respective fields. Next, fill in your user credentials for your ERP, and click + Add button. 

 

 


The instance gets created. 


 

5. Next, select the Attribute, Process, Start and End Date, Time zone.  Click Analyze. As we are creating this snapshot for an previous application version, make sure to select the start and end date before the application was updated. 


 


The test mining process begins.
 

  


6. When the mining is completed, click on the Open Snapshot link on the next page. You will be able to see the snapshot.

 
7. Similarly, create a snapshot for the current version of the application.



Now, let's move to create an Impact report using these snapshots.


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 Veeva from the given options. 



4. Select the Compare Snapshots option as we will be creating Impact report by comparing snapshots of your application. The Release Snapshot option lets you compare your current ERP version with the latest ERP release.



5. Choose the milestone and user story of your testing project if you want to link the impact report for tracking in any of your projects planned in QLM. Once done, click Create.


6. Once the report is created, double-click on the report from the Impact Report dashboard to open it.



7. In the report, you can see the list of compared objects in the left panel. You can select an object and see its impacted elements in the dropdown on the right panel. 



8. In the right panel, you will also find the list of compared object elements. For impacted objects, you can click the Self heal button and it will enable you to fix the impacted objects.


9. In the fields tab, you can see the comparison of old and new fields of the application.


10. you will be able to find test cases fixed by self heal button in the impact ananlsis tab. From there, you can add those test cases to a test suite and execute them to verify if they are working as intended.



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

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