Introduction

A test suite in QMetry is a collection of test cases organized in a specific order 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 specific cycles but can be copied to new cycles for future testing.

This allows QA groups to plan out testing for a specific development cycle. Test Suites are executed against a platform 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.

Open

Key Features of the Test Suite Module:

The Test Suite module UI in QMetry enables users to:

• Create and organize test suites for efficient test management.

• Define and manage test case execution plans within each test suite.

• Monitor the status and results of test cases and suites.

• Configure test suite settings and parameters to tailor them to specific testing needs.

Test Suites Module - UI

The Test Suite module screen has the following UI -

Test Suite List View

Open

The Test Suite List View screen enables users to check:

• Total Test Case Executions and Total Unassigned Executions for each test suite.

• Linked Platform and Linked Test Cases Count.

• Total Estimated Time and Remaining Execution Time.

• Review details such as Created By, Updated By, and their corresponding dates.

Additionally, users can filter test suites based on these fields, enabling efficient management and execution tracking.

Use Case: QA Manager wants to quickly view the details of Total Test Case Executions and Total Unassigned Test Case Executions on the Test Suite Screen.

The Test Suite list view screen further allows users to perform the following operations:

1. Create New Folder - Users can organize test suites into folders and subfolders for improved control and management.

2. Sorting and Clear Sorting- The Test Suite module UI provides options to sort by name, date (newest or oldest first), hide empty folders, and include entities from subfolders, enhancing organization and ease of access to test cases.

3. Perform Bulk Operations on Folders - QMetry enables users to perform bulk operations for archiving, unarchiving, copying, and moving folders.

4. Create New Test Suite - Users can create test suites from the Test Suite module UI.

5. Set Filters - Users can easily filter test assets by any system/custom fields on all module grids. It also helps users in carrying out bulk operations. Both basic and advanced filters can be applied to the records.

• Basic Filters: Basic filters like summary, release, cycle, and platform are provided for easy filtering.

• Advanced Filters: For more precise filtering, users can also add custom fields to the filter criteria by clicking on the '+' sign.

To apply advanced filters, these are the steps:

1. Click on the '+' button.

2. Select required filters.

3. Apply filter values.

4. Click ‘save and apply’.

For example, users want to filter test assets on Priority, and Entity Key. Click on the '+' icon and select the fields on the drop-down list. Users can apply an advanced filter on Entity Key to search for test cases using comma-separated entity IDs, without specifying the complete Entity Key, as shown below.

6. Reset Filters and Clear Filter Value - The "Clear Filter Values" option resets the values in the filter fields, allowing users to adjust criteria without recreating the filter, while the "Reset Filters" option returns all filter settings to their default state, removing any selected fields.

7. Manage Grid Columns - All grids within the 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:

Customization Options:

• Show More Columns: Add additional columns to the view by selecting the checkbox.

• Hide Columns: Remove columns from the view by deselecting the checkbox.

• Search: Quickly locate specific fields using the search box.

• Re-arrange: Change column order by dragging and dropping the fields.

• Select All: This will add all available columns to the view.

• Clear All: This will remove all columns except the default ones.

• Restore Default: Revert to the default column settings.

• Resize Columns: The ability to expand and reduce column width. To change the width of one column, just place the cursor in between the columns and drag the boundary on the right side of the column heading until the column gains the width that you want.

8. Import/ Export - The Import option allows users to import test suites from Excel and Jira, while the Export option enables users to export selected test suites to Excel, CSV, Word, or PDF formats.

9. Bulk Operations on Test Suites - QMetry empowers users with the ability to efficiently perform bulk operations on test suites such as editing, copying, archiving, unarchiving, deleting, sharing, and more.

10. Operations on Individual Test Suites - Users can perform various operations on individual test suites, including copy, move, archive, delete, and stop watching.

11. Include/Exclude Test Suites from Sub-folder at Parent Folder

Users can choose to include or exclude test assets from sub-folders in the parent folder view. By default, assets from sub-folders are shown. To hide them, open the Options drop-down and uncheck "Include Entities from Sub-Folder."

12. Icons on Test Suite List View

