In-place edit will always update the test asset.
To create a new version of test asset, follow the steps mentioned below.
Back to QMetry All Products Help Page
Test Cases Module is the central repository of test cases. A single test case can be used repeatedly and associated with multiple releases and cycles- avoiding the need to copy test cases. The execution status of test cases is independent per cycle allowing organizations to repeatedly execute the same test case without affecting the test results between separate runs.
With the Test Cases Module you can:
The Test Case module screen has the following UI.
All grids within Requirements, Test Cases, Test Suites, and Issues module have Arrange Columns option that allows users to create a customized view of their test assets.
The view is saved for future use.
The following customization can be applied:
Users can show/hide Testing Type field in Test Case module. If users want to use their own UDF instead of this field, they can hide it. The setting is provided in the Manage Fields section of the Customization module. Refer to Manage Fields for more details.
You can search for a particular column through the search box.
Just click on the Test Case Key in the grid view to open the test case detail page on the same page.
To open the test case detail page in new tab/window, right click on the Test Case Key in grid view. Opening test cases in different tab/browser makes comparison between test cases easier. It also provides quick reference while working on multiple assets.
The detail page is redesigned that allows one click access to different sections using organizable tabs.
Organize Tabs
The detail page of QMetry assets has different tabs on it. Users can customize the view of detail page by changing the order of tabs. The tab order is preserved per user.
For example, the tab order of Test Cases module is changed by user "A" for project "PRO1". Now "A" is switching to another project "PRO2". The tabs can be seen in the same order as in project "PRO1".
Combined View vs. Grouped View
A. Individual Section Tabs
B. Combined View (Read Only View)
A. Individual Section Tabs
For Test Case: There are individual tabs for Steps, Details, Requirements, Release & Cycles, Test Executions, Issues, Version, Attachments, Comments, Change Log
Each tab displays relevant details. The details are editable.
B. Combined View (Read Only View)
The tab renders the old view of details page. You can view the details of all the section on a single page. The details displayed on the page are read-only and it can not be edited.
The Previous and Next buttons on the detail page are added for ease of navigation and updation of test cases.
Users can easily filter test assets by any system/custom fields on all module grids. It also helps users in carrying out bulk operations. Filters placed horizontally above the grid earlier, are now placed on the tree panel at left.
Testers can view details grid aligned with folder tree even when they are clicking a folder which is at the bottom. It displays top of the screen instead of bottom of the screen.
Apply Filter
Users can apply basic as well as advanced filters to the records.
A. Basic Filters: By default, basic filter fields are provided to filter the records.
B. Advanced Filters: If users need more fields to filter test assets then click on the '+' icon. It opens the drop-down with a list of additional system and user defined fields corresponding the module.
Select the field you want to apply filter on. The filter parameter is added as Advanced Filters. Apply filter as per your requirement.
For example,
Users want to filter test assets on Priority, Entity Key and Status, then click on the '+' icon and select the fields on the drop-down list as shown below.
Clear Filter and Sorting
Users can clear the applied filter and sorting to the records.
A. Clear Filter: Click on the Clear Filters button above the module grid or on the left pane. It will reset the view to default.
B. Clear Sorting: Click on the Clear Sorting button above the module grid.
Users can opt to include or exclude test assets from sub folders at parent folder. By default, Include Entities from Sub-folder remains selected, and entities from sub-folders are displayed at parent folder level on the module list view.
To hide the entities from sub-folder, open the Options drop-down on the test asset tree at left, and select deselect Include Entities from Sub-Folder.
Once you are on the test case details page, you can go back to the main screen of test cases by clicking on the breadcrumbs.
Test cases are added at the Project level. The Test Case module main screen displays test cases in the Project as per folder selection. You can apply filter to the columns as mentioned above. Multiple columns can be filtered at once to help users find the required test cases.
QMetry allows testers to organize and manage test cases in a Folder based hierarchy. Testers can group related test cases and organize them systematically during authoring or post authoring.
It helps carrying out bulk operations like Move, Copy, Editing, Deleting, Executing all test cases under one folder, etc.
On the Test Case module toolbar, click on the New Folder button to add a new test case folder.
Enter the following fields to add a new folder:
Click Create. The new folder is reflected on the tree.
Note: The following permissions related to the Test Case module are set from User Role for individual roles.
Make sure you have relevant rights to carry out the operation.
Select the folder on tree and click on the Edit icon on the toolbar.
The folder detail screen opens in editable mode.
Select the folder on tree and click on the Delete icon on the toolbar.
On deleting a folder, all the sub folders and entities within the folder will be deleted. The status of the parent folder will get re-calculated in all the scopes that this folder was present in. Root folder cannot be deleted.
On the Test Case module toolbar, click on the New button.
The Add Test Case screen has the following fields on it.
Use Case: Tester writes a test case based on requirement specifications and assigns this test case to the Testing Lead with status “New”. The Testing Lead then reviews the test case and assign status “Reviewed” or “Ready”, if the test case is written properly.
Rich Text:
A. Use of Rich Text Editor allows users to apply text formatting for Test Case Description and reduces chances of missing important details.
B. Users can paste the html/xml content into the Source editor of the "Large Text" field type and it auto-renders the code to show the text outputs on the screen.
Use Case: An organization is using Rich text for Description field, in which they copy-paste the content from their source in html/xml format.
Click on the Edit icon at right to open the source editor.
Note: To enable rich text editor, the Enable Rich Text parameter should be enabled for the Project (Projects > Project / Release / Cycle). Refer to Enable Rich Text Editor for more details.
Enable Rich Text and Source Code Editor: Refer to the Description field above.
You can add test steps that are to be executed under the test case. View, Create, Edit and Delete rights for Test Case are allocated to user roles from Customization > Roles. Users can perform operation as per the permission granted to their user roles.
Steps
A blank row is added on the grid with auto-generated Step number. Enter Step Description, Input Data and Expected Outcome in respective fields by clicking in the cell.
Repeat the same process to add other steps.
Rich Text Editor for Steps
There are two formats in which you can add test steps: Plain Text and Rich Text.
Enable Rich Text and Source Code Editor: Refer to the Description field above.
Note: To enable rich text editor, the Enable Rich Text parameter should be enabled for the Project (Projects > Project / Release / Cycle). Refer to Enable Rich Text Editor for more details.
Click on the Con icon.
It allows you to perform the following actions on the Steps grid:
Click on the Create button to save the test case.
When you open the test case detail page, the Test Case Folder Path displays the path upto the folder the test case lies within.
Also refer to Editing a Test Case section on this page.
While executing test suite, the test case steps appear in the same sequence as you arranged them here for the test case.
You can easily change the order of test case steps through the following way:
Users can get more granular details by adding attachments at test steps. For example, a test step needs to be tested with different test data. The tester attaches an excel sheet containing the test data to keep it ready for execution.
Note: Attachments to test steps can be added either on the test case detail page or on the test case edit page.
A test case can be edited in terms of its parameters and test case steps.
Users can save the test case without creating its new version. In-place editor is provided on the detail screens for all test assets. Just hover over the field and click on the edit icon.
It opens the field in editable mode. In case of text field, enter the value and save the details.
To edit existing test steps, click on the Edit button in the Test Steps section.
In-place edit will always update the test asset.
To create a new version of test asset, follow the steps mentioned below.
If test case steps are added or edited in test case, which is already executed, then it is recommended to save the test case with Save as New Version.
If the User Role has Versioning rights (in Customization > Roles), then the button will be visible to the user. When you edit test case details, you can save the details with a new version of that test case.
Follow either (A) or (B) as mentioned here.
A. Click on the Con icon for the test case and select Create New Version.
B. Open the test case detail page and click on the Create New Version icon on the header.
The next screen opens in editable mode.
Make required changes and click on the Save as New Version button to create a new version of the test case with updates.
If you add/edit test steps within a test case, it will ask you to create a new version of the test case to save the content of steps along with test case parameters. The associated test suite will still be associated with the previous version of the test case.
If the test case was executed before, then the following option is provided while saving the new test case version.
Example: TC1 has execution status “Passed” in TS1. User modifies TC1 details and selects this option to reset the test case execution status while saving TC1. Now TS1 will show TC1 execution status as “Not Run”.
If the above option is not selected, then on the Test Run screen the sync icon appears beside the current version of the test case. On the Test Execution screen, to execute the latest version of test case, click on sync button.
The confirmation message pops up confirming reset of execution status. The synced version will not show previously linked issues.
After syncing the test case with its latest version, its Execution Status changes to "Not Run".
If test steps were added in the latest version of test case, then these test steps will also be added on the execution screen.
Note: QMetry allows you to use different versions of a test case for testing. Read more about it on the Managing Test Case Versions page.
All the versions of the test case should be archived to delete that particular test case.
You can not carry out further operations like adding attachments, linking test cases, issues, and release - cycles on an archived test asset.
A. Archiving from Test Case detail page
B. Archiving from Test Case module list view
A. Archiving from Test Case detail page
Open the test case details page by clicking on the test case.
Click on the Archive icon on the top right corner of the page.
It will archive all the underlying versions of the test case.
B. Archiving from Test Case module list view
Open test cases module.
The test case list view opens with list of existing test cases within the project/folder.
Click on the Cog icon for the test case you want to archive and select Archive. The test case is archived after confirmation.
To unarchive an archived test case, click on the Unarchive icon at the top right corner.
Read Archiving a Specific Test Case Version
To delete a test case, first you need to archive it. All the versions of the test case should be archived to delete that particular test case.
It is a two step process:
All the versions of the test case should be archived to delete that particular test case.
A. From Test Case detail page
B. From Test Case list view
A. From Test Case detail page
Once the test case is archived, it looks like below.
The Delete icon now appears at the top right corner of the page.
Confirm the operation on the pop-up.
B. From Test Case module List view
To view the archived test cases on the screen, select the Show Archived Items check box above the grid.
It displays archived test cases along with other test cases.
Click on the Cog icon for the archived test case and select Delete.
Read Deleting a Specific Test Case Version
Read Bulk Operations
You can link requirements with their relevant test cases. You can link a requirement to a test case only once.
When a requirement is linked to a test case, it is linked with all versions of that test case.
Use Case: Users link requirements with related test cases for testing. Testers get idea of what is developed by studying requirements and on that basis, they write test cases to describe how to test the developed application. Thus, linking test case with requirement gives relevance between the two what is developed and what to test.
Requirements can be linked to test case through the Requirements tab available on Test Case details page and Test Case edit screen.
Steps
Selecting Requirements Across Projects:
Users can link requirements from other projects as well. The Project drop-down is provided to select the project. The requirements for the project are displayed on the screen.
Use Case: Each version of the requirement is expandable so that users can view details of all versions at one place.
Expand the requirement and select the required version to link with the test case.
If you want to link requirements 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 them before moving to Project 2. Else, all the selection of Project 1 will be wiped off.
A. Linking a Single Requirement: Click on the icon to link the individual requirement to the test case.
B. Linking Multiple Requirements: Select requirements that you want to link and click on the Link Selected Requirements button at the bottom.
The selected requirements are linked to the test case. The linked requirement records are shown on the lower grid pane.
If requirements from other project are linked, then the requirements show Entity Key of the corresponding project.
To view the requirement of other project, 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 latest version of requirement to a test case using requirement key separated by comma. Maximum 500 entities can be linked at a time.
Use Case: The feature is useful to link requirements to a test case without searching them individually. For example, users have the list of requirement keys to be linked to a test case, they can use this option to link the requirements directly. This feature will save the users' time in searching requirements in different folders to link them.
Notes:
Steps
3. It opens the Link Requirements pop-up. Mention comma separated Requirement keys.
4. Click Link.
The requirements with mentioned keys get linked to the test case.
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 through the Test Executions tab available on Test Case details page and Test Case edit screen.
Test Suites are linked to the test case in multiple of Platforms associated with it.
Selecting test suites Across Projects:
Users can link test suites from other projects as well. The Project drop-down is provided to select the project. The test suites for the project are displayed on the screen.
You can apply multiple criteria to filter test suites records within and across projects.
Note: User should have 'Modify' rights of the Test Suite module in the targeted project from which the test suites are being linked.
Open the Test Executions tab and Click on the Link Test Suites button. It opens Link Test Suites pop-up.
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 them before moving to Project 2. Else, all the selection of Project 1 will be wiped off.
A. Linking a Single Test Suite: Click on the icon to link the individual test suite to the test case.
B. Linking Multiple Test Suites: Select test suites that you want to link and click on the Link Selected Test Suites button at the bottom.
The selected test suites are linked to the test case. The linked test suites records are shown on the lower grid pane.
If test suites from other project are linked, then the test suites show Entity Key of the corresponding project.
To view the test suite of other project, click on the Test Suite Entity Key. It opens the test suite detail page in the respective project and will change your current project.
In case of eSignature feature:
eSignature in current Project | eSignature in Test Suite Project | Can test suites be linked with the test case? |
---|---|---|
disabled | enabled | No (The Project drop-down on the Link Test Suite screen will only show those projects which have eSignature feature disabled) |
disabled | disabled | Yes |
enabled | enabled | Yes |
enabled | disabled | Yes |
If the eSignature feature is enabled in the Project -
Test Case Status | Can test suites of any project be linked with the test case? |
---|---|
Approved | Yes |
In Review | No |
Link Test Suite Bulk Operations
You can link test suites from multiple projects also through Test Case Bulk Operations.
All scenarios mentioned above also apply to bulk operation of test cases.
You can link test suite to test cases through -
Test Case module > Bulk Operations > Edit > Select Records > Link Test Suites.
The feature allows you to link test suites to a specific version of test case using test suite key separated by comma. Maximum 500 entities can be linked at a time.
Use Case: The feature is useful to link test suites to a test case without searching them individually. For example, users have list of test suite keys to be linked to a test case, they can use this option to link the test suites directly. This feature will save the users' time in searching test suites in different folders and link them.
Notes:
Steps
3. It opens the Link Test Suites pop-up. Mention comma separated Test Suite keys.
The test suites with mentioned keys get linked to the test case.
Test run logs to test case are attached at test run level. These logs are available to view and download on the Test Executions tab of test case details page. If a test suite has attachment(s) attached to it, then Attachment icon is displayed in Blue color for that test suite. Only test case level attachments will be displayed here.
The attachments at test run level are displayed to provide more in-depth information on test case execution. Users can get execution details of the test case on the same screen.
Click on the Blue attachment icon. It opens the Attachments pop-up as below.
Open the test case detail page and open the Test Executions tab. Users can view Execution Time and Remaining Time calculated for Test Execution.
Use Case: Calculation of Execution Time and Remaining Time for test suite is useful for QA Manager in Test Planning as it gives accurate estimates for the test suite. These test case level estimates refine each time a test suite is executed. Testers can make recommendations to have the test estimates revised based on the last few executions in different environments.
Two columns Execution Time and Remaining Time are added on the grid at the following places in the application:
Calculation of Execution Time of a test suite:
Execution Time of a test suite is calculated based on Estimate Time of all the test cases in that test suite.
Calculation of Remaining Time of a test suite:
Once the test suite is executed, the Remaining Time Is calculated of all “Not Run” test cases. Any test case with “Failed” or “Blocked” status will also be considered as the work still remains on it.
The Remaining Time will be reduced for test cases with “Pass” and “Not Applicable” status accordingly.
Example
The following example shows calculation of both – Execution Time and Remaining Time.
Execution time | Status | Remaining time | |
---|---|---|---|
TC1 | 2 | Pass | - |
TC2 | 3 | Not Applicable | - |
TC3 | 4 | Failed | 4 |
TC4 | 5 | Blocked | 5 |
14 | 9 |
Execution Time = 14
Remaining Time = 9
The Issues tab on the test case details tab shows all the issues linked to the test case from the test execution screen.
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 the reason, they edit the test case and associate new release and cycle to it.
Release and Cycle can be associated from test case detail page as well as test case edit page.
To remove the release and cycle association and to remove the scope for the test case, click on the Unassociate button.
Read about Test Case Versions
Read about Change Log
Importing Test Cases from Excel File
Read Exporting Test Cases
To view the test case detail in PDF, open the Combined View tab on the test case detail page. Click on the PDF icon on the header.
The PDF showing test case details opens in new tab.
You can download the file to save test case details onto your local drive.
eSignature feature: If the eSignature feature is enable for project, then the report also includes Approval Workflow details for the test case.
Tip #1: Before Adding test cases establish rules to how test cases are to be designed, categorized, and organized. QMetry comes with a number of system fields. All of the fields, along with the folders can help teams better manage their test cases. In addition, the Status field can be used to create a workflow to improve the development of the test cases from "New" to "Approved".
Tip #2: QMetry allows testers to provide actual results and record status at a test case level which may change how you design test cases moving forward. Teams should properly define how and when to add test case steps.