- Getting Started
- Studio
- Orchestrator
- Testing robots
- Test Manager

Test Suite User Guide
Working with Heatmap
- Application components: Visual containers that group related SAP transactions under a specific component or module.
- Transactions: Boxes inside components representing individual SAP
transactions or programs. Eachbox displays transaction data, such as:
- Transaction name
- SAP code
- Testing status and coverage
To get started with the Heatmap, you need to create test cases for your SAP transactions with UiPath Studio. To ensure the Heatmap accurately shows which transactions are covered by tests and their status, you need to set the Studio project Enable SAP monitoring setting to True.
TRAN:SAP_CODE
or
PROG:SAPPROGRAM
.
Create Purchase Order
,
with ME21N
as its SAP code, has the TRAN:ME21N
label.
If you want to create a test case for this transaction, the same label appears in the
Labels field of the Create Test Case dialog box.
After you create test cases in UiPath Studio for your SAP transactions, you can configure the ratios and settings based on which the Heatmap will display the test relevance and coverage.
The Heatmap is generated based on the values of five SAP attributes. You can configure the assignment ratios to prioritize the attributes most relevant to your testing strategy.
The following table shows the SAP attributes used to generate the Heatmap:
SAP attribute | Description | Default value |
---|---|---|
Users | The number of users using the transaction. | 40 |
Execution | The number of executions per transaction. | 10 |
Time | The overall processing time it takes for a transaction to execute. | 10 |
Object | The number of development objects used in a transaction, such as screens, functional modules, tables. | 10 |
Intensity | The type of transaction:
| 30 |
100
.
Direct connection to SAP instance
- Select the gear icon
in the top-right.
- Change the assignment ratios according to your use case.
For example, to highlight the most intense transactions (of type Create), rather than the most used ones, change the User ratio to
10
, and then the Intensity ratio to60
.
Connection with CSV file
Z_UIPATH_CUST_HEATMAP_DOWNLOAD
program, go in the
Parameters tab and configure the ratios.
After you create tests for your SAP transactions, and configure the Heatmap ratios, you can start analyzing the results and testing specific transactions. Check the following sections for information on how to leverage the Heatmap.
The analysis of Heatmap results involves viewing the test coverage of your transactions, filtering test coverage types, and reviewing transaction overviews. Explore the following topics to gain a comprehensive understanding of how to examine Heatmap results.
Viewing test coverage for transactions
To see which transactions have automated tests, and the results:
- Under the heatmap, select Passed to see the transactions that passed their test results.
- Under the heatmap, select Failed to see the transactions that failed their test results.
- Under heatmap, select No test case assigned to see the transactions that don't have any test cases assigned to them.
- Under heatmap, select Show all (selected by default) to see all the above transactions.
Filtering heatmap transactions
-
Open Heatmap and select what transactions you want to appear from the
Top Transactions dropdown:
- All transactions (default)
- Top 10 transactions
- Top 20 transactions
-
Select the start time for transactions from the Time period
dropdown:
Checking the overview of a transaction
After you analyze the results displayed in the Heatmap, you can start improving your testing portfolio, by creating test cases and test sets for uncovered or failed transactions. Check the following pages for steps on creating test cases and test sets for a specific transaction.
Creating test cases for a specific transaction
TRAN:SAP_CODE
or PROG:SAPPROGRAM
.
Create Purchase
Order
, with ME21N
as its SAP code, has the
TRAN:ME21N
label. If you want to create a test case for this
transaction, the same label appears in the Labels field of the Create Test
Case dialog box.
Learn more about linking test cases to transactions here.
Creating test sets for a specific transaction
- Link a test set to a transaction.
- Select More Options
inline with the test set that you want to execute.
- Select one of the following:
- Execute Manually
- Execute Automated
- Check out the test results in the heatmap.
- Create test cases in Studio
- Linkage and connection between heatmap, test cases and transactions
- Configure Heatmap ratios and settings
- Changing the heatmap settings
- Analyze and test transactions
- Understanding the Heatmap results
- Creating test cases and test sets
- Linking Orchestrator test set to a transaction
- Execute test sets for a transaction
- Heatmap attachments