- Getting Started with Test Suite
- Studio
- Orchestrator
- Test Manager
Heatmap
- Test Relevance—the size of
the box in the Heatmap displays how relevant the test is for achieving a
specific goal. The size of the box answers the question: How often and how
heavily is this transaction used?.
Test relevance is calculated and weighted based on parameters such as: number of users, number of executions, overall execution time, transaction complexity (based on the number of development objects), and the type of transaction intensity that you configure.
Depending on the source of the SAP data, you can define the default heatmap ratios settings.
- Test Coverage—The colors of the boxes provide a visualization of the execution coverage of a transaction through executed test cases.
The actual heatmap that is generated using your SAP data 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.
- White - no test cases were assigned to this transaction.
- Gray - no test cases were executed for this transaction.
- Red - test cases exist and one or more executions failed.
- Green - test cases exist and all executions passed.
The heatmap offers the Change Impact Analysis sublayer that analyzes your SAP system for changes and shows the testing status of them, so you can allocate your testing efforts more efficiently.
To analyze the impact of changes in your SAP system over your testing portofolio, select Analyze Transports in the top right. Hover over the information icon next to Analyze Transports for a preview number of your transports that can be analyzed.