Grid View Execution Screen

Introduction

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. View: Active/Archived/All test cases on the execution screen.

B. Key/Summary

C. Filter drop-down with filter options on it:

Note: A maximum of 10 filters, including system as well as custom fields, can be selected at a time.

  • 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.

  • Test Case Assignee: The Test Case Assignee is a user who is assigned to a test case from the test case details screen. You can filter test cases based on Test Case Assignee and bulk update those test cases. For example, you can bulk assign those test cases to an Execution Assignee so that you do not have to check test cases individually.

Steps

1. Filter test cases on the Test Case Assignee field.

2. Select the test cases you want to update. Click on Bulk Operations and select the Update option. The Update screen opens.

3. Assign values to the required field(s). For example, the Execution Assignee is assigned from the drop-down list.

4. Click Update to update the test cases for the selected field values.

image-20240118-091228.png
  • More: Reporter, Labels, Components, Build, Status, Priority, Sprint, Fix Versions, Environment, Coverage/Stories, Estimated Time, Actual Time, Test Case Type, etc. You can filter out Test case records based on execution custom fields.

  • Custom fields: There are two sections for custom fields: Test Execution Custom Field and Test Case Custom Field. Custom fields of the current project are displayed on the filter menu. If cross project's test cases are linked with the test cycle, then custom fields of the test cycle project (i.e. current project) will be displayed.

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.

→ Apply Filters with Operators

In addition to the “OR” operator to filter the test assets, you can filter the test assets using the “AND” operator for the Multi-Lookup List. It enables you to filter the entities having multiple similar values in their fields. For example, you can filter test cases that have both Label1 & Label2 in the Label field. The filter will search for those test cases in which both values are present in the Label field. There are a total of 10 test cases, out of which 3 test cases have Label1, 2 test cases have Label2, and 5 test cases have both the labels Label1 and Label2. So, the search output will display 5 test cases that have both the Label values.

The filter is available on these fields: Label, Components, Fix Versions, Multi-dropdown custom field, Labels custom field, Multi-users custom field, and Checkboxes custom field.

Note: If a filter with the AND operator is applied, you can not carry out Group By Folder and Component operations.

Select more than one filter value for the field. The Operators option becomes visible on the drop-down. The filter considers “OR” as the default operator and applies it to filter the records, which displays records with either of the selected values.

Note: The operators are visible only on the selection of more than one filter value.

To change the operator, click on the Edit icon beside the “OR” operator.

The drop-down displays two operators: “OR” and “AND”.

You can select “AND” as the operator to apply for the filter.

The filter applies with the operator “AND” and the output shows the records holding both values.

 

D. Reset Filter Values: You can reset/clear the criteria of the saved filter.

E. Remove All Filters: You can clear all the applied filters.

F. Expand/Collapse Filter panel

 

Beneficial features of Grid View:
A. View Archived/Active/All test cases

B. Test Case Search on Key/Summary
C. Easy to identify the execution status of each Test Case just by looking at the vertical line of the Test Case.
D. Ability to select multiple Test Cases and carry out a Test Case bulk update.

E. The more icon (ellipsis) has two categories of options - Sort By, and Group By to apply to 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 the execution result for individual Test Cases as shown in the below screenshot.

2. Bulk Execution: On the left panel, select the test cases you want to update the execution result of. Click on Bulk Operations and select the Update option. The Update screen opens. 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 the test case and test steps.

Test Case Details

The Test Case Details tab in Grid View of the execution screen displays details entered for the test cases in the Test Case module. The tab displays the system and custom fields of the test case from the current project as well as cross-project. The 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.

Note: Inline images added to test case/test step/comments while authoring or execution will be attached under test case attachments. 

  • Environment: The drop-down shows values entered in Configuration > Test Execution > Environment.

  • Build: The drop-down shows values entered in Configuration > Test Execution > Build.

  • Execution Assignee: Assignee assigned from the execution screen.

  • Executed by: User who has executed the Test Case.

  • A.T.: The actual time that is taken for executing the Test Case.

  • S.C.: Steps Count

  • Bugs: Bug Count

  • Attachment

  • Comments

  • Execution Custom Fields: These are the Test Execution custom fields added from Configuration > Custom Fields. An asterisk (*) next to a field name indicates a mandatory field. 

  • 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.

If the Precondition is mentioned in the test case, then it will be displayed in the Steps tab.

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.

Bug Tab

For a linked bug, the Bug Level displays whether the bug is logged at the 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.

Attachments Tab

The Attachments tab lists 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.

Comments Tab

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, the QA team wants to communicate the execution result of a Test Case to the Development team immediately and draw their attention.

→ Jira Permissions that are needed for tagging users

  • The user and atlassian-addons-admin should have the Browse users and groups permissions. (Jira Settings > System > Global Permissions > Browse users and groups): The user and “atlassian-addons-admin” groups should be part of this permission.

  • Assign Issue permission (Project Settings > Permissions): The users having this permission can tag other users.

  • Assignable User permission (Project Settings > Permissions): The users having this permission can be tagged.

Execution Custom Fields Tab

Custom fields from the Configurations section of the current project are displayed on the Execution Custom Fields tab. If cross project's test cases are linked with the test cycle, then custom fields of the test cycle project will be displayed. You can enter/edit/remove values in the custom fields. An asterisk (*) next to a field name indicates a mandatory field. 

Sync Latest Test Case Version

The Sync icon on the screen acts as an indicator that indicates whether the linked version of the test case is the newest version or an older version. You can easily come to know that you need to sync the latest version of the test case with the test cycle.

