Skip to main content

Add Test Case

This explains the process for adding a new test case to the project repository using the Add Case dialog.

New test cases can be added in several ways:

  1. Manual Creation: Navigate to the desired folder in the Repository and click the 'Add Case' (+) button
  2. AI Generation: Use the AI-powered generation wizard to create test cases from issues or requirements (requires LLM Integration)
  3. CSV Import: Bulk import test cases from CSV files using the Import Cases wizard

Dialog Layout​

The Add Case dialog uses a resizable two-panel layout:

  1. Left Panel (Main Fields): Contains the core test case definition fields based on the selected template.
  2. Right Panel (Metadata): Contains standard fields like Estimate, Automated status, Tags, and Attachments.

Header Controls​

  • Title: "Add Test Case".
  • Template Selector: A dropdown menu to select the Template for this test case. Changing the template dynamically updates the fields available in the left panel.
  • Parent Folder: Displays the name of the folder the case will be added to.

Left Panel Fields​

  • Name (Required): The name or title of the test case. This is usually a text area allowing for longer descriptions.
  • State (Required): A dropdown to set the initial workflow State for the test case (e.g., Draft, Ready for Review).
  • Dynamic Template Fields: All the custom fields defined in the selected Template are displayed here. This could include:
    • Text fields (single or multi-line)
    • Dropdowns
    • Multi-select lists
    • Checkboxes
    • Date pickers
    • Number/Integer fields
    • Link fields
    • Steps: A dedicated field for defining the test steps, including Action and Expected Result for each step.

Right Panel Fields​

  • Estimate: An optional field to estimate the time required to execute the test case (e.g., "30m", "1h 15m").
  • Automated: A toggle switch to indicate if the test case is intended for automated execution.
  • Tags: Allows selecting and assigning existing Tags to the test case.
  • Attachments: An area to upload files (e.g., design mockups, requirement documents) relevant to the test case definition.

Actions​

  • Cancel: Closes the dialog without creating the test case.
  • Create: Validates the input fields and creates the new test case in the selected folder. It also creates the initial version (Version 1) of the test case.

AI-Powered Test Generation​

When LLM integrations are configured, you'll see an additional Generate Test Cases button (with sparkles icon) in the folder view. This opens the AI generation wizard which allows you to:

Generation Sources​

  • From Issue: Pick a Jira / GitHub / Azure DevOps issue from your project's tracker. The AI uses the issue's title, description, and comments — and automatically pulls in the issue's directly-linked items (one hop) so it sees the wider context. For example: pick an Epic and the AI also sees the Stories under it; pick a Story and the AI also sees what blocks it, what it relates to, and any subtasks.
  • From Document: Type or paste your own requirements directly. Useful when no tracker issue exists yet.
  • From URL: Point the AI at a web page (e.g., a public spec, a help article, a SaaS app screen). The AI crawls and reads the page content.

What the AI sees when you pick an issue​

After you select an issue, the wizard shows a Linked issues that will be included section listing each linked issue's key (e.g. PROJ-123) and its relationship to the source (parent, subtask, blocks, relates-to, etc.). This lets you preview the AI's context before generating. Linked-issue traversal stops at one hop — issues linked to your linked issues are not followed.

When the combined context (your issue + its linked issues + all their comments) is too large for the AI model's token budget, the wizard automatically trims linked-issue content first, never the source issue itself. After generation, if any linked issues were dropped to fit the budget, you'll see an alert above the generated cases listing exactly which issues were excluded — so you know what the AI saw and what it didn't.

Generation Process​

  1. Select Source: Choose an issue or provide requirements document details
  2. Select Template: Choose the template and specific fields to populate
  3. Configure Settings: Set quantity, provide additional instructions, enable auto-tagging
  4. Review & Import: Review generated test cases and select which ones to import

Key Features​

  • Smart Field Population: AI automatically fills template fields with contextually relevant content
  • Context Awareness: Considers existing test cases in the folder to avoid duplication
  • Flexible Quantity: Generate from single test cases to comprehensive test suites
  • Auto-tagging: Automatically generates and assigns relevant tags
  • Test Steps Generation: Creates detailed action/expected result pairs

For per-tracker details (which Jira link types are followed, GitHub sub-issues, ADO System.LinkTypes.*, etc.) and the AI configuration side, see the Test Case Generation admin documentation.