# 24.50.0 - public and private clouds ## Guidelines Version 24.50 Date: 05.06.2024 ## Creating multiple test cases with AI Copilot **Useful when:** * You need to create a test case that covers specific path: happy or negative * When you want to save time and delegate AI to create first version of the test cases before adding more details * Reduce human error with AI-generated test cases that adhere to specified guidelines and requirements. **Guide:** The new and improved way to create test cases with the help of AI! Follow these simple steps to leverage the AI Copilot for creating efficient and accurate test cases When on the navigation page, click on the "+ Add new" button located at the top left of your screen.

Once you select the ‘Test case’ option, the modal will appear.

You need to activate AI Copilot by clicking on the toggler.

Once it’s enabled, the modal will change the interface and you will see additional options.

In the ‘Context’ field, provide details about the product, feature, or functionality under test. Include any special glossary terms the AI should consider. Even though this block is optional, additional information helps the AI Copilot generate more relevant and precise test cases.

Then, select a requirement which AI should cover with test cases.

As soon as the requirement is selected and context provided, choose whether you want to create a single test case or multiple test cases by selecting either ‘One’ or ‘Multiple’ under ‘Number of test cases’.

Use the dropdown menu under ‘Max number of test steps’ to set a limit on the number of steps the test case should include. Options range from 3 to 12 steps or you can select ‘Any’ for no limit.

In cases when you need to create only one test case, you can choose the path (case) which test case should cover: positive or negative.

When you create multiple test cases, AI Copilot will generate both: positive and negative path test cases. As soon as all options are preselected, click the button ‘Create’. Ai Copilot will analyze a linked requirement and start creating test case or test cases. **Single test case** When a test case is generated, you can either regenerate it or add it if you are satisfied with the result.

The generated test case will be linked as a dependent item that covers your requirement. **Multiple test cases** When AI starts creating test cases, you will see the number it can create in the corresponding block. You can switch between the test cases to review them before adding as coverage to your requirement

By default, all test cases will be linked to a requirement as soon as you click the ‘Add button’, but if you see that some of the test cases are not relevant, you can exclude them by unchecking the ‘keep’ box.

If you are not satisfied by generated test cases at all, you can use ‘Regenerate’ button. {% hint style="info" %} Please note, that for now it will start the regeneration of the whole suite at once. {% endhint %} *** ## New option to create items **Useful when:** * You need to quickly create drafts with minimal required information. * You want to add more details later, ensuring you can focus on the essentials first. * Oftentimes create multiple drafts and want to do it without interruption. **Guide** Users with AI enabled can now create new items in an even easier way. Here’s how it works. When you need to quickly create a draft version of an item, simply provide a title and a short description.

Save the ticket with just these basic details. You can add all other details later at your convenience. If you need to create multiple drafts, select the option ‘Create and add another’.

This allows you to streamline the creation process without leaving the modal. To start working on the ticket in a more advanced manner as you did before, click on the expand button. This will open up a more detailed view for you to complete your item.

*** ## Improved sprint creation and burndown chart template When creating a sprint, you can now conveniently provide a title and description. Once you set the start and end dates, the system automatically calculates the sprint's length, allowing you to see immediately if the selected dates are correct for 1-week, 2-week, etc., sprints.

You can set velocity which will be taken into an account once you build the burndown chart.

To properly display 'burned' points, ensure the default 'Points' field is added if it hasn't been enabled for the item yet on the template page. Next, open project settings and under the 'Agile' tab, define the 'Definition of Done' for the item types used.

Once all settings are configured, navigate to the dashboard and click 'New Chart.' Then select 'Template' and choose the 'Burndown' chart. Give it a title, select a project, and choose a sprint for the burndown chart. Save it.

Now you're all set.

*** ## Translate content to more than 70 langues with AI Copilot The AI Copilot text helper now supports translation in over 70 languages, including both popular and less common ones, giving you full flexibility. To translate content, simply highlight the text you want to translate, click on the AI Copilot icon, and select ‘Translate.’

Then, choose a language from the list or search for the desired language.

You can either replace the original text with the translation or add the translation below it. AI Copilot will remember the language you used most recently, so it will appear at the top of the list next time you need it. {% hint style="success" %} **Want to know what's coming next? Keep an eye out for updates, as we're currently working on exciting changes that will take your testing experience to the next level.** {% endhint %}
--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.aqua-cloud.io/documentation/product-updates-for-public-and-private-clouds-customers/product-updates/2024/24.50.0-public-and-private-clouds.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.