The table below provides a brief description of the icons in the test suite list view:

Managing Test Suite Folders

Users can organize test suites into folders for more efficient management. Each folder groups test suites with similar attributes, enabling bulk operations such as cut, paste, copy, edit, and delete.

Folders helps users to manage and arrange execution of all test suites based on specific feature/needs. The purpose to add separate folder is to add test suites of similar category to its respective folder so that testers can manage them easily. You can add a new folder to the root itself or as a child of other folder.

The default attributes set for a folder by default applies to all the test suites within that particular folder. Users can also add test suite(s) under root folder. The count of test assets in a folder and total test assets in the folder hierarchy are displayed alongside the folder name. The count includes active + archived test suites.

For example, this is the folder hierarchy: Folder A → Folder B → Folder C

Folder A has 5 test suites, Folder B has 3 test suites, and Folder C has 2 test suites, then the count will be displayed as follows.

Folder A (10) <------ Parent Folder

The Test Suite module main screen displays test suites in the Project as per folder selection. You can apply filter to the columns as required. Multiple columns can be filtered at once to help users find the required test suites.

Adding a Test Suite Folder

The tree/folder panel is expandable, allowing users to widen the area for longer folder names. Users can also hover over a folder to view its full name.

• On the Test Suite tree, click on the New Folder button to add a new folder.

• Enter Folder Name and click Create.

• The new folder is reflected on the tree.

Editing a Test Suite Folder

Steps to edit a test suite folder:

1. Select the folder on tree and click on the Edit icon on the toolbar.

2. The folder detail screen opens in editable mode.

Copying Test Suite Folder

Steps to copy a test suite folder:

1. Go to the Test Suites module.

2. Right click on the test suite folder that you want to copy and select Bulk Copy.

3. Select entities to copy with the folder and click Next.

4. Select Destination Folder and click Copy.

Moving a Test Suite Folder

1. Go to the Test Suites module.

2. Right click on the test suite folder to move and select Bulk Move.

3. Select the Source Folder and click Next.

4. Select the Destination Folder and click Move.

The folder is moved under the destination folder.

Deleting a Test Suite Folder

To delete a test suite folder, users must first archive the folder.

Steps to archive a test suite folder:

1. Select the folder on tree and click on the Archive icon on the toolbar.

2. A confirmation message appears on the screen.

Steps to delete a test suite folder:

1. After archiving a test suite folder, users can view it by enabling 'Show Archived Items' in the filters.

2. To delete, select the folder and click the delete icon on the toolbar.

3. Deleting a folder will delete all the subfolders and entities within the folder.

Test Suite Detail Page - UI

To view the Test Suite detail page, click the test suite entity Key in the grid view. To open the test suite detail page in a new tab/window, right-click on the Test Suite Key in the grid view. Opening of requirements in different tabs/browsers makes the comparison between test suites easier. It also provides quick reference while working on multiple assets.

The detail page is designed that allow one-click access to different sections using organizable tabs.

Navigation

A. Breadcrumb

On the test suite details page, users can return to the main test suite screen by clicking on the breadcrumbs.

B. Previous and Next Button

In addition to that, the Previous and Next buttons (< >) on the detail page also enables easy navigation.

Organize Tabs

The detail page of QMetry assets features various tabs. Users can customize the tab order with the drag and drop feature, and this arrangement is saved for each user.

For example, the tab order of the Test Suites module is changed by user "A" for the project "PRO1". Now "A" is switching to another project "PRO2". The tabs can be seen in the same order as in project "PRO1"

Tabbed View Vs Combined View

Individual Section Tabs - The Test Suites detail page includes tabs for Test Executions, Test Cases, Platforms, Details, Release & Cycles, Attachments, Comments, and Change Log. Each tab displays relevant details. The details are editable.

Test Execution Tab

The test execution tab enables users to execute test runs, schedule test executions, archive test runs, assign tests, share test executions with team, bulk execute test executions and assign planned date to the test suites.

For further information, refer to the Test Suites Module | Test Execution Section in this document

Test Case Tab

Users can view linked test cases on the Test Cases Tab of the Test Suite Detail Page. From this tab, users can also link or unlink test cases, reorder them, and export all linked test cases.

