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
On the Test Case module toolbar, click on the New button.
The Add Test Case screen has the following fields on it.
Summary: Enter the name of the test case.
Priority: Select an option from the list.
Labels: You can select multiple options from the list.
Status: Select an option from the list, which contains values like New, Approved, In Progress, Ready to Review, etc. The list is customizable. Users can add more list values from Customization > Lists.
Use Case: Tester writes a test case based on requirement specifications and assigns this test case to the Testing Lead with the status “New”. The Testing Lead then reviews the test case and assign the status “Reviewed” or “Ready”, if the test case is written properly.
Owner: The drop-down list contains QMetry users having rights on the current Project. Select the owner of the test case who will be executing it.
Test Case Category: Select an option from the list e.g. Regression, Performance, Security.
Estimated Time (In Minutes): Mention the estimated execution time of the test case in minutes.
Description: Enter description regarding the test case. Test Case Description can be added either Plain Text or Rich Text.
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 the Description field, in which they copy-paste the content from their source in HTML/XML format.
Click on the Edit icon at the right to open the source editor.
Note: To enable a 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.
Testing Type: You can see this field on test case detail page once a test case is created. The field shows how the test case was created in QMetry: Manual or Automated. If a test case is created through UI or imported from Excel, then it is identified as a manual test case. Test Cases which are created through Automation APIs are identified as Automated test cases. The Testing Type field remains read-only.
User-Defined Fields: If UDFs are added for the test case module, then they are displayed on the Create Test Case screen and Test Case Details screen.
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
Go to the Steps section on the Create Test Case screen.
Follow either of the following ways to add a test step:
Hover the mouse over Step Description cell and click on the Edit icon (pencil). You can also move using TAB on the keyboard.
Click on the "+" icon at the right and select the Insert Row option to insert a new step at the end.
Click on the settings icon for the test step and select the Insert Row option to insert a new step next to the current step.
A blank row is added on the grid with an 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.
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 User Management > 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.
There are two formats in which you can add test steps:
Note: To enable rich text editor, the Enable Rich Text parameter should be enabled for the Project (Projects > Project / Release / Cycle).
Click on the action menu 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.
Note: Attachments to test steps can be added either on the test case details page or on the test case edit page.
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.
Click on the Attachment icon for the test step to which you want to add an attachment.
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 Administration > 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 requirement.
Follow either (A) or (B) as mentioned here.
A. Click on the Con icon for the requirement 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, click on the Save as New Version button 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. To execute the latest version of test case on execution screen, click on sync button.
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.
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 settings 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 check box above the grid.
It displays archived test cases along with other test cases.
Click on the settings icon for the archived test case and select Delete.