Back to QMetry All Products Help Page
Test Execution Screen Detail View
- 1 Introduction
- 2 Test Run Detail View
- 2.1 Filters
- 2.2 Planned Date
- 2.3 Execute Individual Test Cases
- 2.4 Execution Status of Test Cases with Parameterized Values
- 2.5 Log Issues
- 2.6 Add Attachments
- 2.7 Add Comments
- 2.8 Actual Attended Time (mins)
- 2.9 Bulk Operations
- 2.9.1 Planned Date
- 2.9.2 Execution Comment
- 2.10 Execution Status
- 2.11 Execution Type
- 2.12 Assignee
- 2.13 Issues
- 2.14 Execution Time
- 2.15 Assigning Build for Test Executions
- 2.16 Linking The Latest Test Case Version at Run-time
- 2.17 Test Result Log
- 2.18 Change Log
- 2.19 Export
- 3 Test Case Run Detail View
- 3.1 Test Case Details
- 3.1.1 Steps Tab
- 3.1.2 Details Tab
- 3.1.3 Requirements Tab
- 3.1.4 Issues Tab
- 3.1.5 Attachments Tab
- 3.1.6 Execution Comments Tab
- 3.1.7 Audit Log Tab
- 3.2 Assign Execution Status
- 3.1 Test Case Details
- 4 Share Test Execution Runs with Other Users
Starting March 2026 with QMetry Test Management version 8.25.0, the documentation was migrated from Atlassian to a dedicated, standalone QMetry Test Management documentation site. For the latest updates, refer to Test Execution Screen Detail View.
Introduction
The Test Suite Execution screen is used for performing Manual Testing and scheduling Automation Testing by QA teams. Test suites are executed on different platforms and the run results derived therefrom are marked on the screen. There are two views available for the test execution screen: Default View and Detail View. You can select the view as per your preference. This page refers to the Detail View of the test execution screen. To read about the Default View of the test execution screen, refer to https://qmetrysupport.atlassian.net/wiki/spaces/QPro/pages/76152917.
Users can opt to view the Detail View of the execution screen from the test execution default view. The Detail View of execution screen shows the test case execution details grouped in different tabs on a single screen. You can also change the sequence of the tabs through drag and drop operation. The preferences are saved as per each user.
On the execution screen, the Default View of the execution screen is available by default.
To switch to the Detail View of the execution screen, click on the Switch to Detail View button at the top.
Test Run Detail View
The Test Run Detail View screen opens.
Platform Attributes
If any Platform Attributes are tagged for runtime, then a pop-up like the following appears to edit Runtime Attributes when you click on the Switch to Detail View button. You can provide attribute values on the Execution Screen either at run time or afterward.
Filters
The Test Run Detail View screen has Filters panel to apply Basic and Advanced filters to search the entities. This feature helps organize and streamline the test execution process effectively.
Basic Filters: Basic filters enable you to filter test cases by status, assignee, owner, and test case folder path.
Advanced Filters: For more advanced filters, click on the '+' icon. It opens the drop-down with a list of additional system and user defined fields. Select the field you want to apply filter on. The filter parameter is added as Advanced Filters. Apply filter as per your requirement.
You can filter the linked test cases in the test suite by the folder path. You can also view the linked test cases of specific folders or the subfolder hierarchy of the folder by clicking on the include entities from subfolders checkbox. By default, this option is selected.
Sort Test Cases on the Execution Screen
You can easily sort test cases on the Test Execution screen by clicking on the respective column headers. Sorting icons (up/down arrows) appear on the header to indicate the selected sort order.
Planned Date
Users with ANY of the following permissions can modify the Planned Date:
Test Suite Modify Permissions
Test Suite Execute Permissions.
Users can manually set or update the planned date for individual test cases from this screen.
Steps:
Navigate to the Test Execution Screen and open the Detail View.
Click on the planned date field for the test case you wish to update.
Select the desired date from the calendar.
Click the checkmark to confirm and set the date.
Execute Individual Test Cases
Select the execution status for the test case under the Execution Status column.
Execution Status of Test Cases with Parameterized Values
The execution screen displays the execution status at the parameter group combination level when executing parameterized test cases.
Use case:
As a tester analyzing a failed test case execution with multiple parameter group combinations, you can quickly identify both the failed parameter combinations and unexecuted cases with a "Not Run" status.
Notes
The execution status for parameter groups will only be displayed for projects in which the “Derive Test Case Execution Status from Test Step Status” setting is enabled.
Only the consolidated execution status for each parameter group combination is displayed based on the test step execution performed for that combination. This execution status is not editable.
The execution status of each parameter combination follows the similar status prioritization logic used to calculate the test case execution status. Refer Execution Status Management to know more.
Log Issues
On the Test Run Detail View, click on the Bug icon for the test case with which you want to link the issue.
It navigates you to the Issues tab of Test Case Run Detail View. Refer to the Issues Tab for more details.
Add Attachments
To add an attachment to the test case, click on the Attachment icon for that test case. Refer to https://qmetrysupport.atlassian.net/wiki/spaces/QPro/pages/38076495 for more details.
Add Comments
To add a comment to the test case, click on the Comment icon for the test case.
It navigates you to the Execution Comments tab of the Test Case Run Detail View. Refer to the Execution Comments Tab for more details.
Tagging Users in a Comment
You can tag QMetry users in the Comments section, which improves collaboration among the team. An email notification will be triggered to the user who is tagged on adding/updating the comment.
QMetry users can be tagged by their usernames in the Comments section. For example, @<username>
Actual Attended Time (mins)
Users can enter Actual Setup Time and Actual Attended Time for each test case on the execution screen. Refer to Tracking Actual Execution Time with Stopwatch Timer document to know about timer settings.
Bulk Operations
Users with ANY of the following permissions can Assign/Modify/Unassign test execution testers and change the planned date:
Test Suite Modify Permissions
Test Suite Execute Permissions.
You can perform the following bulk operations:
Execution Status
Execution Type
Execution Comment
Assignee
Planned Date
Issues
Sync with Latest Version
Refer to https://qmetrysupport.atlassian.net/wiki/spaces/QPro/pages/76152917/Test+Execution+Screen+Default+View#BulkOperations for more details.
Planned Date
You can set a single planned date for multiple test cases in bulk.
To set planned date in bulk, perform the following steps:
Open the Bulk Operations drop-down and select the Planned Date option (A).
Select the test cases from the grid (B)
Open the Planned Date calendar and choose the desired date for the selected test cases (C).
If no planned date is available, click on Set as Unplanned.
The planned date for all the selected test cases will be updated in bulk.
Execution Comment
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.
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 Status
You can also 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 execution of 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 option on it. It makes the Status drop-down visible which has Passed, Failed, Not Run, Blocked and Not Applicable statuses on it.
Select multiple test cases to which you want to apply the status.
Select the required status on the Execution Status drop-down. It applies to all the test cases selected on the grid.
Execution Type
Users can assign Execution Type in bulk to test cases whose execution type is similar. Users do not have to update the Execution Type of test cases one by one.
Open the Bulk Operations drop-down and select the Execution Type option on it. It makes the Execution Type drop-down visible which has the list of users on it.
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
Users with ANY of the following permissions can Assign/Modify/Unassign test execution testers:
Test Suite Modify Permissions
Test Suite Execute Permissions.
Users 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 the Assignee option on it. It makes the Assignee drop-down visible which has the list of users on it.
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.
Issues
Users can link QMetry issues or Jira defects to multiple test cases at a time.
User Case: 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 the Link Issues option on it. It makes the Assign Issues button visible.
Select test cases on the grid.
Click on the Assign Issues button. It opens the Issues screen.
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 under the defects linked with test cases in QMetry.
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 > General Settings & Audit and turn the Allow manual edit of last executed date/time flag On.
Open the Bulk Operations drop-down and select the Execution Time option on it. It makes the Execution At field visible.
Select test cases on the grid.
Select the date and time of execution using the calendar and click Apply.
The date and time are changed under the Executed At column for the selected test cases.
Assigning Build for Test Executions
Refer to https://qmetrysupport.atlassian.net/wiki/spaces/QPro/pages/76152917/Test+Execution+Screen+Default+View#AssignBuildforTestExecutions for more details.
Linking The Latest Test Case Version at Run-time
You can associate the latest version of the test case to the test suite from the Detail View Execution screen by syncing the test case version. You can sync a single as well as multiple test case versions to the latest ones.
Refer to https://qmetrysupport.atlassian.net/wiki/spaces/QPro/pages/76152917/Test+Execution+Screen+Default+View#LinkLatestTestCaseVersionatRun-time for more details.
Sync a Single Test Case to the Latest Version
Bulk Sync Test Cases to Latest Version
Test Result Log
The Test Result Log displays detailed information about each test.
Refer to https://qmetrysupport.atlassian.net/wiki/spaces/QPro/pages/76152917/Test+Execution+Screen+Default+View#TestResultLog for more details.
Change Log
The Change Log displays logs of the following activities carried out on the execution screen for a particular Test Execution.
Refer to https://qmetrysupport.atlassian.net/wiki/spaces/QPro/pages/76152917/Test+Execution+Screen+Default+View#ChangeLog for more details.
Export
You can export test executions in Excel.
Refer to https://qmetrysupport.atlassian.net/wiki/spaces/QPro/pages/76152917/Test+Execution+Screen+Default+View#ExportTestExecution for more details.
Export Test Execution to PDF
Refer to Export from Execution Screen.
Test Case Run Detail View
To view the test case run detail view, hover over the test case. Click on the Eye icon visible on hover over the test case.
It opens the detail view of the test case.
The panel at left displays test cases linked to the test suite.
The top section of the screen displays the test case run details.
You can view the following details for the test case on the execution screen.
Build Name: The drop-down shows values entered in Projects > Builds.
Assignee: Assignee assigned from the execution screen.
Executed by: User who has executed the test case.
Actual Setup Time: The actual time required to set up the test case.
Actual Attended Time: The actual time that is taken for executing the test case.
Issues Count
Attachment Count
Comments Count
Execution Result
The counts can be clicked to open its relevant tab below.
The area below the top section includes the Steps and other tabs.
The left side of the screen shows the test case list section. You can click on the test case to view its detail view at the right.
A. Search test cases by Key/Summary
B. Easy to identify the execution status of each test case just by looking at the vertical line of the test case.
C. Stopwatch Timer: Click on the Edit icon to record the execution time.
D. Count of Issues: Clicking on this button opens the Issues tab below.
E. Count of Attachments: Clicking on this button opens the Attachments tab below.
F. Comments: Clicking on this button opens the Comments tab below.
G. Assign Execution Status to the test case.
H. Clear Sorting
I. Arrange Columns
J. Step View: List View/Detail View
Test Case Details
The following tabs are there on the execution screen. You can also change the sequence of the tabs through drag and drop operation. The preferences are saved as per each user.
Steps
Details
Requirements
Issues
Attachments
Execution Comments
Audit Log
Steps Tab
You can opt to view steps either in List View or in Grid View.
Steps in List View
Open the List View to view the step details organized vertically.
Steps in Detail View
Open the Details View to view the step detail in a row.
Users also have the option to Expand individual steps or Expand all steps at a time.
Enable Steps Custom Fields
Click on the Arrange Columns drop-down for the Steps tab and select the fields you want to show on the screen.
Details Tab
The Details tab in the Detail View of the execution screen displays details entered for the test cases in the Test Cases module, which makes it convenient for testers to view them directly on the execution screen. The Test Case Version is displayed along with the Test Case Key.
Requirements Tab
The “Requirements" tab enables testers to view requirements associated with the test case under execution.
Issues Tab
You can created a new issue or link existing issues to the test case. You can also view linked issues to the test case in this tab. For a linked bug, the Linkage Level displays whether the issue is logged at the test case level or test step level. You can unlink a bug from its place of linkage. Read more details on https://qmetrysupport.atlassian.net/wiki/spaces/QPro/pages/3227287553.
Attachments Tab
The Attachments tab lists down all the attachments added from the Test Cases module as well as from the execution screen. You can filter attachments based on their Attachment Level.
The Attachment Level column displays at which level the attachment has been linked - to a Test Case or a test step in the Test Case module or on the execution screen. You can delete an attachment from its place of linkage. Read more details on https://qmetrysupport.atlassian.net/wiki/spaces/QPro/pages/3227287771.
Execution Comments Tab
Use the Execution Comments tab to write your comments. It facilitates smooth communication between two teams/groups.
Tagging Users in A Comment
You can tag QMetry users in the Comments section, which improves collaboration among the team. An email notification will be triggered to the user who is tagged on adding/updating the comment.
QMetry users can be tagged by their usernames in the Comments section. For example, @<username>
Audit Log Tab
The Audit Log tab consists of two sections: Test Result Log and Change Log.
→ Test Result Log: The section displays test result execution log for the test case. You can expand the test case and drill down to view the steps.
→ Change Log: The section record the change log for that particular test case.
Assign Execution Status
The testers assign execution result to the respective test case or test steps for tracking the testing progress.
Assign Status to Test Case
There are two ways you can assign execution result to a test case:
A. The execution result drop-down is displayed at the top of the screen. Select the execution result you want to assign to the test case.
B. The test cases associated with the test suite are displayed on the panel at left. Select the result you want to assign to the test case directly by clicking on the result icon on the left panel.
Test Run Details: To view the test run details, click on the info icon at the top.
Assign Status to Test Step
Open the Steps tab and select the status that you want to assign to the step.
You can link issues and attachments to the step.
A. Click on the Bug icon to link issues to the step.
B. Click on the Attachment icon to link attachments to the step.
Automation Error Trace
If the automated test case fails, then you can view the relevant error details for the test case by clicking on the icon at the top.
Share Test Execution Runs with Other Users
QMetry allows easy sharing of test execution runs with other users. The recipient will receive an email with an asset summary, a message from the sender, and a link to the asset.
Steps
Go to the Test Suite > Test Executions.
Click on the Share icon at the top. The Share pop-up opens.
Enter the email address(es) of QMetry user(s) to share the asset.
Write a message (optional but recommended) for the recipient(s).
Click on the Share button.
Copy Test Asset Link
Users can copy the test asset link and share it with other users for direct access. Authorized members can access the test asset through the shared link.
URL Syntax
https://<URL>>/#/<AssetType>/<AssetKey>
For example,
Steps
Go to the Test Suite > Test Executions.
Locate and click on the Copy Link icon ( ) on the breadcrumb navigation.
Users can share this link via any preferred communication channel.
The test asset link gets copied to the clipboard. You can share this link with other team members, whom you want to work on the test asset, either through email or chat or any other communication means.
Back to QMetry All Products Help Page