Risk-Based Testing for SAP

Panaya's Change Intelligence (CI) for ongoing changes provides real-time change impact assessment for test cycles in any project, release, or ongoing enhancement.  
Panaya layouts the risk associated with your planned transports to allow you to evaluate your test plan.

This article explains how to -

• Perform risk assessments from a testing cycle 
• Select relevant transports and link them for evaluation
• Obtain immediate insights into your current coverage with guided suggestions to optimize your test plan

Linking SAP Transports

First, define and link the relevant SAP transports for step-by-step recommendations on optimizing your planning strategy and eliminating any unpleasant surprises associated with the change. 

1. Open up the Test Tree
2. Highlight a Cycle and select the Summary tab
3. Select Optimize, then search and select the relevant transports.
   
   
   You can select to paste your transport IDs into a list using the From list option, or you can use an Excel spreadsheet to import the IDs.
   
   
   
4. Click on Link
5. Take a look at your Risk-Based Testing summary

Risk-Based Testing Summary

The Risk-Based Testing summary displays a list of insights and suggestions - 

• Change Analysis for the Cycle – This is a direct link to the Transports tab of a dedicated Change Analysis activity created by Panaya.
  You can review and manage all Change Analysis activities from the Development List.
• Optimize entry points – This link will redirect you to the Impact Risk section, where you may scope out findings that have been recommended for exclusion. 
• Consider adding tests from other cycles – Provides you with the capability to increase the testing coverage by copying suggested tests that cover the changes from other cycles in your project. When adding from other cycles, Panaya creates a copy of the tests in the optimized cycle, with a newly generated test ID. The tests will be located in a dedicated folder named 'Change Analysis Cloned Tests.'
• Automatically generate tests for entry points where we did not find relevant tests. The tests will be located in a dedicated folder named 'Change Analysis Generated Tests.'
• Consider removing tests that are not related to the actual changes. If you need to remove tests, you can move them to another cycle or permanently delete them.
• Review Change Requests test failures - Panaya highlights change requests associated with test failures for you to review. Panaya considers in-scope tests for each entry point. This will help you understand which change requests are risky to deploy.

Good to Know!
Panaya also generates a new Change Analysis activity
All Change Analysis activities can be managed from the Development and Workstreams lists.