Test Execution


Test Run Detail


The Execution screen displays Test Case records. Pagination is available when the test case count exceeds fifty. You can directly jump onto a specific page by entering the page number in the box.



A. Platform: The value is editable. Select the value from the drop-down. You can even add new platform from the screen by clicking on the Add Platform link on the list.

B. Comment: It is editable. Just hover the mouse over it.

C. You can filter out test case records by applying different criteria.

  • Assigned To
  • Execution Result
  • Issues with Bugs
  • Story
  • Test Scenario
  • Label
  • Version
  • Component
  • Sprint
  • Project

Filters will be preserved user wise. When the user opens the execution screen, they see the same filters applied on the screen.

Story and Test Scenario criteria are also added to let users filter records as per requirement. For example, it helps QA Manager find particular Story/Test Scenario quickly and assign them to testers for execution.


D. Test Cases are expandable to view test step details.


The grid on the Test Run Detail screen includes the following columns:

  • Test Case
  • Execution Result: The field is editable and each row has all statuses on it.
  • Assigned To: The tester to whom the issue has been assigned to execute. The field is editable. You can change the assignee from the screen. The user name populates as you start typing in the field.
  • Defects: Click on the icon to link defects to the test scenario/test case either from the existing ones or by creating new defects and linking them directly. Read more about Log Defects.
  • Attachments: Click on the icon to attach files to the test scenario/ test case. Read more about File Attachment.
  • Comment: You can add or edit comments here. Read more about Comments and Actual Result.
  • Story: Story associated with the test case.

  • Test Scenario: Test scenario associated with the test case.

  • Automation Result: It will only display when automation testing is being performed. Click on the icon to view Automation Test Results for the test scenario/test case. Read more about Automation Details.
  • Step Summary, Test Data, Expected Result, Actual Result: The columns display details entered for Test Steps.


Sorting on Columns

On the Execution Screen, sorting is available on the following columns:

  • Test Case Key
  • Execution Result
  • Assigned To
  • Comments
  • Story Key
  • Test Scenario Key
  • Executed By (Date)

You can sort test cases ascending/descending based on the Issue ID. It helps users arrange test cases in sequence for ease of operation. The sorting is not preserved for future.

To remove the applied sorting, open the Clear drop-down at top right and select Clear Sort. It will remove the sorting and test cases will be displayed in the sequence they were executed.

First mouse click will sort column as Ascending, second mouse click will sort column as Descending, and third mouse click will sort column as Default.


Assign Execution Result

Till now test case status and test step status were independent of each other. QMetry for Jira v3.3 onwards, users can set preference to update test case execution result based on its test step execution result.

Use Case: Testers want to auto update the test case execution status based on test step execution status. For example, if a test steps is failed, then the test case should also be failed.

The option Automatically propagate Test Step Execution result to Test Case is provided as Execution Preferences on the Project Settings (QMetry Configurations > Project Settings).

If the option is enabled

  • when the user executes a test case step, the execution result of test case will be changed according to the priority of execution result set from Execution Results (QMetry Configurations > Execution Results).
  • when the user executes a test case, the execution result of all underlying test steps will be also changed same as test case status.



For example, the set priority of Execution Results is:

  • Blocked
  • Fail
  • On Hold (Custom Execution Result)
  • Not Executed
  • Pass
  • Work in Progress


For the above set priority, see how the test step results impact the execution result of respective test cases.


Test Step/CaseCase 1Case 2Case 3
Test Step 1Not ExecutedPassOn Hold
Test Step 2Not ExecutedPassNot Executed
Test Step 3PassBlockedNot Executed
Test Step 4FailFailNot Executed
TC Execution ResultFailBlockedOn Hold


More Options

The following buttons are available on the screen:

  • Bulk Actions
  • Summary
  • Rebuild
  • Export

Rebuild Test Run

Users can apply rebuild to test assets.

  • Partial Rebuild: This rebuild is applied to particular test cases selected by users. It will update only selected test cases, instead of updating all the test cases within the test run.
  1. To rebuild test cases, click on the Bulk Actions drop-down and select Refresh Test Cases.
  2. Select test cases and click Apply.


  • Full Rebuild: This rebuild is applied at Test Run level. All the test cases within the test run will be synced and updated to the latest ones.

Clicking on the Rebuild Test Run option, reconciles the story within the test run to bring it to its updated status. Read more about Update Test Run Snapshot.

Assign Testers

You can assign tester who will execute the test run. You can assign one tester to the entire story or different testers to different test cases under the story. Read more about Assign Testers.

View Summary/Statistics

To view the Test Case Summary, click on the Summary button at top right corner. To close the view, click on the Summary button again.

The Summary tab shows distinct count of Story, Test Case, Test Scenario and Bugs.



The Test Case tab shows  graph of test case execution result.

The graph displays execution result wise test cases which included under the test run. The table shows the count and coverage of test cases per result.



The Bug tab shows the graph of issues logged during execution of the test run.

The issues are bifurcated as per Defect Status. The table displays priority wise count for each Defect Status.



Customize Execution Screen View

Hide and Show Columns:

On the Test Run Execution screen, users can show/hide test case columns.

For example, QA Manager wants to view only selective fields for test case, for the reason, they hide column they don't want to view on the grid.



A. On the Test Run Execution screen, open the Columns drop-down.

B. Select Test Cases/Test Steps tab the columns of which you want to show/hide.

C. Remove the check box selection of the column you don't want to view.

D. Drag and drop: You can also drag and drop column to rearrange them.


The columns will be displayed as per the visibility and sequence set.

View Test Step Details

Users can have a distraction-free view of test step details on the test execution screen even the test step content is lengthier. The View Details icon turns visible when the content size within the field goes beyond purview. The icon is provided with Test Summary, Test Data, Expected Result, Actual Result, and Comments fields of test step.

Click on the View Details icon for the field. It which opens a pop-up window with complete details on it.


Bulk Update

User can update test run results of multiple test scenarios, test cases and test steps in one go. Read more about Bulk Update Execution Status.

Export

Test Execution Results can be easily exported with Test Scenarios, Test Cases and Test Steps. Read more about Export.