Back to QMetry All Products Help Page
Grid View Execution Screen
Introduction
To access the Grid View of execution screen, click on the Grid View button at the top.
The Execution screen displays Test Case records that are linked to the Test Cycle under execution.
You can filter out Test Case records by applying different criteria:
A. Key/Summary
B. Filter drop-down with filter options on it:
Execution Assignee: The execution Assignee is a user who is assigned to execute a Test Case from the execution screen.
Execution Result
Defects: You can filter test cases with defects or test cases without defects linked to them.
More: Reporter, Labels, Components, Build, Status, etc.
Filters created are user-specific so they will be saved and displayed on a user profile basis. This means that when the user opens the execution screen, they see the same filters applied on the screen.
C. Reset Filter Values: You can reset/clear the criteria of the saved filter.
D. Remove All Filters: You can clear all the applied filters.
E. Expand/Collapse Filter panel
Beneficial features of Grid View:
A. Test Case Search on 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. Ability to select multiple Test Cases and carry out a Test Case bulk update.
D. The more icon (ellipsis) has two categories of options as - Sort By, and Group By to apply on the Test Case records
How to execute Test Cases on the Grid View Execution Screen?
You can execute Test Cases from three places -
1. On the left panel, select execution result for individual Test Cases as shown in below screenshot:
2. Bulk Execution: On the left panel, select Test Cases and click Update. Select Test Case Execution Result. The latest Test Case execution will be updated.
3. On the Executions tab on the right panel, select the execution result for Test Case and Test Steps.
Test Case Details
The Test Case Details tab displays details entered for the Test Cases in the Test Case module. The tab displays only system fields of the Test Case. Test Case Version is displayed along with the Test Case Key.
Executions
The Executions tab displays execution details of the Test Cases in the test suite. You can view the following details for the Test Case -
Environment: The drop-down shows values entered in Configuration > Test Execution > Environment.
Build: The drop-down shows values entered in Configuration > Test Execution > Build. You can add values in-line. The added values will also be reflected in Configuration. You can skip assigning value to this field on the execution screen.
Execution Assignee: Assignee assigned from the execution screen. You can skip assigning value to this field on the execution screen.
Executed by: User who has executed the Test Case.
A.T.: The actual time taken for executing the Test Case.
S.C.: Steps Count
Bugs: Bug Count
Attachment
Comments
Execution Result
The counts can be clicked to expand the Test Case row to show its relevant tab in the expanded area.
Each Test Case row is expandable. The expanded area has four tabs on it: Steps, Bug, Attachments, and Comments. These tabs can be organized through drag and drop.
Steps tab:
The user can select List View/Grid View for steps in either List View or Grid View.
Steps in List View
Steps in Grid View
Users also have the option to (A) Expand individual steps or (B) Expand all steps at a time.
For a linked bug, the Bug Level displays whether the bug is logged at Test Case level or test step level. If a bug is linked to a test step, the step number is also mentioned. You can unlink a bug from its place of linkage.
The Executions tab on the Test Case detail page (Test Case >Execution tab) displays the bugs and attachments linked on the execution screen.
The Attachments tab lists down all the attachments added from the Test Case 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.
Use the Comments tab to write your comments. You can also tag a Jira user with their comment. It induces smooth communication between two teams/groups. For example, QA team wants to communicate the execution result of a Test Case to the Development team immediately and draw their attention.
Start a New Test Execution
Refer to https://qmetrysupport.atlassian.net/wiki/spaces/QTM4JS410/pages/2234065595.
Clone a Test Execution
You can clone the execution of the Test Case. It will clone all steps, defects, attachments linked with the test execution. The cloning of test execution is useful when you need the same details of the current execution. For example, a Test Case A is failed in Build1 and the tester needs to test the same Test Case in the next Build2 with all the existing associations.
On the execution screen, click on the Clone icon for the test execution that you want to copy.
A pop-up opens. Click Clone to proceed.
A copy of the existing test execution is created. You can then change the Build or Environment as per your requirement and go ahead with the execution.
Delete a Test Execution
If a test execution is created by mistake or you have changed your mind and do not require the new test execution anymore, you can delete it by clicking on the Delete icon for the test execution.
The Delete icon is only visible when there are more than one test executions exist for the test case.
Sync Test Steps
When the steps are added/updated/deleted in the Test Case module, a warning message is shown for the Steps tab indicating the required sync. Click on the provided link to sync the steps with the Test Case and update them on the execution screen.
The pop-up opens. Click on the Sync Steps button.
Sort Test Cases
On the execution screen, you can sort the Test Cases for execution on different attributes.
Open the Sort By drop-down and select the attribute you want to sort Test Cases on.
Group Test Cases
On the execution screen, you can group Test Cases for execution on different attributes.
Click on the more options icon and under Group By, select the attribute on which you want to group the test cases.
The test cases are categorized accordingly on the left panel.
Assign Execution Status
The testers assign the Execution result to the respective Test Cases or Test Steps for tracking the testing process progress. Configuration related to how the execution results of test steps will impact the final execution result of their Test Case is done from Configuration > Project Configuration > Execution Result.
Assign Status to Test Case
If the status of the Test Case is updated, then the status of all the test steps will be updated with the same status as that of the Test Case.
There are two ways you can assign execution result to a Test Case:
A. Under the Execution Result column, select the result you want to assign to the Test Case. If you want to view execution result options, then click on the existing test result of the Test Case.
B. Test Cases under the Test Cycle 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.
Assign Status to Test Step
Each Test Case is expandable on clicking on the step count (S.C.) for the Test Case.
If there is any change (add/update) in the steps in the Test Case module, a warning message is shown for the Steps tab indicating the required sync. Click on the provided link to sync the steps with the Test Case and update them in the execution screen as described in the steps Sync Steps section above.
A. Expand to view more execution status. Select the one that you want to assign to the step.
B. Click to link a defect to a step.
C. Click the icon to link an attachment to a step.
Bulk Update Test Cases from Execution Screen
Assign Build and Environment to the Test Cases linked to a Test Cycle
You can change/assign the environment and build for multiple Test Cases at a time on the execution screen. The change in Build will impact the latest execution of the Test Case.
Select Test Cases the Build and Environment values of which you want to change.
Click on the Update button. The Update screen opens with fields on it.
3. Assign/Change the value of Change Environment and Build in respective fields. If you want to keep the Build field blank, then select the “Set Field as Blank” option on the drop-down.
Bulk Update Test Execution Results
Users can bulk update the execution results of multiple Test Cases at a time from the execution screen.
1. Select the Test Cases you want to execute on the left panel.
2. Click the Update button.
It opens the Update pop-up.
3. Select the Execution Result from the drop-down for all the selected Test Cases.
If you also want to update the execution result of test steps, select the Update Test Step Execution Result checkbox.
4. Click Update.
Bulk Update Execution Assignee
You can update the assignee who will execute the Test Cases from the execution screen. Users can also bulk update the Execution Assignee of multiple Test Cases at a time from the execution screen.
1. Select the Test Cases you want to execute on the left panel.
2. Click the Update button.
It opens the Update pop-up.
3. Select the Execution Assignee from the drop-down for all the selected Test Cases. If you want to keep the field blank, then select the “Set Field as Blank” option on the drop-down.
4. Click Update.
View Summary
Refer to https://qmetrysupport.atlassian.net/wiki/spaces/QTM4JS410/pages/2234065750
Execution Logs
Refer to https://qmetrysupport.atlassian.net/wiki/spaces/QTM4JS410/pages/2234065645
Export Test Execution
Refer to
Back to QMetry All Products Help Page