Subscribe

UiPath Studio

The UiPath Studio Guide

Activity Coverage

Overview


You can use the workflow activity coverage panel to check whether your test cases have been covered or not and look for redundancies. The test execution results are shown in the Activity Coverage panel.

Analyzing activity coverage results


You can analyze the workflow's activity coverage, debug newly created test case and view covered and uncovered activities. To assist your workflow debugging, you can see the traversed path, by opening the Activity Coverage panel and double-clicking the test case. You can see the path highlighted in green and any skipped activities in red. Additionally, you can quickly identify whether a test case has passed passed or failed failed and view the result.

📘

Note

You can examine test results only for test cases that include verification activities:

1920

Activity coverage scenarios


Partial coverage rate

Consider the partial coverage rate of the following workflow that automates a loan management process.

1183

In this high-volume short-term loan scenario, the activity coverage result shows that 53% of the workflow activities were covered during execution. This flowchart uses a Flow Switch activity. You can create another test case to follow the execution of different scenario, for low-volume loans. Therefore, depending on your automation needs, you can create separate test cases to cover each scenario during the execution.

Full coverage rate

The following full coverage rate scenario tests all activities. This workflow uses a CSV file to import data and a For Each Row in Data Table activity to pass it through each activity as part of data-driven testing.

435

The activity coverage results show a 100% coverage rate, meaning that the data set used in the test case, together with the added activities went through all possible scenarios.

1539

Updated about a year ago

Activity Coverage


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.