- Getting started
- Project management
- Project operations and utilities
- Test Manager settings
- ALM tool integration
- API integration
- Troubleshooting

Test Manager user guide
You can distribute your work within a testing project by assigning manual test case executions to users, and setting due dates for them. You can assign manual executions to any user, keeping in mind that they should have permissions to execute tests.
Prerequisites
To assign or unassign manual test case logs, you must have the Change test case executions assignments task permission in one of your roles. By default, this task permission is integrated in the Test Manager pre-defined role.
Assigning manual executions
To assign one or multiple manual executions to a user, perform the following steps:
- Go to the Execution section of your project.
- Select the name of a test
execution and open it.
Note: Any test execution can be selected, regardless of its type. This is because the objective is to facilitate manual execution by the user, irrespective of the method used in its prior execution.
- Assign the manual test case executions in one of the following ways:
- To assign a single manual test case execution: select More Options for the desired test case, and then select Assignment.
- To assign multiple manual test case executions: select the check boxes next to the desired manual test case keys, and then select Assign.
The Assignment dialog box opens.
- In the Assignee field,
enter the username or email address of the user to which you want to assign the
test cases.
Ensure that the user to which you assign the test case has permissions to execute tests.
- In the Set the due date field, enter the date by which you want the user
to run the test case.
The format of the date is: Month/Day/Year.
You can also use the date picker for this step.
- Select Assign to complete
your action.
If subscribed to these events, the user will receive a notification that test cases were assigned to them.
Unassigning manual executions
To unassign one or multiple manual executions from a user, perform the following steps:
- Go to the Execution section of your project.
- Select the name of the target test execution and open it.
- Unassign the manual test case
executions in one of the following ways:
- To unassign a single manual test case execution: select the check box next to the desired test case, and then select Clear assignment.
- To unassign multiple manual test case executions: select the check boxes next to the desired manual test case keys, and then select Clear assignment.
If subscribed to these events, the user will receive a notification that test cases were unassigned from them.
You can set a due date for a manual test case execution. If that date passes without running the test case log, the due date will be highlighted.
To set a due date for a manual test case execution:
- Go to the Execution section of your project.
- Select a manual test execution and open it.
- Open a test case log.
- In the Due Date field, from the test case log header, enter the due date. The
format should be: Month/Day/Year.
You can also select the date using the date picker.
Note: You can also set the due date when assigning the manual test case execution to a user.
Both Test Manager test sets and test sets that have been linked from Orchestrator can be executed manually. if manual steps have been defined for the test cases.
For more information on test results, see Analyzing Test Results.
Alternatively, you can open your test set, select Execute and then select Manually from the dropdown list.
Manual execution assistant
The manual execution assistant allows you to perform a set of manual tests one after another. You need to set a result on each manual step to advance to the next test case in the test set. Through the Manual Execution Assistant, you need to treat and mark steps in each case either as passed or failed.
- To mark the progress of each step in the test case, select Set Failed or Set Passed.
- Include comments, especially when marking a step as failed, to supply specific information about the outcome.
- After marking a step, you can set several following steps as passed. Do this by selecting Set Passed Until Here.
- Once you conclude a test case by assigning a result to the last step, select
Next.
This action allows you to advance to the next test case within your test set.
- Repeat steps one to four until you reach the final test case in the test set.
- If a postcondition is specified for a manual test, verify it after assigning a
result to the last step of a test case.
- If the postcondition is satisfied, select Condition Met.
- If the postcondition is not met, leave Condition Met unselected.
- After finishing the last test case, select Done to complete the entire execution process.
Taking screenshots when manually executing tests
Capture the behavior of an application with screenshots during manual test execution, following these steps:
- Navigate to the Test Sets section of your project and open a manual test set.
- Select Execute >
Manually.
The manual execution assistant opens, displaying the first manual test case ready for execution.
- Start executing your tests manually.
- When you reach a test step where you want to take a screenshot of the application,
go to More options > Capture screen.
window appears, offering the following capture options, which apply to most browsers:
The Choose what to share with https://govcloud.uipath.us/portal_
- Entire Screen: This option takes a screenshot of a desired active screen.
- Window: This option takes a screenshot of a desired application window.
- <Broswer> Tab:
This option takes a screenshot of a certain browser tab, such as Chrome, for
example. The name varies based on the browser in use.
Note: While capturing a screenshot of a window or browser tab, that tab or window gains focus. To resume the manual test execution, you have to manually return to the manual execution assistant. This step is due to a security limitation of the browser.Figure 3. Capturing a screenshot in the Choose what to share window
- After you select the element that you
want to capture, select Share.
Your captured screenshot now appears as a preview within the test step.
Note: If a screenshot of any window or tab other than Test Manager is captured, that window or tab will become the main focus. To proceed with the manual execution after taking the screenshot, you will need to manually navigate back to the manual execution assistant. - You can optionally select View
within the test step to check the preview.
Figure 4. The preview of the screenshot inside the manual execution assistant
Result: After completing the manual test execution, open the log of the test case where screenshots were captured. The screenshots appear under the Attachments column.
Uploading attachments when manually executing tests
To add more detail to your manual test executions, upload attachments by following these steps:
- Navigate to the Test Sets section of your project and open a manual test set.
- Select Execute >
Manually.
The manual execution assistant opens, displaying the first manual test case ready for execution.
- Start executing your tests manually.
- When you reach a test step where you
want to attach a file, go to More options > Upload
attachment.
The file explorer of your machine opens, allowing you to choose the file to upload.
Depending on the type of attachment, you can interact with them as follows:
- For images, select View to check a preview.
- For other file types, select Download to retrieve the attached file.
Result: After completing the manual test execution, open the log of the test case where attachments were uploaded. The attachments appear under the Attachments column, where, depending on the file type, you can view or download the attachment.
You can execute manual test cases simultaneously with other users. This allows for the re-execution of test cases even while a manual test set run is in progress. The test case log status is constantly updated according to the most recent user activity encompassing both the start and end of a test. Status updates occur immediately when a user begins to re-execute a previously completed test case log, without preserving the previous result throughout the re-execution process. While a record of past executions is maintained, any new result overwrites the old one, meaning the test case log reflects the outcome of the most recent execution.
Identifying the last test case executor
Within the Results tab of a manual execution, the ExecutedBy column displays the username of the most recent user who executed the test case log. This information refreshes each time you or other users take any of the following actions on a test case:
- Execute a manual test set for the first time;
- Run a pending execution of a manual test execution;
- Re-execute a test case log from a manual execution.
Tracking test case logs
If you re-execute a test case log during a particular test execution, Test Manager will not preserve the test case log's history and will overwrite it. However, you can review the execution history for each test case, across different test executions and associated user details, in the Latest Results tab.
- Executing manual tests
- Assigning manual executions to users
- Prerequisites
- Assigning manual executions
- Unassigning manual executions
- Scheduling a due date for manual executions
- Execute Test Sets Manually
- Manual execution assistant
- Taking screenshots when manually executing tests
- Uploading attachments when manually executing tests
- Executing test cases simultaneously
- Identifying the last test case executor
- Tracking test case logs