While reviewing the linked test case of a test cycle, the QA Manager/Tester easily finds out whether the test case that is getting executed/linked is the latest one. While executing the test case the testers shall know if they are executing a new test case version or still executing an older one.  The Test Cycle > Test Cases tab and the execution screen now indicate the availability of a newer version of a test case besides the older linked version. If the older test case version is found, testers have the option to sync the latest version of associated test cases individually or in bulk. 

The feature is useful as -

  • the syncing of test cases to a new version can be done individually or in bulk, which saves time. 

  • it eliminates the need to manually unlink the older version and link the newer version of the test case for execution.

→ Required Permissions: Users should have “Test Cycle Edit” permission to sync the latest version of the test case with the test cycle.

An archived test case can’t be synced with the latest version. To sync the archived test case with the latest version, unarchive it first.

If multiple versions of a test case are linked to a test cycle and the latest version of the test case is available, you can sync only one version with the latest version of the test case. In bulk operation, if multiple versions of a test case are selected for sync, the first test case in the order of the linking will be synced.

Once the latest version of the test case is synced -

  • the action of syncing the latest test case version can’t be reverted.

  • this action shall reset the execution status of the test case and its test steps to “Not Run” on all its current and previous executions on this test cycle.

  • bugs linked with the previous executed version shall not be carried forward (linked) to the latest synced version of the test case and shall be unlinked from older executions.

  • the “Actual Time”, “Actual Outcome”, “Comments”, “Attachments”, and “Any other Custom Execution Fields” values shall be erased and shall be lost.

 

The following table shows the indication of different colored Sync icons.

Icon

Description

Icon

Description

 

It indicates that the latest version of test case is available.

 

It indicates that the test cycle is synced with the latest version.

Sync Latest Version of a Single Test Case

You can sync the latest version of a single test case as well as multiple test cases on the execution screen. This section describes the steps to sync the latest version of a single test case.

Steps:

1. Open the Grid View of the test execution screen.

The Sync icon adjacent to Version indicates whether the test case version is the latest or not. The icon appears in Blue when the latest version of the test case is available for sync.

2. Click on the Sync icon to sync the latest version of the test case with the test cycle.

 

The confirmation message appears. Read it carefully.

3. Click Sync to proceed.

The latest version of the test case is synced with the test cycle.

Sync Latest Version of Multiple Test Cases

You can sync the latest version of a single test case as well as multiple test cases on the execution screen. This section describes steps to sync the latest version of multiple test cases at a time.

Steps:

1. Select test cases the latest available version of which you want to sync with the test cycle.

2. Click on the Bulk Operations button and select the Sync with Latest Version option.

The confirmation message appears. Read it carefully.

3. Click Yes to proceed.

The latest version of the test case is synced with the test cycle.

Audit Logs

The syncing of the latest version of test cases is displayed in the Audit Logs tab of the test cycle detail page.

Clone a Test Execution

You can clone the execution of the Test Case. It will clone all steps, defects, and 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 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 Copy icon for the execution that you want to clone.

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.

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 on which you want to sort the test cases.

Group Test Cases

On the execution screen, you can group Test Cases for execution on different attributes.

Open the Group By drop-down and select the attribute you want to group Test Cases on. The Test Cases are categorized accordingly on the left panel.

Assign Execution Status

The testers assign Execution results 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 results 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.

Note: The status of the Execution Result is disabled if all the mandatory execution system and custom fields are not filled.

Assign Status to Test Step

Each Test Case is expandable by 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.

Note: The status of the Execution Result is disabled if all the mandatory execution system and custom fields are not filled.

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.

1. Select Test Cases the Build and Environment values of which you want to change.

2. Click on the Bulk Operation button and select the Update option.

3. Assign/Change the value of Change Environment and Build in respective fields.

Bulk Update Test Execution Results and Execution Custom Fields

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 on the Bulk Operation button and select the Update option.

3. Select the Test Case Execution Result from the drop-down for all the selected test cases.

Note: If Auto Update Execution Result Preference is ON, the Test Steps Result will also get updated.

Update Execution Custom Fields

→ You can bulk update execution custom fields along with changing the execution status of the test cases. The change in custom field values will be applied to all the assets selected for the bulk operation.

Under the Test Case Execution Result section, you can see the Execution Custom Fields panel. Enter required values in the execution custom fields.

Note: The Bulk Update option will replace the empty value and existing values of the custom fields with selected values only in the latest execution result of the test case.

4. Click Update.

Note: The status of the Execution Result for the selected test cases whose mandatory execution system and custom fields are left blank will not change.

→ You can bulk update execution custom fields independently without updating the test case execution result. Select the status “Unchanged” to skip updating the test case execution result.

Note: For selected Test Cases, users will not be able to update the Execution result status if the mandatory system or custom fields are empty on the execution screen. An error message is displayed asking you to fill in all the mandatory fields.

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.

The Execution Assignee field can be filtered for blank values. The Unassigned parameter is provided for the Execution Assignee filter, using which users can filter the test cases and assign the execution assignee to them.

Steps

1. Open the Execution Assignee filter drop-down and select the Unassigned check box.

The filter is added to the Filter panel above.

2. Open the Execution Assignee filter and select the Unassigned check box on it.

The test cases, for which the Execution Assignee field is blank, will be listed on the screen.

3. Select the test cases for which you want to update the Execution Assignee field.

4. Click on the Bulk Operation button and select the Update option.

The Update screen pops up.

4. Select the Execution Assignee from the drop-down for all the selected test cases.

5. Click Update.

The Execution Assignee value will be applied to the test cases.

View Summary

Refer to https://qmetrysupport.atlassian.net/wiki/spaces/QTM4J/pages/1595179526

Execution Logs

Refer to https://qmetrysupport.atlassian.net/wiki/spaces/QTM4J/pages/1565721921

Export Test Execution

Refer to https://qmetrysupport.atlassian.net/wiki/spaces/QTM4J/pages/1595441647