Bulk Operations on Test Executions
Bulk assign Execution Status, Execution Type, Assignee, and Planned Date for test suites with multiple test cases, platforms, releases, and cycles.
To bulk execute test runs, perform these steps:
The selection range of respective checkboxes on the screen:
Platforms
Releases and Cycles
Platform Attribute: To view Platform attributes, click the icon adjacent to the platform name.
Select a particular release and cycle for all test cases on the current page.
Select a Platform with all test cases under all releases and cycles.
Select individual test cases.
Select a test case with all releases and cycles and platforms associated with it.
Select all test cases under all releases and cycles associated with all platforms.
Go to the Test Suite module and select Test Execution tab.
Select test cases to execute and click Bulk Execute.
Note
A maximum of 20 test execution runs can be selected at a time.
Perform bulk updates for selected test cases, including:
Execution Status
Execution Type
Assignee
Planned Date
 |
Execution Status
You can assign execution status to multiple test cases at a time.
Use Case: A new build is received from the development team, and the QA Manager has scheduled a Regression Test. The scope covers multiple modules and functionalities thereof. Testers are well aware of the test cases and test steps associated with each module. So they jump-start on executing the test cases one after another without going into details. They keep running continuous execution without updating the run status of each test case. At the end or a certain point they just update the status of bulk test cases with a few clicks instead of assigning status one by one on each test case execution.
Open the Bulk Operations drop-down and select the Execution Status.
Select test cases to apply the status.
Select status on the Execution Status drop-down.
Add a comment to explain the status change(optional).
Click Update to save the changes.
Execution Type
You can assign Execution Type in bulk to test cases whose execution type is similar.
Open the Bulk Operations drop-down and select Execution Type.
Select test cases on the grid.
Open the Execution Type drop-down and select the type that is to be assigned to the selected test cases.
Assignee
Note
Users with ANY of the following permissions can Assign, Modify, Unassign test execution testers:
Test Suite Modify Permissions.
Test Suite Execute Permissions.
You can assign test cases in bulk to a tester to execute. It saves QA Lead, Manager's time to assign multiple test cases to the same tester.
Open the Bulk Operations drop-down and select Assignee.
Select test cases on the grid.
Open the Assignee drop-down and select the tester to whom all the selected test cases are to be assigned for execution.
Planned Date
Note
Users with ANY of the following permissions can modify the Planned Date:
Test Suite Modify Permissions
Test Suite Execute Permissions.
You can set a single planned date for multiple test cases in bulk.
To set planned date, perform the following steps:
Open the Bulk Operations drop-down and select Planned Date option.
Select the test cases from the grid.
Open the Planned Date calendar and choose the desired date for the selected test cases.
If no planned date is available, click Set as Unplanned.
The planned date for all the selected test cases gets updated in bulk.
Issues
Users can link QMetry issues or Jira defects to multiple test cases at a time.
A testing team has some test suites containing many test cases. They want to link a Jira issue with multiple test cases. Linking an issue to each execution can be very time consuming. Thus, they want the ability to link a JIRA issue to multiple executions at once.
Open the Bulk Operations drop-down and select Link Issues.
Select test cases on the grid.
Click Assign Issue.
Then follow the same mentioned process of linking existing issues. Read more about Adding/Linking Issues to Test Case and Test Step.
When opening the issue in Jira, the test case links in Jira are displayed in accordance with the defects linked with test cases.
Execution Comment
Note
You need Test Suite Execution Permissions to add execution comment.
You can add execution comments for multiple test case runs in bulk. This comes handy when you need to add the same comment for multiple test case execution runs in a test suite.
To set execution comment in bulk, perform the following steps:
On the Execution Screen, open the Bulk Operations menu, and select Execution Comment.
Select test case executions using check boxes and filters.
In the text box, enter the comment, and select the check mark to save.
Note
You can update up to 1,000 records in a single operation.
The Select All option is not available for test case dependent projects.
To use rich text in comments, enable the Rich Text Editor in Project settings.
Rich Text Editor supports formatted text but excludes image insertion, image copy-paste, and user tagging.
You can add comments at the Test Case Execution Level and not at the Test Step Execution Level.
The maximum comment length is 65,535 characters.
Execution Time
Users can modify the execution date and time for multiple test cases at a time.
To enable the editing of the Execution date and time, go to Customization and select General Settings and Audit and turn the Allow manual edit of last executed date or time flag On.
Open the Bulk Operations drop-down.
Select Execution Time.
Select test cases on the grid.
Select the date and time of execution using calendar and click Apply.
The date and time is changed under the Executed At column for the selected test cases.