Use Vansah Intelligence (VI) in a Jira work item to suggest tests from its requirements. Review the headlines, choose the tests you need, and create the selected Test Cases linked to that work item.
Before you begin
Make sure you can access the Jira space, work item, and Vansah Intelligence features available with your subscription.
Ask a Jira administrator to enable Vansah Intelligence if it is not already enabled.
Give the work item a clear summary and description, including the behavior and acceptance criteria you want tested.
Review existing linked Test Cases so you can identify overlap in the suggestions.
Example requirement: “A customer can reset a password using a valid reset link. Expired links are rejected, and a used link cannot reset the password again.” Specific behavior produces more useful test objectives than a title such as “Password reset.”
1. Open Vansah Intelligence
Open the Jira work item you want to test. You can open it from a board, search, or a direct work item link.
Find the Vansah Test Management panel.
Open the Vansah Intelligence tab, shown by the sparkle icon.
2. Choose the generation settings
Setting | What to choose |
Type | Choose the Test Case type for the testing you need. |
Test Script | Choose the format for the created tests. Multi Steps provides separate actions and expected results. If you choose an automation format, complete the required Target selection. |
Testing Scope | Optional focus for the suggestions. The selected scope is also added as a label to the created Test Cases. |
Generate new Test Cases which have not been created previously | Use this to ask VI to avoid existing tests. Review the results for overlap before creating them. |
Maximum Test Cases | Choose an available count or let VI decide. VI may return fewer suggestions when the requirement details do not support the requested number. |
Review any available context controls. VI uses the work item’s summary and description, with selected work item attributes and other context supported by your subscription and settings. Do not assume that every comment or attachment is included.
Select Next to generate suggested headlines.
3. Review and create the selected tests
Read each headline and compare it with the acceptance criteria and existing Test Cases.
Edit any headline that needs a clearer test objective.
Select the suggestions to create and leave unrelated or duplicate suggestions unselected.
Select Next to generate and save the full Test Cases for those headlines.
Wait for the creation progress and completion message.
The second Next step creates Test Cases. The headline stage lets you choose the test objectives first. Full Test Cases are saved after you proceed from that selection.
4. Review the linked Test Cases
Open the created Test Case links and review their descriptions, preconditions, scripts, test data, and expected results.
Correct assumptions and add any missing application-specific details.
Select Done when available and return to the work item’s Test Cases tab.
Confirm that the new Test Cases are linked to the intended work item.
Generating a Test Case does not run it or confirm that the work item passes testing. When ready, follow Execute a Test Case from a Jira Work Item.
If generation does not complete
What happens | What to do |
The VI tab is unavailable | Check workspace activation, subscription access, and your Vansah Intelligence permission in the Jira space. |
Next is unavailable | Choose a Type and any required script Target. On the headline page, select at least one suggestion. Wait for active generation to finish. |
VI cannot find enough requirement detail | Improve the work item’s description and acceptance criteria. Check the selected context attributes, then generate suggestions again. |
Suggestions are too broad or repetitive | Make the requirements more specific, check the Type and Testing Scope, and compare with existing tests before creating them. |
Only some Test Cases were created | Review the saved cases first. Use Continue when offered for the remaining selections. Stopping generation does not remove cases already created. |