| Table of Contents | ||
|---|---|---|
|
...
Show More Columns: The ability to add columns in the view. If there are other columns that you think important to display on the module grid apart from the default view, then you can just select those columns to add them to the view.
Hide Columns: The ability to remove a column from view. If you do not want to include columns of less important on the module grid view, then remove column selection to hide those columns on the view.
Users can show/hide the Testing Type field in the 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.
Re-arrange: The ability to arrange the columns in a different order through drag and drop functionality.
...
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.
Apply Filter
Users can apply basic as well as advanced filters to the records.
...
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.
...
Testing Type: You can see this field on the 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 that 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.
...
Show/Hide and Re-arrange Test Step ColumnsUsers can opt to show/hide test steps columns (Input Data, Expected Outcome) and arrange the test steps columns on test case create screen and the Steps tab on the test case detail page.
You can organize the test steps columns in the panel through drag and drop operation. You can also opt to hide/show Input Data and Expected Outcome columns on the screen.
...
As an alternate way, you can click on the Edit icon for the step that you want to edit.
The step section opens in the expanded view.
...
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.
...
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.
Archiving a Test Case
All the versions of the test case should be archived to delete that particular test case.
Archiving Entire Test Case
...
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:
...
Deleting Entire Test Case
All the versions of the test case should be archived to delete that particular test case.
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.
...
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.
...
B. To unlink multiple requirements, select requirements you want to unlink from the test case and click on the Unlink Selected button.
Linking Test Suites to Test Cases
...
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 Link icon to link the individual test suite to the test case.
...
While import any change in the status of such archived test case executions will be ignored.
If test suites from other project are linked, then the test suites show Entity Key of the corresponding project.
...
Test Suites key will be ignored if relevant test suite with that key is not found.
If a single key is mentioned multiple times, it will be linked only once.
Archived test suites will be skipped from linking. Only unarchived version of entities will be linked.
Skip Duplicate Linkage is "On": If the test case is already linked with a test suite, then the linked test suite will be skipped. Only those test suites will be linked which are not yet linked with the test case version from where the linking is being performed.
Skip Duplicate Linkage is "Off": The test case version from where the test suite is being linked, that version will get linked to all the test suites.
Steps
1. Go to the Test Executions tab of the test case.
2. Click on the Link Test Suites By Entity Key button.
3. It opens the Link Test Suites pop-up. Mention comma separated Test Suite keys.
...
The Test Executions tab shows the last execution build for the test suite. It is useful when a QA Manager/Tester wants to see the latest Build against which the execution was done on 'Test Executions' tab of Test Case screen.
View Test Run Logs
...
The associated release and cycle appear in the grid on the screen.
To remove the release and cycle association for the test case, click on the Unassociate button for the release and cycle combination.
...