Back to QMetry All Products Help Page
Design Test Cycles with QI
- Mrunalini Potnis
Introduction
The QI feature Design Test Cycles analyzes your execution objectives to suggest precise recommendations for relevant test cases from the project library. You can select test cases from the suggested ones to link with the test cycle. It ensures thorough coverage and efficient planning.
Administrators can enable or disable the QI feature for the QTM4J instance based on the organization's privacy policy.
Key Benefits
Streamlined Process: Simplifies test cycle creation by intelligently suggesting test cases based on your objectives.
Comprehensive Coverage: Ensures no critical test cases are missed, providing complete coverage aligned with your testing goals.
Enhanced Usability: Provides flexibility with features like drag-and-drop ordering, manual selection/deselection, and customizable views.
Cross-Project Capabilities: Enables seamless search and selection across multiple projects.
Efficiency: Reduces manual effort in test case identification and test cycle design.
Configuration
The administrator can configure the Design Test Cycle with QI settings under Global Settings.
Required Permission: Jira Admin can configure QMetry Intelligence Configuration.
Steps
1. Go to Apps > QTM4J > Global Settings.
2. Select the AI Configuration section.
→ Design Test Cycle with QI
Enable users to design test cycles using QI: The option is disabled by default. When enabled, it prompts the admin to select one of the following options using a radio button.
Select from either of the options:
Option 1: Feature Enabled by Project Administrators
Option 2: Feature Enabled Automatically
The options are described below.
Option 1: Feature Enabled by Project Administrators
Let project administrators decide and enable this feature for their respective projects. (Default Setting):
This setting allows project administrators to enable/disable the feature for their respective projects.
Project Level Settings for Option 1
Once the process is completed, the Design Test Cycles settings will be displayed under QMetry Intelligence for each QMetry-enabled project.
Project-Level Settings: For enabled projects, the Design Test Cycles section is displayed under QMetry Intelligence with Information and Configuration tabs. The following permission is required to access the settings.
→ Required Permission: Users should have the Enable/Disable Design Test Cycle With QI permissions under Project Settings > Apps > QMetry Project Settings > Project Permissions. The permission is auto-enabled for users or groups with the “Configuration Modify" rights.
Steps
1. Go to Apps > QMetry > QMetry Intelligence > Design Test Cycles.
2. Open the Configuration tab.
Detailed information about this setting is available in the Information tab.
The instruction window pops up.
3. Read the instructions and click Proceed.
The process is initiated.
Note: The feature cannot be disabled while the AI service activation is in progress.
The status will be updated once the AI service activation is complete.
Option 2: Feature Enabled Automatically
Automatically enable this feature for ALL existing QMetry-enabled projects. For newly created or enabled projects, project administrators will need to enable the feature explicitly.
Enabling the 'Design Test Cycles with QI' feature for all projects may take some time, depending on the number of projects and the assets within them. Once the service is successfully enabled, a 'Completed' status will appear next to the 'Design Test Cycles with QI' option on the screen.
The Design Test Cycles with QI configuration is enabled for all the users of all the projects on the instance to use the design test cycle using the QI feature.
Configuration Audit Logs
The audit logs related to the Design Test Cycle with QI Configuration are captured under the Configuration Logs.
Steps
1. Go to Apps > QMetry > Configuration > Audit Log.
2. Open the Configuration Logs tab.
You can view the audit logs related to the Design Test Cycle with QI Configuration for the project.
Using the Feature
Once the Design Test Cycle with QI feature is enabled for the project, you can access the Design Test Cycles feature. Using the Design Test Cycle feature, you can:
A. Create a New Test Cycle using QI
B. Link Test Cases to Existing Test Cycles using QI
A. Create a New Test Cycle using QI
You can create a new test cycle using the Design Test Cycles with the QI feature. Describe the execution objectives, and QI will suggest the most relevant test cases from the project library, ensuring comprehensive coverage and prioritizing execution effectively.
Steps
1. Open the Test Cycle module.
2. Click on the Design Test Cycles button at the top.
The Design Test Cycles screen opens with a text box to specify your execution objective. QI will then identify the relevant test cases from the project library.
The image below is annotated for the following components:
A. Text box to write the execution objective.
B. Drop-down with the list of projects. You can select test cases from cross-projects. One project can be selected at a time.
If Option 1 is selected during the configuration, the drop-down will show only those projects in which the Design Test Cycles using QI for this project feature is enabled.
C. Sample prompts to use as execution objectives.
3. Write the execution objective.
For semantic execution objectives, QI will search for details within the Test Case Summary, Description, and Step Summary.
Note: The input length for the execution objective should be between 20 and 500 characters.
4. Select the project from which you want to retrieve the test cases based on the execution objective.
5. Click the right arrow button.
The QI process to identify the test cases is initiated.
The next screen opens with the list of recommended test cases. There are three stages involved in the process:
Stage 1. Recommend Test Cases
Stage 2. Review Collection
Stage 3. Enter Test Cycle Fields
Stage 1. Recommend Test Cases
The test cases are retrieved based on the execution objectives.
Note: A maximum of 1000 test cases can be retrieved on the screen at a time.
1. Select the test cases you want to link with the new test cycle that is being created.
2. Click the Add to Collection button to link the selected test cases with the test cycle.
Note: A maximum of 1000 test cases can be added to the collection at a time.
→ Applying Filter to the Execution Objective
You can filter the fields to achieve a more specific list of test cases. Refer to the table below for fields supported for applying the filter.
Notes:
When specifying filters in the execution objective, use the exact field names and provide valid values enclosed in single or double quotes.
Example: Verify test cases where the Labels is "Regression" and the Components contain "Reports" or "Gadgets".
Write the execution objectives using two separate sentences when both the semantic and filter-based inputs are used.
Example: Give the list of test cases containing “seamless integration with devices”. Test Case Priority as “Blocker” or “High”.
When filtering test cases on the assignee of test case or execution, tag the user using “@”. The username will prompt as you type the name “@username”.
Example: Give the list of test cases for Execution Assignee = @Liza Mathew.
Once you select the test cases, click the Add to Collection button.
3. You can modify the Execution Objective text to add more test cases to the collection.
The test cases are added to the collection. The Add to Collection button displays the count of test cases added to the collection.
Note: A total of up to 1000 test cases can be added to the collection.
4. Click Next to review the test case collection.
Best Practices
When searching for test cases based on their purpose or objective, QI identifies matching keywords or phrases within the Test Case Summary, Description, and Step Description fields. Example:
Verify all test cases related to login functionality.When specifying filters in the execution objective, use the exact field names and provide valid values enclosed in single or double quotes. Example:
Verify test cases where the Label is "Regression" and the Components contain "Reports" or "Gadgets".When providing execution objectives, start with phrases like “Show all test cases”, “Verify test cases”, or “Search test cases”. This helps the QI understand that you are searching for test cases and applying filters.
In execution objectives, “and” is interpreted as an intersection (common values), and “or” is interpreted as a union by the service. To retrieve all relevant test cases, use prompts like “Contains All” or “Contains Any”.
Present your expectations in separate sentences when execution objectives include both semantic and filter-based input. Example:
Show all test cases related to login functionality. Filter test cases where Labels are "Regression" and Components are ("SSO", "SAML", "MFA")”. If the response is unsatisfactory, reorder the statements in your objective, prioritizing the filter part first.For user-related inputs, such as assignee and reporter, use the @username format to fetch the relevant test cases.
For folder-related inputs, enter the complete folder path in the format:
/[Folder Name]/[Subfolder Name]/...(for example,/f1/f2/f3).Provide the sprint name, including the board name, in the format:
[Board Name] / [Sprint Name](for example,L4 board / L4 Sprint 1).
Stage 2. Review Collection
You can manually reorder, auto-sort, or remove test cases from the collection. You can re-order the test cases and unlink the linked test cases.
Remove Test Cases from the Collection
→ Unlink a Single Test Case
Hover over the test case you want to unlink and click on the Unlink icon visible hover.
→ Unlink Test Cases in Bulk
Select the test cases you want to unlink and click the Unlink Test Case option.
Review the test case collection before linking them with the test cycle.
Click Next once you review the collection.
Stage 3. Enter Test Cycle Details
Enter Summary, Description, and values in other system fields and custom fields for the test cycle that is being created.
Click Create to proceed.
The success message pops up with the test cycle key.
In the Test Cycle module, you can see the newly created test cycle.
B. Link Test Cases to Existing Test Cycles using QI
You can utilize the QI feature to get recommendations for test cases that can be linked to the existing test cycle. Describe the execution objectives, and QI will suggest the most relevant test cases from the project library, ensuring comprehensive coverage and prioritizing execution effectively.
Steps
1. On the test cycle detail page, open the Test Cases tab.
2. Click on the Recommend Test Cases button at the top.
The Identify Test Cases screen opens.
3. Enter the execution objective to list out relevant test cases to link with the test cycle and click the right arrow button.
The next screen shows the list of recommended test cases.
Note: The test cases already linked to the test cycle will be excluded from the list.
If you want to modify the execution objective or use filters, you can do so by editing the objective in the text box.
4. Select the test cases that you want to link with the test cycle.
5. Click on the Add to Collection button.
6. Then click Next to proceed.
7. Review the collection of test cases.
At this stage, you can remove test cases from the collection by unlinking them individually or in bulk as shown below.
8. Click Update if you want to link the test case collection to the existing test cycle.
The test cases are linked to the test cycle.
View Usage Statistics
The section provides statistics like how many test cycles are created or updated, how many users use the feature, and how many projects are using the feature. You can track the usage metrics at project and instance levels.
→ Usage Statistics for Administrators (Instance Level)
The administrator can access the Design Test Cycle with QI configuration and view the Usage Statistics of the feature under Global Settings.
Steps
1. Go to Apps > QTM4J > Global Settings.
2. Select the AI Configuration section.
3. Expand the Show Usage Statistics section. The following statistics are displayed:
Number of test cycles created across the projects on the instance.
Number of test cycles updated across the projects on the instance.
Number of users using the feature on the instance.
Number of projects using the feature on the instance.
Number of projects in which the Design Test Cycles with QI feature is enabled.
→ Usage Statistics in Test Cycle Module (Project Level)
Users can view the Usage Statistics of the Design Test Cycle with QI feature in the Test Cycle module.
Test Cycle List View
Open the Test Cycle module and hover over the Design Test Cycles button.
You will see the statistics for the Test Cycle Created/Updated using QI.
Test Cycle > Test Cases tab
Go to the test cycle detail page, open the Test Cases tab, and hover over the Recommend Test Cases button.
You will see the statistics for the Test Cycle Updated using QI.
Test Cycle List View
In QMetry-enabled projects where the Design Test Cycles feature is activated, a column QI Generated is displayed on the Test Cycle list view.
This column is filterable, allowing users to view the relevant data easily.
For each test cycle, the QI Generated column indicates "Yes" or "No," reflecting whether the test cycle was created or updated through QI.
Provide Your Quick Feedback
You can provide quick feedback on the recommended test cases through QMetry Intelligence. If you find inaccuracies, omissions, or areas for improvement, you can give feedback directly in the QMetry Intelligence interface. The feedback and information will be used to improve the feature.
Thumbs Up
You can select either of the following options to indicate what you like:
Correct Sequence
Complete Coverage
Relevant Suggestions
More...
→ More: You can enter your feedback by entering text up to 2000 characters in the box.
Thumbs Down
You can select either of the following options to indicate which improvements you expect:
Sequence Issue
Incomplete Coverage
Irrelevant Suggestions
More: You can enter your feedback by entering text up to 2000 characters in the box.
Disclaimer: While your data is stored in your region, all AI processing is done exclusively in the US region.
Back to QMetry All Products Help Page