• Link: Users can link individual test cases, or all test cases associated with a requirement using the following options:

  • Test Case

  • Test Case from Requirement

  • By Entity Key From Requirement

  • By Entity Key From Test Case

• Unlink Selected: Users can unlink selected test cases from this screen.

• Export Selected Test Cases: Users can export selected test cases linked with a test suite using this button.

• Change Order: Test cases linked to the test suite will appear in the same order on the test execution screen. However, users can adjust this sequence to match the desired execution flow. Use the Cog icon and select one of the following options:

  • Move Up

  • Move Down

  • Shift to First

  • Shift to Bottom

Details Tab

The Details tab lets the user edit and update the status, owner, description, and execution command of the test suite.

Release & Cycle tab

The release and cycle tab lets the user view the associated releases and cycles to the test suite. The user can further edit, update, unassociate or add new release and cycle from this tab.

Platforms Tab

The Platform tab within a test suite allows users to view all associated platforms. From this tab, users can also link new platforms, unlink existing ones, and view both active and archived linked platforms.

Attachment Tab

The Attachments tab lists all associated files, allowing users to add new attachments, download files, or delete selected attachments from this section.

Read more Managing Attachments.

Combined View

The tab shows the previous view of the details page. All sections are visible on a single page, but the information is read-only and cannot be edited.

Managing Test Suites

Managing test suites in QMetry allows users to efficiently add, organize, filter, and view detailed information for test suites within a project, streamlining test management and comparison.

Adding a Test Suite

To add a test suite, follow these steps:

• Open the Test Suite module.

• Click on the New button on the toolbar.

• The pop-up shows two options on it: Create Test Suite and Create Folder.

The Create screen opens for the test suite.

System Fields

Enter the following fields to add a test suite:

• Summary - Enter the name of the test suite.

• Owner - Assign test suite owner.

• Status - Select suitable status from the drop down.

• Associated Releases: While adding a test suite, select the release and cycle for which the test suite is being added. The list of releases appears according to the releases added on the project details page (Projects > Project / Release / Cycle).

• Associated Cycles: Cycle is mandatory for execution. The cycle list is prompted for the selected release.

• Description: Enter the description for the test suite. This can be added as either Plain Text or Rich Text.

  • Rich Text: The Rich Text Editor allows users to format text, insert images, hyperlinks, and tables, reducing the chances of missing important details.

  • Image Upload: Users can add images up to 1 MB to any Large Rich Text Editor field (System or Custom) by:

    • Browsing and uploading the image,

    • Inserting the image via URL,

    • Copying and pasting the image directly into the editor.

• User Defined Fields: If UDFs are added for the test case module, then they are displayed on the Create Test Suite screen and Test Suite Details screen.

Automation Testing

For Automation Testing, refer to QMetry Automation Agent.

Linking Platforms

Linking a platform is mandatory for executing a test suite. Users must associate platforms with test suites to conduct test runs. A default platform, “No Platform,” is provided for new test suites. Users can add additional platforms via Projects > Platforms.

1. Go to the Platforms section on the Test Suite creation page.

2. Click on the Link button.

3. The Link Platforms pop-up opens with the list of Platforms on it. "No Platform" is available by default.

4. To manage a long list of platforms, users can filter by Platform Name, Creation Date, or Created By.

Use Case: For example, there are thousands of platforms maintained in QMetry. Testers want to link only specific platforms to a test suite. So they can search required platforms with their creation date and created user along with the platform name.

5. Users can also create a new platform from this screen by clicking on the ‘Create New Platform’. It opens the Platforms screen of Projects > Platforms in a separate tab, wherein you can add new Platforms. Read Creating New Platforms. Once you are done adding platforms, reload the Link Platforms screen.

6. Select single or multiple platforms from the list.

7. Click the "Link Selected Platforms" button.

The selected platforms are now linked to the test suite. Navigate to the Test Execution tab on the test suite detail page to view the test suite with the newly linked platforms. If a test suite is saved without linking a platform, a confirmation message gets displayed.

Linking Test Cases

