| Table of Contents | ||
|---|---|---|
|
...
A test suite contains a set of the test cases organized in a specific order to be executed. It is usually created to test a complete end to end test case scenario. A test suite may also be created to test a complete set of test cases by type like a BVT, smoke test, regression, etc.
In QMetry, test suites are part of a specific cycle; however, you can copy test suites from one cycle to the next. This allows QA groups to plan out testing for a specific development cycle. Test Suites are executed against a platform which that provides any needed environmental or configuration information. This is to help QA understand not just what functions were tested, but against what hardware and/or software it was tested.
...
- Show More Columns: The ability to add columns in the view. If there are other columns that you think are 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.
- Re-arrange: The ability to arrange the columns in a different order through drag and drop functionality.
...
Select the field you want to apply filter on. The filter parameter is added as Advanced Filters. Apply filter as per your requirement.
User can click on the '+' icon and select the field Entity Key to search test suites using comma separated entity IDs (i.e without specifying the complete Entity Key as described below)
...
The pop-up shows two options on it: Create Test Suite and Create Folder.
The Create screen opens for the test suite.
Enter the following fields to add a test suite:
- Summary
- Owner
- Status
- Associated Releases: Selecting Release and Cycle is mandatory for execution. While adding a test suite, select the release and cycle for which the test suite is being added. The list of releases appears as per the releases added on the project details page (Projects > Project / Release / Cycle). Select the release under which you want to cover the test suite.
- Associated Cycles: Selecting Release and Cycle is mandatory for execution. The cycle list is prompted for the selected release.
- Description: Enter the description for the test suite. 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 Description and reduces chances of missing important details. Users can also insert images, hyperlinks and tables to the field.
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 the 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.
...
- Platforms: It is mandatory to link the platform for the execution of the test suite. Read more details in the section below.
- Link Test Cases: It is mandatory to link at least one test case to create a test suite. Read more details in the section below.
...
- Click on Link Test Cases from Requirement button.
- A pop-up window with list of Requirements opens. The window displays only those requirements which have test cases associated with them.
- Filter the requirements based on your scope of testing. Use filter option based on Summary, Version Id, Priority, Labels, Releases, Cycles, Created By, and Folder path.
- Select the requirements.
- Click on the Link Selected Requirement button.
- Test Cases associated with the selected requirements will be linked to the test suite.
...
- Select test cases that you want link to the test suite. The Filters will populate only for the selected Project. Additional filters Labels and Folder path are added for the ease of searching.
- You can select a particular Version of the test case to link to the test suite. Test Cases with multiple versions are expandable.
...
(A) Copy Existing Release & Cycle
Select a folder on the tree in which the test suite is to be copied.
The check boxes - Platforms, Release & Cycle and Reset to Not Run are selected by default.
- Platform: Select the check box to copy the associated platform with the test suite that is being copied. This option is selected by default; however, some companies who change platforms frequently between releases may opt to deselect this from time to time to avoid adding a lot of test runs with platforms that are not needed for testing.
Use Case: A QA manager of a mobile app company needs to copy the regression suite from the last release to the new test cycle; however, they do not want to copy platforms because the mobile devices they needed to test against have changed.
- Release & Cycle: Select the check box to copy Release & Cycle associated with the test suite. This option is selected by default. If you do not want to copy the releases and cycles associated with the test suite, then deselect this option.
- Test Case Version: It will sync test cases with the latest unarchived version of the test case that is associated with the test suite. This allows users to easily create regression suites using latest unarchived version of test cases. If you want to use the preserved version of the test case then deselect this option.
- Reset to Not Run: Select the check box to reset the test case execution status to Not Run.
- Reset Assignee: Select the check box to reset the Assignee.
- Execution Status: On the Execution Status drop-down, select the Execution Status of test cases you prefer to copy the test cases of.Copy platform with selected Execution Status: Users can copy Platforms based on selected Execution Status above. Only those platform will be copied which has test case with selected execution status. The check box is enabled on selecting the Execution Status. Select the check box to copy platforms which has test cases with selected status run.
Use Case: While copying a test suite, testers want to copy only "Failed" test cases, and only the Platforms that have the failed test cases, so that while testing in a new sprint, they test only the failed test cases, on the platforms on which they have failed. They do not need other platforms to be copied.
(B) Link New Release & Cycle
...
5. The following is the screen to select an existing folder/create a new folder and other options to copy test suites. Then click Copy.
Select a folder on the tree in which the test suite is to be copied.
The check boxes - Platforms, Release & Cycle and Reset to Not Run are selected by default.
- Platform: Select the check box to copy the associated platform with the test suite that is being copied. This option is selected by default; however, some companies who change platforms frequently between releases may opt to deselect this from time to time to avoid adding a lot of test runs with platforms that are not needed for testing.
Use Case: A QA manager of a mobile app company needs to copy the regression suite from the last release to the new test cycle; however, they do not want to copy platforms because the mobile devices they needed to test against have changed.
- Release & Cycle: Select the check box to copy Release & Cycle associated with the test suite. This option is selected by default. If you do not want to copy the releases and cycles associated with the test suite, then deselect this option.
- Test Case Version: It will sync test cases with the latest unarchived version of the test case that is associated with the test suite. This allows users to easily create regression suites using latest unarchived version of test cases. If you want to use the preserved version of the test case then deselect this option.
- Reset to Not Run: Select the check box to reset the test case execution status to Not Run.
- Reset Assignee: Select the check box to reset the Assignee.
- Execution Status: On the Execution Status drop-down, select the Execution Status of test cases you prefer to copy the test cases of.
- Copy platform with selected Execution Status: Users can copy Platforms based on selected Execution Status above. Only those platform will be copied which has test case with selected execution status. The check box is enabled on selecting the Execution Status. Select the check box to copy platforms which has test cases with selected status run.
Use Case: While copying a test suite, testers want to copy only "Failed" test cases, and only the Platforms that have the failed test cases, so that while testing in a new sprint, they test only the failed test cases, on the platforms on which they have failed. They do not need other platforms to be copied.
Moving Test Suites
You can move test suites in three ways -
...
3. The Bulk Operations pop-up opens. Select the Move option and click Next.
4. Select test suites to be copied and click Next.
5. Select the destination folder to move the selected test suites. You can also create a new folder to move the test suites. Click Move.
Deleting a Test Suite
You need to archive test suites before deleting them. The Delete option will be enabled only for archived test suites.
...