- Getting started
- Project management
- Documents
- Change Impact Analysis
- Requirements
- Assigning test cases to requirements
- Linking test cases in Studio to Test Manager
- Delete test cases
- Document test cases with Task Capture
- Create test cases
- Importing manual test cases
- Generate tests for requirements
- Cloning test cases
- Exporting test cases
- Automate test cases
- Manual test cases
- Parameters
- Applying filters and views
- Scheduling executions
- Executing tests
- Searching with Autopilot
- Project operations and utilities
- Test Manager settings
- ALM tool integration
- API integration
- Troubleshooting

Test Manager user guide
Change Impact Analysis
Change Impact Analysis represents the process of identifying and assessing the impact of a proposed change to an SAP system. It is a proactive approach that contributes to the reliability, stability, and efficiency of SAP systems. Change Impact Analysis is a systematic process to understand the potential effects that a proposed change can have on a SAP system. The primary goal is to proactively manage and mitigate risks associated with software changes.
In the Heatmap, hover over the information icon next to Analyze Transports to see an overview of the impact of changes on your SAP system.
Select Analyze Transports and understand the impact of changes on your SAP system using Change Impact Analysis.
The impact of changes is shown as Fits and Gaps. Below is a description for the two states:
- Fit: The transactions impacted by the selected transports that are covered by test cases.
- Gap: The transactions impacted by the selected transports that are not covered by test cases.
When using an RFC connection, Change Impact Analysis offers a comprehensive way to consider the potential impact of changes (Fits and Gaps) on your SAP system. It does this by presenting three different view tabs that help examine transaction relationships:
- UI: Displays transactions impacted by the selected transports.
- API: Displays technical interfaces impacted by the selected transports, such as SAP BAPI, SAP RFC, SAP QUERY, and SAP IDOC.
- Security: Displays security transactions and corresponding users impacted by the selected transports.
Change Impact Analysis, similar to the Heatmap offers a two-level view:
- Application components—containers inside the heatmap that contain all the transactions used inside a specific application component.
- Transactions—boxes inside
the application containers that contain data about a certain transaction or
program, such as: name, SAP code, and the percentage of test relevance in the
heatmap.
Yon can zoom in on a selected area of interest and focus only on a specific SAP component or module.
- Gap - The transactions impacted by the selected transports that are not covered by test cases.
- Fit - The transactions impacted by the selected transports that are covered by test cases.
- Not impacted - The transactions in the transport weren't impacted by the change.
You can analyze your SAP transports and generate the Change Impact Analysis only if Test Manager is using an RFC connection or Web service connection to your SAP system.
- Install the UiPath SAP AddOn.
Visit Heatmap prerequisites for step-by-step instructions on how to install the add-on. Regardless of whether you have an existing Heatmap connection or not, it is crucial to follow these instructions for downloading and installing specific files required for the Change Impact Analysis.
- Create a connection to an SAP
instance, specifically for Change Impact Analysis:
- Open your project in Test Manager, and go to Project Settings > Integration.
- Open your existent SAP connection, or select SAP from the New Connection dropdown list.
- Select Change Impact Analysis connection.
- Under Impact Analysis Access select the view tabs
corresponding to SAP change types that you want to display in your
Change Impact Analysis:
- UI: Selected by default, displays transactions impacted by the selected transports.
- API: Displays the technical interfaces impacted by the selected transports, such as SAP BAPI, SAP RFC, SAP QUERY, and SAP IDOC.
- Security: Displays security transactions and corresponding users impacted by the selected transports.
Note: This configuration is available only for RFC connections. - Select the type of
SAP connection that you want to use:
- Same as Heatmap: Keep the same SAP connection details that you are using for the Heatmap.
- New
connection: Create a new SAP connection specifically
for Change Impact Analysis. This option allows you to
use different authentication details while maintaining the
same connection type as the Heatmap.
To create a new SAP connection, follow the same steps for creating either an RFC or web service connection.
When you analyze transports with Change Impact Analysis you consume Transport units. Transport units come in bundles of 100 units.
Every unique transport analyzed consumes one Transport unit. For example, if you purchase three bundles of Transport units, you can analyze 300 unique transports.
When you analyze a transport that has been analyzed before, no Transport unit is consumed.
Follow the procedures below to leverage the capabilities of the Change Impact Analysis.
- Open Heatmap.
- Select Analyze Transports
in the top-right.
- If you don't have
Transport units licenses, or if you consumed all your
licenses, you will only see an overview of your analyzed transports and
impacted transactions.
- If you have unconsumed Transport units licenses, the Transports view opens.
- If you don't have
Transport units licenses, or if you consumed all your
licenses, you will only see an overview of your analyzed transports and
impacted transactions.
You can analyze transports in your SAP system, focusing on data only from the last 30 days for retrieval.
- In the Transports view, next to Retrieve transports from, select a date range within the last 30 days for retrieving transports.
- After you choose a range of dates, select Search to filter the transports.
- Select the transports that you want to analyze.
- Select Analyze transports to
generate the Change Impact Analysis.
The Change Impact Analysis is generated in the Heatmap View.
Change Impact Analysis offers view tabs for switching between the SAP changes that you want to investigate. You can choose what tabs are available in your Change Impact Analysis when configuring the connection.
The available view tabs are:
- UI: This tab is always available, and it displays transactions impacted by the selected transports.
- API: Displays technical interfaces impacted by the selected transports, such as SAP BAPI, SAP RFC, SAP QUERY, and SAP IDOC.
- Security: Displays security transactions and corresponding users impacted by the selected transports.
Under Impact Analysis, select one of these view tabs to investigate the SAP changes in your system.
In the Change Impact Analysis view you can see the transactions impacted by changes within a transport, and their relevance in your SAP system, based on the ratios you configured for the Heatmap. Visit Heatmap ratios to learn how the ratios of the heatmap influence the relevance of transactions.
To see the impact of changes within a transport on your transactions:
- Under the heatmap, select Gap to see the transactions that are impacted and aren't assigned to test cases.
- Under the heatmap, select Fit to see the transactions that are impacted and are assigned to test cases.
- Under the heatmap, select Not impacted to see the transactions that aren't impacted by the changes.
- Select Show all (selected by default) to see all the above transactions.
- All impact types (default)
- Fits
- Gaps
- UI tab – You can filter transactions based on interface types:
- All interface types (default)
- [T] - Transaction in SAP WinGui
- [R] - Report/Program in SAP WinGui
- [W] - Transaction in SAP WebGui
- [F] - Application in SAP Fiori
If you are using an RFC connection, the following view tabs are also available:
- API tab – You can filter transactions based on API types:
- QUERY
- IDOC
- RFC
- BAPI
- Security tab – You can
filter transactions based on security types:
- Security TCode: Displays security TCodes and the user authorized to access them.
- Transactions:
Displays transactions along with their corresponding users.
Note: Information for this security type is not shown in the List view, but you can select Export to view it as a CSV file.
- Users: Displays
users along with their corresponding transactions.
Note: Information for this security type is not shown in the List View, but you can select Export to view it as a CSV file.
For further investigation, you can select Export to retrieve the filtered transactions in a CSV file.
Prerequisites
- To use AI-powered test generation for SAP transaction, your Test Manager role must have the following permissions: Test Case - Create.
- If you want to leverage RAG when generating tests, you first need to get started with using Context Grounding, which RAG is a component of. To get started with Context Grounding, visit the dedicated Best practices page.
- In the Analyze Transports step from the Impact Analysis, select List view to switch to a table of the impacted transactions.
- For the transactions marked as
GAP, select Generate.
The Provide Supporting Documents window opens, focused on the Add documents section, prompting you for attachments or other documents necessary for generating test cases.
Figure 2. Selecting GenerateTests for Gaps in the Impact Analysis
- In the Add
documents section of the Provide additional context
window, select additional attachments. These are used when generating
tests. You can also upload other files yourself.
Figure 3. The Add documents section for generating tests
- In the Leverage RAG section
of the Provide additional context window, select an index which
stores your data uploaded to Context Grounding.
The selected index helps Autopilot in generating more accurate tests by giving it context about the applications that you are trying to automate. For example, you can leverage RAG when a requirement document has incomplete information or refers to additional details in other sections. In this case you can leverage RAG to draw those details from indexed references.
Note: For best practices on working with Context Grounding, visit Best practices.
- From the Select folder dropdown list, select the folder where you store the indexes storing the desired information you want to share with Autopilot.
- From the Select index dropdown list, select the specific index that you want Autopilot to reference.
- For Number of results, enter the number of tests you want Autopilot to generate based on the referenced information.
Figure 4. The Leverage RAG section for generating tests
- In the Add
documents section of the Provide additional context
window, select additional attachments. These are used when generating
tests. You can also upload other files yourself.
- Select Next and provide
additional instructions that AutopilotTM
should use when generating test cases. Choose from a prompt from the Prompt
library or type these instructions in the Provide Additional
Guidance window.
These are some of the instructions that Autopilot can follow:
- You can instruct AutopilotTM the number of test cases that you want to generate. The maximum number of test cases is 50.
- You can specify AutopilotTM to cover all user steps and acceptance criteria described in the loan request requirement.
- You can instruct AutopilotTM to generate pre-conditions.
- You can specify AutopilotTM to generate an expected result for each test step.
- By default, Autopilot considers existing tests linked to a requirement to prevent duplicating tests. However, you can instruct Autopilot to disregard existing tests during new test generation. You can do this by providing an instruction like: "Do not consider tests that are linked to this requirement when generating tests".
Figure 5. Entering instructions in the Provide additional guidance window
- Select Generate tests to
initiate the process.
When the generation finishes, you will receive a Test Case generation completed notification. Depending on your notification preferences, you can receive the notification both in-app and via email.
- Select the Test generation
completed notification to review the generated test cases.
- Expand each test case in the Generate tests panel, and review the generated test cases.
- If you are satisfied with their content, select Create tests.
Figure 6. Expanding a generated test case
- If you are not satisfied with the
generated test cases, select Regenerate, and provide additional details
about your use case.
- Attach more relevant documents for AutopilotTM to use.
- Click Next and type additional details in the Provide instructions text box.
- After refining the steps, select Regenerate.
- Click the Test generation completed notification to access the regenerated test cases.
- Expand each test case and review them.
- Select the test cases that you are satisfied with, and then select Create tests.
Supported file types
Autopilot can process various file types. Depending on the file type, Autopilot can process certain content from it. The following list presents the file types you can offer to Autopilot, along with details about the type of content Autopilot can process from each type:
- Processes only text content – Autopilot processes only the text content from
these file types:
- TXT
- BPMN
- CSV
- Processes both text and image content – Autopilot processes both the text and
images from these file types:
- DOCX
- XLSX
- PNG
- JPG
- In the Change Impact Analysis view, select Table view to switch to a table of the impacted transactions.
- Inspect the impacted transactions,
based on the following information:
- Code: the unique code of a transaction.
- Name: the name of the transaction.
- Transport: the transport that a transaction is part from.
- Relevance: the relevance of a transaction based on the ratios configured at the Heatmap level.
- Process: the process used to publish the test cases that cover the impacted transactions.
- Impact: the type of impact of the change on the testing status of the transaction. This can be either Fit, Gap, or N/A.
- Test Set: the test set where the impacted transactions belong to.
- Select the transactions that you want to add to a test set.
- Select Add to New Test.
Figure 7. Adding impacted transactions to new test sets
- Create a new test set.
- When you're done creating test sets for gaps in your SAP testing portfolio, select Finish.
- View tabs for SAP Changes
- Impact analysis display
- Prerequisites
- Steps
- Licenses
- Test Manager roles and permissions
- Working with Change Impact Analysis
- Accessing Change impact analysis
- Analyze transports
- Switching view tabs for SAP changes
- View the test coverage of impacted transactions
- Filter the impacted transactions
- Generate test cases for impacted SAP transactions
- Create test sets for impacted transactions