There are three ways to link test cases with Test suite. Linking can be done while adding or editing a test suite. 

• Link Test Cases from Requirement

• Link Test Cases 

• Link by Entity Key

Link Test Cases from Requirement

Linking a requirement to a test suite automatically includes all test cases associated with that requirement, eliminating the need for individual selection. This method ensures comprehensive requirement coverage and traceability, enabling the QA team to monitor requirements from creation through execution.

Additionally, test cases from requirements in different projects can also be linked.

Example:

The requirement titled "Health Parameters" is associated with the following test cases:

• Sleep Tracking

• Calories Tracking

• Stress Tracking

• Step Count

These test cases are associated with the test suite "Health Stats". Now, the test suite “Health Stats” is executed and the respective execution statuses for the test cases are recorded. The entire flow enables you to view the traceability of the requirement “Health Parameters”.

Linking test cases from a requirement minimizes manual effort and saves time by automatically including all relevant test cases. This approach also reduces the risk of overlooking any test cases planned for the requirement.

Steps:

1. Click the Link Test Cases from Requirement button.

2. A pop-up shows only requirements with associated test cases.

3. Users can filter requirements based on Summary, Version ID, Priority, Labels, Releases, Cycles, Created By, or Folder Path.

4. Select requirements to be linked

5. Click the Link Selected Requirement button.

Test cases linked to the selected requirements will be added to the test suite.

Link Test Cases 

Users can link test cases individually by clicking the Link button or choose to link test case in bulk. You can filter test cases, select multiple test cases, and link them to the test suite simultaneously.

Use Case: Link Test Cases enables users to link ad-hoc or additional test cases to a test suite that were not planned/associated to a Requirement. Organizations that manage their test cases only in QMetry and do not use QMetry as requirement repository, should use the Link option to link test cases to test suites.

Steps  

1. Go to the Test Cases section on the Create Test Suite screen.

2. To view the list of test cases that is available to link, click on the Link button.

3. The Link Test Cases screen opens.

Users can apply Basic or Advanced Filters to quickly locate test cases. (Refer to the filters section above for detailed instructions on using filters.)

Additionally, test cases can be viewed based on the following criteria:

• Show Test Cases Linked to Releases and Cycles: Displays test cases associated with the release and cycle linked to the current test suite.

• Show Test Cases Not Linked to Any Test Suite: Identifies all the test cases that are not linked to any test suite for the selected release and cycle, highlighting uncovered test cases. To apply the filter, first select Release and Cycle under Basic Filters.

• Hide Test Cases Already Linked to This Test Suite: Hides test cases already linked to the test suite to avoid duplicate linkage.

• Linking Test Cases From other Projects: Users can link test cases from different projects by selecting the project from the Project drop-down. The screen will then display test cases for the chosen project.

• Finalize Linking: After selecting test cases, click the Link Selected Test Cases button. The test case(s) are linked to the test suite.

If test cases from other project are linked, then the test cases show Entity Key of the corresponding project. To view the test case of other project, click on the Test Case Entity Key. It opens the test case detail page in the respective project and will change your current project.

Link Test Case by Entity Key 

Users can link the latest version of a test case to a test suite using comma-separated test case entity keys. Link Test Cases From Requirement automatically links test cases versions associated to that requirement. If eSignature is On then only “Approved” versions associated to the requirement will be linked.

Use Case: This feature is useful to link test case to a test suite without searching them individually. For example, users have list of test case keys to be linked to a test suite, they can use this option to link the test cases directly. This feature will save the users' time in searching test cases in different folders and link them.

Steps:

1. Go to the Test Cases tab of the test suite page.

2. Click on the Link by Entity Key button.

3. Two options will appear - From Requirement and From Test Case.

4. Select either of the options and a pop-up appears.

5. Enter Requirement entity keys or Test case entity keys.

6. Click on Link.

Editing a Test Suite

An in-place editor is available on detail screens for all test suites. Hover over a field and click the edit icon to open it in editable mode. Users can then enter a new value and save the changes. To modify a value on the test suite details page, simply hover over the field and click the edit icon.

Editing Associate Releases & Cycles

Releases and cycles are initially associated with a test suite during its creation. To update these associations, users can do so via the test suite details page or the edit page.

To associate additional releases and cycles with an existing test suite:

1. Click the Add New button to enable the drop-down menus for selecting releases and cycles.

2. Choose the desired releases and cycles from the drop-down lists.

3. Click Save to apply the new associations. The updated releases and cycles will be displayed in the grid.

To remove an association, click Unassociate for the release and cycle combination you wish to remove.

View Archived Release & Cycles

Users can apply filters to view the required releases and cycles. To view archived releases and cycles, select the Show Archived checkbox in the filter options.

Copying Test Suites 

Users can copy test suites in three ways -

(A) Copy individual test suite

(B) Copy test suite folder

(C) Copy test suites in bulk through Bulk Operations

Copy Individual Test Suites

To copy individual test suites, follow these steps:

1. Go to the Test Suites module.

2. Click on the Cog icon for the test suite that you want to copy and select Copy.

Copy Test Suite Options

The following is the screen to select a folder and other options to copy the test suite. You can either -

(A) Copy Existing Release & Cycle or

(B) Link New Release & Cycle

Copy Existing Release & Cycle

When copying a test suite, users can configure various options:

1. Select Folder: Choose the folder where the test suite will be copied.

2. Platforms: Check this box to include associated platforms. It is selected by default but can be deselected if platforms have changed and are no longer needed.

3. Release & Cycle: Check this box to include associated releases and cycles. This is selected by default but can be deselected if not needed.

4. Test Case Version: Select this option to sync test cases with their latest unarchived versions. Deselect to use the preserved version.

5. Reset to Not Run: Check this box to reset the test case execution status to "Not Run."

6. Reset Assignee: Check this box to reset the test case assignee.

7. Execution Status: Choose the execution status to filter the test cases you want to copy.

   • Copy Platform with Selected Execution Status: Check this box to copy only the platforms that have test cases with the selected execution status.

Link New Release & Cycle

The option to link new release and cycle is only provided for single test suite copy operation.

The additional options on the screen are described below.

• Release & Cycle: Users can link new release and cycle while copying the test suite along with existing releases and cycles of the source test suite. Users can select one release and cycle at a time.

• Status: Select the execution status.

• Select Existing Release - Cycle for Mapping: This option is enabled only when the Reset Assignee checkbox is unchecked, allowing the assignee and status to be copied from an existing Release/Cycle. If the user does not want to reset the Assignee or execution status to Not Run in the new test suite, they should select the existing release and cycle from which to copy these values.

The following matrix shows the impact of the option selected on the screen.

Copy Test Suites in Bulk

1. Go to Test Suites module.

2. Click on the Cog icon on the header at top right and select Bulk Operations.

3. The Bulk Operations pop-up opens. Select the Copy option and click Next.

4. Select test suites to be copied and click Next.

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.

Moving Test Suites 

Users can move test suites in three ways -

• Move individual test suite

• Move test suite folder

• Move test suites in bulk through Bulk Operations

Move individual test suites

1. Go to the Test Suites module.

2. Click on the Cog icon for the test suite that you want to move and select Move.

3. Select the Destination folder in which you want to move the test suite and click Move.

Move test suites in bulk

1. Go to the Test Suites module.

2. Click on the Cog icon on the header at the top right and select Bulk Operations.

3. The Bulk Operations pop-up opens.

4. Select the Move option and click Next.

5. Select test suites to be copied and click Next.

6. 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

Users need to archive test suites before deleting them. The Delete option will be enabled only for archived test suites.

Archive Test Suites

User can archive test suites through any of the following ways:

• Clicking on the Archive icon at the top right corner on the test suite details page.

• Clicking on the Archive option on Cog icon of individual the test suite on the grid.

• To archive multiple test suites at once, select Bulk Operations > Archive Records. The screen only displays archived test suites.

• To view archived test suites on the grid pane, open the filter panel by clicking on the Filter icon. 

• Select the Show Archived Items check box.

• The grid pane at right starts displaying the archived test suites.

User can delete test suites through any of the following ways:

• Clicking on the Delete icon at the top right corner on the test suite details page.

