Introduction

Test Cases are a set of conditions that would help testers to determine whether a product works correctly or satisfies the requirements. QMetry allows users to seamlessly create such Test Cases which the testers can make use to even determine the problems with the system or product requirements.

The user should have the “Test Case Create” permission for the project to be able to create a test case in QMetry Jira add-on.

Test Case List View

Users can show/hide all field columns except Sequence No, Key, and Summary in the test case module grid. Columns selected on the list will appear on the test case screen. Columns not selected/deselected will remain hidden on the screen.

To return to the default view of the Test Case list view, open the Columns drop-down and select Reset to Default.

Note: A maximum of 40 columns can be selected at a time to display.

Open

Open

Steps to Create a Test Case

You can create a new test case and directly associate it with a folder.

1. Select a folder on the tree.

2. Click on the New button. The new test case will be associated with the folder you selected on the tree.

There are three tabs: Details, Steps, and Attachments.

Enter Test Case Details.

Note: Inline images added to the test case while authoring will be attached under test case attachments.

• Summary: It is a short description of the test case.

• Description: It describes the test case with more details like images, links, etc. The field has Wiki markup editor. You can use different options that are available to apply to the text. Refer to https://qmetrysupport.atlassian.net/wiki/spaces/QTM4J/pages/1598554359.

• Precondition: It describes the setup required for a test case to carry out its execution successfully.

• System Fields: These are system-defined fields. Enter/select values for the fields. The list values are entered in the Configuration > Project Configuration.

  • Folder Path: It shows the folder path of the test case where it is located.

  • Priority: It shows how important the test case is with priority assigned as - blocker, critical, high, low, etc. You can configure the priority list values from Configuration > Priority.

  • Status: It shows the workflow of the test case with Statuses like To Do, In Progress, Done, etc. You can configure the status list values from Configuration > Statuses.

  • Assignee: It shows the user who is assigned to work on the test case. The user's list displays users who have access to the project.

  • Reporter: It shows the user who has created the test case. The user's list displays users who have access to the project.

  • Components: It references Project Components that you have created in Configuration > Components like UI, Configuration, etc.

  • Labels: It is helpful to group test cases into categories. You can configure the Labels list values from Configuration >Labels.

  • Sprint: The field is useful for Agile methodology where planned tasks have to be completed by the team and made ready for review. It shows the Sprint in which the test case is included.

  • Fix Versions: It shows the version of the software in which the issue is fixed. The field values come from Jira.

  • Estimated Time: Now users can mention the approximate time required to execute the test case. The time should be entered in HH:MM format.

• Custom Fields: Users can add additional fields other than system fields. Custom Fields are added from Configuration > Custom Fields.

Note: QMetry Test Management for Jira uses Jira’s native editor and some characters like backslash used in the wiki markup body become unusable by default. This is a technical limitation from Jira's end. As a workaround, we would suggest you use the 'Code' from the rich text editor to mention any text containing a backslash.

Once you are done entering details, click Create to create the test case.

Create another:

Create another check box allows users to keep on creating one test case after another without having to click on the "Create" button again and again. It is helpful when you have to create a series of test cases.

While creating another entity, values of some fields populate as these field values get preserved.