Generating the Test Case with AI Test Case Assistant 1.1
Follow the steps below to generate a test case:
Step 1: Analyze the Item
1. In the Document View or Document Edit View, select an item and click Analyze on the AI Test Case Assistant start page. The AI Test Case Assistant analyzes the description of the item and enables the Condition step. This step displays the Test Breakdown page.
The Test Breakdown page displays the AI generated test conditions. You can manually add additional test conditions in this step using the 
icon. You can edit or delete the test conditions using the 
and 
icons.
icon. You can edit or delete the test conditions using the and icons. | • The AI Test Case Assistant generates test case conditions using an LLM. If the administrator has provided additional context or guidelines using the Set AI Context option, that context is appended to the input passed to the LLM. The test case conditions are then generated based on those guidelines along with the LLM input. • For the selected requirement, the AI-generated test conditions, including the manually added and edited test conditions are saved for future use. The AI-generated conditions are automatically regenerated when you rerun the analysis, however, the manually added and edited test conditions are preserved. |
2. Click 
to display the existing test cases covered under the available conditions. Click it again to hide the list of test cases for the conditions.
to display the existing test cases covered under the available conditions. Click it again to hide the list of test cases for the conditions.| | After manually adding a test condition, click the again to refresh the coverage results. |
3. To filter the test conditions based on the coverage, select an option in the drop-down next to the icon:
icon:◦ Select Show all to display all available test conditions for the test case, with and without coverage. This is the default selection.
◦ Select Show without coverage to show only the test conditions that do not have any associated test cases.
4. Select a test condition against which you want to generate a new test case and click 
. The Technique step is enabled.
. The Technique step is enabled.Step 2: Select the Test Technique
1. The Technique step displays the Test Techniques page. The list of displayed techniques is based on the International Software Testing Qualifications Board (ISTQB) standard. The following system-defined test techniques are listed by default:
◦ Boundary Value Analysis— A testing technique used to identify errors at the boundaries of input domains rather than within the range. It is based on the observation that defects often occur at the extreme ends of input values.
◦ Compatibility Testing — A type of non-functional testing to validate that an application or system works as expected across different devices, operating systems, browsers or network environments.
◦ Equivalence Partitioning — A type of testing technique used to reduce the number of test cases while maintaining effective coverage. It works by dividing input data into partitions (or classes) where all values in a partition are expected to behave similarly.
◦ Random Testing — Random testing involves selecting test data randomly from the input domain of the test item. Random testing is useful when domain knowledge is limited, large volumes of test data are needed quickly, or bias reduction is important, such as in fuzz testing and chaos engineering.
◦ Scenario-Based Testing — Scenario-based testing evaluates system behavior in realistic workflows using models like activity diagrams or use cases. Scenarios include the main path, alternatives, and exceptions. This approach is common in system or acceptance testing but can also apply to other levels and non-functional tests.
◦ State Transition Testing — A type of testing technique used to validate how a system behaves when transitioning between different states based on events or inputs. It is particularly useful for applications where the output depends on both the current state and previous state.
◦ Generic Testing — This test technique creates a generic test case when none of the predefined test techniques cover the intended scenario.
Based on the requirement analysis and selected conditions, the system suggests a relevant test technique from the list.
2. Select the AI-suggested test technique, or any other test technique that you think is appropriate and then click . The Details step is enabled.
. The Details step is enabled.Step 3: Review and Edit the Test Case Details
1. The Details step opens the Test Case Details page, where fields such as Name (Required), Description, and Pre-Action are prefilled with AI-generated content. You can manually edit any of these fields if required. Note that these fields support only plain-text.
2. Click , the Outline step is enabled.
, the Outline step is enabled.Step 4: Review and Edit the Test Case Outline
1. The Outline step displays the Test Case Outline page. The Test Case Outline shows the framework of the test case, that is, the test steps. Based on your testing requirements, you can add new steps, or edit or delete, the existing test steps using the , , and icons. You can also reorder the steps in the outline using the drag handles 
.
, , and icons. You can also reorder the steps in the outline using the drag handles .| | The AI-generated test steps, including the manually added and edited test steps are preserved and available for future sessions. |
2. Click , the Steps step is enabled.
, the Steps step is enabled.Step 5: Review and Edit the Test Steps
1. The Steps step displays the Test Steps page. This page list the AI-generated steps that will be included in the new test case.
2. Click Expand All to view the Action, Expected Result, and Post-Action fields for each step. The Action, Expected Result, and Post-Action fields are prefilled with AI-generated content. However, you can edit the content of these fields, if required.
| | The Action, Expected Result, and Post-Action fields support only plain-text. |
Step 6: Save the Newly Created Test Case
1. Once you have reviewed the test steps in Test Steps page, click 
in the AI Test Case Assistant footer to save the test case. The Save Test Case dialog opens.
in the AI Test Case Assistant footer to save the test case. The Save Test Case dialog opens.◦ For Codebeamer version 3.1 and later:
The Save Test Case dialog displays the following fields: Stream, Project, and Tracker.
▪ The Stream and Project drop-down lists show the current stream and project as the default selections.
▪ You can change the default selection in the Project drop-down if needed.
▪ The default selection in the Stream drop-down cannot be changed.
◦ For Codebeamer version 3.0.0.3:
The Save Test Case dialog displays the following fields: Project, Working Set, and Tracker.
▪ The Project and Working Set fields show the current project and working-set as the default selections.
▪ You can change the default selection in the Project drop-down only if you are currently in the default working-set.
▪ The default selection for the Working Set drop-down cannot be changed.
2. Select the required test case tracker in the Tracker drop-down.
| | The Tracker drop-down shows only those trackers that have the custom fields Last Influenced by AI, Influenced by AI, AI Test Condition and AI Test Technique configured. For more information, see Configure Custom Fields for Trackers. |
3. Click Save. The new test case is saved in the selected Stream/Project/Tracker or Project/Working-Set/Tracker based on the Codebeamer version that you are currently on. When save is complete, Codebeamer displays a success message with a link to the new test case. The new test case is marked with Influenced by AI field set to true, along with Last Influenced by AI field updated with the latest date and timestamp.