Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. On the Test Case Step(s) grid, click the Cog icon for the step you want to remove.

  2. Select Remove Row.

  3. Click Update.

...

Image Added

→ Delete/Remove Test Steps in Bulk

...

If requirements from other project projects are linked, then the requirements show Entity Key of the corresponding project.

To view the requirement of other projectprojects, click on the Requirement Entity Key. It opens the requirement detail page in the respective project and will change your current project.

...

The feature allows you to link the latest version of the requirement to a test case using the requirement key separated by a comma. Maximum 500 entities can be linked at a time.

...

  • Requirement key will be ignored if a relevant requirement with that key is not found.

  • If a single key is mentioned multiple times, it will be linked only once.

  • If an older version of the requirement is already linked and you are linking the same requirement key, then the latest version will not replace the older version. It will be skipped.

  • Archived versions will be skipped from linking. Only the latest unarchived version of entities will be linked.

...

How to Unlink Requirements Linked to a Test Case

Open the the Requirements tab on the test case details page.

...

B. To unlink multiple requirements, select the requirements you want to unlink from the test case and click on the Unlink Selected button.

...

You can link test suites with relevant test cases for testing. QMetry allows users to link test suites of multiple projects to a test case. Test Suites can be linked to test case cases through the Test Executions tab available on the Test Case details page and Test Case edit screen.

Test Suites are linked to the test case in multiple of Platforms associated with it.

...

If you want to link test suites from multiple projects, then first select one project. Search records and link them before moving to other projects. For example, User A is in Project 1 and searches for some records and link links them before moving to Project 2. Else, all the selection of Project 1 will be wiped off.

...

All scenarios mentioned above also apply to the bulk operation of test cases.

...

Test run logs to test case are attached at the test run level. These logs are available to view and download on the Test Executions tab of the test case details page. If a test suite has an attachment(s) attached to it, then the Attachment icon is displayed in Blue color for that test suite. Only test case level attachments will be displayed here.

The attachments at the test run level are displayed to provide more in-depth information on test case execution. Users can get the execution details of the test case on the same screen.

...

Release and Cycle can be associated from the test case detail page as well as the test case edit page.

The tab allows users to associate release and cycle to the test case. One test case can be associated with multiple releases and cycles. Release and Cycles are added from Projects > Project/Release/Cycle.

Once the test case is added, the user wants to add it to a particular Scope - release and cycle. For this reason, they edit the test case and associate the new release and cycle to it.

...