Aviator
Available for: SaaS and Web Client only
Aviator is an AI-powered virtual assistant that can help boost your productivity. You can use it to suggest tests for requirements and create manual tests based on the suggestions.
Prerequisites
Before using Aviator, review the following prerequisites.
Prerequisite | Details |
---|---|
License |
The Aviator license is installed and valid. For details, see Editions. |
Permissions |
If you want to use Aviator to create manual tests from the generated suggestions, you must have permissions to create test folders, tests, and test coverage. Without these permissions, you can use Aviator to generate suggested tests only but you cannot use it to create tests from the suggestions. For details about permissions, see Manage groups and permissions. |
Suggest tests with Aviator
Use Aviator to suggest tests for your requirement and create manual tests based on the suggestions.
Preparation
Verify the following before using Aviator:
-
The name and description of the target requirement clearly convey the intent. This can give Aviator some context about the requirement, which helps increase the relevance and accuracy of the suggestions.
-
The target requirement has test coverage enabled. Aviator does not support requirement types that have test coverage disabled.
For details about requirement type customization, see Customize requirement types.
To generate suggested tests for a requirement using Aviator:
-
Open the Requirements tab.
-
From the requirements tree, select the target requirement.
You cannot use Aviator for the requirement root folder.
-
Click Aviator
.
-
In the Aviator pane, from the Aviator Center list, use the following options to decide the requirement context and enhance the quality of the suggested tests.
The options you select are remembered and automatically applied the next time you use Aviator.
Option Details Use Direct Sub-requirements for Context This option specifies whether to also consider the names and descriptions of child requirements when suggesting tests for the requirement.
-
If it is selected, the names and descriptions of both the selected requirement and its first-level children are considered, providing more context to generate accurate and relevant test suggestions.
-
If it is cleared, only the name and description of the selected requirement are considered, ignoring the context of the children.
Avoid Duplication with Linked Tests This options specifies whether to avoid suggesting the same or similar tests that are already linked to the requirement.
-
If it is selected, the names of the existing linked tests are considered. This ensures the suggested tests are unique and do not duplicate these linked tests.
-
If it is cleared, duplications of existing linked tests may be included in the suggestions.
-
-
In the Aviator pane, click Suggest Test Cases.
-
Aviator suggests up to 10 tests.
-
Each suggested test includes: Name, Description, Steps, and Expected Result.
-
-
If the suggestions are not satisfactory, click Try Again to regenerate suggested tests.
The new generated tests are added after the previously suggested tests.
-
To create manual tests based on the suggestion, click Create Tests.
Note:
-
Suggestions generated by AI may be inaccurate and incomplete. Make sure to review the results before you create the suggested tests.
-
Creating tests is not supported for version-controlled projects.
-
-
From the suggested test list, select the tests you want to create and click Add Selected Tests.
If you generate suggested tests more than once, only the latest generated tests are available for selection.
The selected tests are created and added as follows:
-
The test fields that are automatically filled includes: Name, Description, Steps, and Expected Result.
Note: If some test fields are set as required, you're prompted to fill in these fields before Aviator creates the tests.
-
These tests are added in the Tests from aviator folder of the Test Plan tree.
Tests added for the same requirement are grouped under the same sub-folder, named in the format of <requirement ID> <requirement name>.
-
These tests are linked to the requirement and added in the Test Coverage tab of the requirement.
-
See also: