Creating New Test Cases

You can create test cases manually, import them from BDD feature files, or leverage AI to auto-generate them. This flexibility helps teams build and manage test cases based on their preferred workflow.

The Create New Test Case screen provides a unified interface that streamlines the process of test case creation. It allows you to create test cases and manage requirement linking, test suite association, execution planning, and defect linking, all in one place.

To create a new test case manually, perform the following steps:

1. Go to the Test Cases module.

2. Click New.

Open

3. Enter Test Case Details: Fill all required fields with the necessary information.

4. Link Requirements (Optional): You can link requirements to the test case by:

   1. Selecting requirements from the list,

   2. Entering the Requirement Entity Key manually.

5. After entering all relevant test case details, you can:

   • Click Create to save the test case.

   • Click Plan Executions to link the test case to a Test Suite and plan its execution.

6. If Plan Executions is selected:

   • Choose to either

     • Create a New Test Suite

     • Link an Existing Test Suite.

   • After selecting or creating the Test Suite, you will have two options:

     • Link Test Suite and Close
       Links the test case to the selected Test Suite and closes the screen. Execution can be performed later.

     • Execute
       Opens the execution screen, where you can immediately run the newly created test case within the linked Test Suite.

The system saves the test case and redirects you to the Test Case list view, with the new test case added at the end.

The System Fields section contains standard fields for test case definition:

• Custom fields added to the Test Case module appear under User Defined Fields.

• UDFs can include look-up lists, multi-lookup lists, and cascading values.

• Mandatory cascading fields require selecting both parent and child values.

• UDFs can be configured under Manage Fields in Customization.

Open

Test steps define the actions and expected outcomes for test execution.

Adding and Editing Steps

1. Go to the Test Steps section.

2. Click the expand icon for full-screen view.

3. To add a step:

   • Click the Edit (pencil) icon or press TAB to navigate.

   • Click the cog icon and select Insert Row for a new step.

4. Enter the Step Description, Input Data, Expected Outcome, and UDF details(if any).

5. Repeat to add additional steps.

Shareable or Copied Steps

• Insert Shareable Test Case: Click the cog icon, select a shareable test case and link it.

• Copy Steps from Existing Test Case: Click the cog icon, select steps and click Copy or Copy & Close.

• The “+” icon can also insert shareable or copied steps.

User-Defined Test Step Fields

• Additional UDF columns appear beside default fields if added in Customizations.

• Column arrangement changes are reflected across all relevant screens (Execution, Detail, Version, Exploratory Testing).

Editing Steps

• Hover over a step field and click the edit icon to enable inline editing.

• Press TAB or click outside to save changes.

• Enter: Risk Type, Risk Category, Likelihood, Impact.

• The system calculates Risk Priority Number and Extent of Testing, helping prioritize test cases.

Open

To link requirements, perform the following steps:

1. Click Link.

2. You can link requirements by Entity Key or by selecting them directly from the Linking screen.

3. You can create a new requirement from the Linking screen and link it to the test case.

Plan Executions helps streamline test execution. You can either add a new test case to an existing test suite or create a new test suite and schedule its execution.

Open

On clicking Create Test Suite, the creation screen opens. The entity key of the newly created test case is displayed at the top. You can click this entity key to navigate directly to the test case.
All test cases linked to the Test Suite are listed in the Test Cases section.

Open

To create a test suite, perform the following steps:

• Enter Test Suite details and fields.

• Associate a folder path.

• Link one or more Releases, Cycles, and Platforms. This is mandatory.

• By default, Release and Cycle are auto-filled from Test Case. Owner defaults to the logged-in user.

• You can select multiple values in the Release, Cycle, and Platform fields to associate with a Test Suite. The Release and Cycle values are inherited from the Test Case.

Link Existing Test Suite opens the list of available Test Suites in the current project.

Open

A test case can be associated with only one Test Suite.

After selecting the Test Suite to link, choose one of the following actions:

• Link and Close
  Links the test case to the selected Test Suite and closes the screen. No execution runs are created.

• Proceed with Execution
  Links the test case to the selected Test Suite and initiates execution runs. You will be redirected to the Execution Flow screen to begin execution.

• Cancel
  The test case is saved but not linked to any Test Suite, and no executions are created.

Proceed with Execution directs you to the test execution flow. This screen displays the following details:

• Test Suite Key

• Summary

• List of all test case execution runs.

Open

You can edit the following details for each execution:

Open

You can add or link existing bugs directly from the test case execution screen .

• Test Case execution view.

Open

• Step execution view.

Open

Open

You can create a test case directly from a Jira or Azure Work Item that is synced with your QMetry project.

1. Go to the Test Case section within the synced Jira or Azure Work Item.

2. Click +Test.

   • You are not logged in: You will be prompted to log in before proceeding.

   • You are logged in and have Project access: You will be redirected to the Create Test Case screen.

3. The following fields are auto-filled:

   • Project: Same as the project of the source Work Item.

   • Requirement Linking: The Requirement linked to the Work Item is auto linked to the Test Case.

   • Summary, Release and Cycle: Defaulted from the Work Item's summary.

4. The rest of the workflow is same as Creating Test Case from Requirement.

After a Test Case is created, the system navigates to the Test Case Details screen, where the new test case is automatically linked to its originating work item.

You can also create a test suite directly from a Jira or Azure Work Item that is synced with your QMetry project.

• Click the + Suite button.

• This opens the Create Test Suite Screen in QMetry if you are already logged in and have necessary project access rights.

• Similarly, the created test suite gets linked to all test cases associated with the originating requirement work item.

• The following fields are auto-filled:

  • Project: Same as the project of the source Work Item.

  • Requirement Linking: The Requirement linked to the Work Item is auto linked to the Test Case.

  • Summary, Release and Cycle: Defaulted from the Work Item's summary.

• In the Test Case Section, click Create Test Case.

• The following fields are auto-filled:

  • Project: Same as the project of the source Work Item.

  • Issue Linking: The Issue Work Item is auto linked to the Test Case.

  • Summary, Release and Cycle: Defaulted from the Work Item's summary

• Enter all other relevant details.

• Click Create to save the Test Case or Proceed with Execution to link a test suite and execute the test case.

• The Issue gets auto-linked to the created test case.