• Clicking on the Delete button on the Edit screen of the test suite.

To delete multiple test suites at once, select Bulk Operations > Delete Records. The screen only displays archived test suites.

Sharing Test Suites with Other Users

Share Test Suites

Users can share a test suite with others via email. The recipient receives an email with the test suite summary, the message provided, and a link to the specific test suite for easy access.

Steps:

1. Open the test suite details page.

2. Click the Share icon at the top. The Share pop-up will appear.

3. Enter the email addresses of the users to whom the test suite should be shared. Multiple email addresses can be added.

4. Enter the message to be included in the email.

5. Click the Share button.

Copy Test Suite Link

Users can copy the test suite link and share it with other users to provide direct access to a specific issue. Authorized members can access the test suite directly via the shared link.

→ The following is the syntax of the URL:

https://<URL>>/#/<AssetType>/<AssetKey>

For example,

https://qtmtest.qmetry.com/#/test-suites/FIT-TS-9

Steps

1. Open the test suite details page.

2. Locate and click on the Copy Link icon on the breadcrumb navigation.

3. Users can share this link via any preferred communication channel.

Export Test Cases Linked to Test Suite

Users can export test cases linked to a test suite, allowing QA Managers to review selected fields in a PDF or Word format.

Options:

• Export all test cases

• Export selected test cases

Steps:

1. Navigate to Test Suite > Test Cases tab.

2. To export all test cases, click the Export All Test Cases button at the top of the test case list.

3. To export desired test cases, select the test cases to export and click on the Export Selected Test Case button.

4. Select the format PDF or Word to export the test cases.

5. Select the page orientation: Portrait or Landscape.

6. Open the Test Case Fields drop-down, and open the Test Cases/Test Steps tab.

7. Select the fields you want to export the details of the required fields of the test cases and test steps.

8. Click Save.

9. Select from the Additional Options:

• Test Suite Details

• Test Case Approval Details (This option is available only for the eSingature-enabled projects.)

• Issues Linked to Test Cases

• Requirements Linked to Test Case

10. Click on the Export button.

Users can view the progress in the Scheduled Task section.

Test Execution

Platform-wise records appear on the Test Execution tab once you associate Release, Cycle, and Platform to a test suite. Test Execution records are added on the screen in accordance with the number of platforms, releases, and cycles linked to the test suite.

For example, if there are 2 Releases, 4 Cycles, and 2 Platforms associated with the test execution, then the number of test execution records will be 16 for each combination of Release - Cycle - Platform.

The screen displays details like Test Suite Summary, Release, Cycle, Platform, Status, and Execution Time.

Customize the Test Execution Tab View

Users can adjust the Test Execution tab view in the test suite through the arrange column option on the screen.

• Show/Hide Columns: Select or deselect checkboxes to display or hide specific fields accordingly.

• Reorder: Reorder columns to fit preferred layout by dragging and dropping the fields.

• Resize Columns: Adjust column widths for better visibility by dragging the borders.

Users can also filter and sort test suite executions by different fields to easily find related information.

Test Execution Tab Fields

• Execution Type

• Status

• Total Test Case Executions and Total Unassigned Test Case Executions

Assign Tester

To assign a tester to execute a test suite on a specific platform:

1. Select the test suite(s) by checking the corresponding boxes.

2. Click on the Assign Tester button.

3. Choose a user from the drop-down menu.

The selected tester will be assigned to execute the chosen test suite on the designated platform.

Planned Date of Execution

You can manually record the planned execution date for each test case run using the "Planned Date” field. This feature enables testers to schedule and document intended execution dates, improving visibility, tracking, and reporting for planned versus actual timelines while ensuring alignment with project schedules.

Steps

1. Navigate to the test execution tab on the test suite module.

2. Select the desired test execution runs. To perform a bulk update, select multiple test execution runs.

3. Click on the planned date field and select the desired date.

4. If execution is not planned, then select "Set as Unplanned" option.

Planned dates can be bulk updated from the Execution Screen, the Test Executions tab, and the Bulk Execute section on the Test Execution tab.

Bulk Execute

