Considerations When Generating and Saving the Test Case
Consider the following while generating and saving the test case using the AI Test Case Assistant:
• The AI Test Case Assistant remembers your progress if you leave the process midway. When you return to the same requirement, you can resume from the step where you left off.
For example, you start the Test Case Assistant for a requirement and reach the Technique step. If you then switch to another requirement the assistant saves your progress. When you return to the original requirement, the process resumes from the Technique step.
However, if something changed while you were away, for example, if the requirement was updated or conditions were modified or deleted, the saved information may be outdated. In this case, the Test Case Assistant detects the change and shows a warning. You then need to reanalyze the requirement and restart the process.
• All editable input text fields have predefined character limits, which are displayed within the respective fields. These character limits apply only in the AI Test Case Assistant and not in any other view of Codebeamer.
• Hovering over the Condition and Technique steps in the stepper shows the applied conditions and techniques in a tooltip, allowing you to review them later during test case generation.
• When you save a test case created by the AI Test Case Assistant, any mandatory fields that were previously set are not automatically enforced. We recommend that you review the saved test case and fill in any required fields to make sure the test meets your project or tracker requirements.
• When you open or reanalyze a requirement, a warning appears if any previously saved conditions are out of date and must be reviewed.
• When generating a test case, if the requirement changes, after the newly created test case is saved, the generated test case is marked as a suspect.
• You cannot save test cases across different Working-Sets or Streams. The target test case tracker must be in the same Working-Set or Stream as the original tracker.
Special Use Cases
|
Use Case
|
Outcome
|
||
|---|---|---|---|
|
After generating the test steps and before saving the test case, the user updates the target tracker’s configuration to remove the custom AI fields.
|
Saving the test case fails.
|
||
|
During test case generation, the user changes data on a particular page and then navigates to a previous page and updates the data on that page.
|
Your manually made changes in the original page are lost as AI regenerates the data on this page.
|