This feature enables bulk assignment of Execution Status, Execution Type, Assignee and Planned Date for test suites with multiple test cases, platforms, releases, and cycles. Once triggered, the assignments are processed in the background.

Steps

1. Go to the Test Suite module > Test Execution Tab

2. Select the test cases you want to execute and click on the Bulk Execute button.

3. The next screen displays the combination of test cases with their associated Platforms, Releases, and Cycles.

On this screen, users can perform bulk updates for selected test cases, including:

• Execution Status

• Execution Type

• Assignee

• Planned Date

The image below denotes the selection range of respective checkboxes on the screen.

Bulk assign test cases to testers

• Select test cases/releases & cycles/ platforms to which you want to allocate an assignee.

• Click on the Assignee and select the user that you want to assign to the selected test cases and their platforms at a time.

Bulk Execute test cases

• Select test cases and platforms the execution status to update.

• Click on the Execution Status and select the status to apply to test cases and their platforms at a time.

Bulk set execution type

• Select test cases and platforms the execution type to update.

• Click on the Execution Type and select the type (Manual/Automated) to apply to test cases and their platforms at a time.

Bulk Set Planned Date

You can set a single planned date for multiple test cases in bulk.

Steps:

1. Select the test cases from the grid.

2. Open the Planned Date calendar and choose the desired date for the selected test cases.

3. If no planned date is available, click on Set as Unplanned.

The planned date for all the selected test cases will be updated in bulk.

Archive Test Execution/Test Run

The Test Execution Archive feature allows users to lock executions to prevent any further changes.

Test executions can be archived in the following scenarios:

• When the entire Test Suite is archived.

• When the associated Release or Cycle is archived.

• When the associated Platform is archived.

• When the Test Execution itself is archived.

• When the Project is archived.

Archived test executions will not appear on the Test Executions tab of the test suite.

Archive Test Runs Manually

1. Open the test suite detail page and go to the Test Execution tab. Click on the Archive button for the test run to archive.

The confirmation message pops up. Click Yes to proceed.

View Archived Test Runs

To view archived test runs, select the Show Archived Records check box in the filter on the Test Execution tab. This will display test runs archived due to platforms, releases, cycles, or the test run itself.

For imported data, any changes in the status of archived test case executions will be ignored.

Impact of Archiving a Test Execution/Test Run

• Any new test case linked to the test suite will not be added to the archived execution.

• Existing linked test cases would not be allowed to unlink if they are linked to an archived execution.

• When new version of test case is created ,it cannot be force-synced or manually sycned in the archived execution.

• In case of test case steps update in the existing version, any change in test case step data in that test case version will reflect in test cases under archived execution.

• Bugs, attachments which are part of archived executions cannot be unlinked.

• Test Case and Step Comments, Execution Status, Actual, Expected outcome added during execution cannot be changed for archived executions.

• When "archived" execution is unarchived, any test cases that are linked to the test suite, are auto-linked with the execution after unarchive.

• If an execution's release, cycle or platform are archived, it will not be allowed to unarchive.

• Deleting any executed test case or test case version will remove the executions from the archived executions.

• In a cloned project (with data), the archived test run also get copied.

• For eSignature enabled project, State (In-Review/Approve/Closed) of the test Run will not be allowed to change.

• Closed test execution can be archived but on unarchive test execution nothing will happen.

• Test case data grid related modification will not be reflected in archived execution.

Unarchived Test Runs/Test Executions

• Missing test cases will be linked on unarchive test execution with associated test case version and latest data grid values.

• Existing linked Test case version will not get modified on unarchive test execution.

• Manually archived test execution will not get unarchived if any associated archived Platform/Release/Cycle is unarchived.

• If Test Case-Test suite Data Grid Mapping is modified after archive test execution, then older mapping (steps) will be removed on unarchive test execution.

• In case of parameterized test case, edited value of test case will not affect test cases under the archived test run. Once the test run is unarchived, the values will be updated in the respective test cases.

Bulk Operations on Test Suites

Read about Bulk Operations on Test Suites

Import Test Suites

Read about Import Test Suites

Export Test Suites

Read about Export Test Suites