- Projects
- Test Cases
- Data Sets
- Imports and Exports
- Step Groups
- Test Runs
- Test Plans
- Integrations
- Testsigma Two-way Integration
- Settings
- Manage Users
- Reports & Analytics
- CI/CD Integrations
Generate Test Cases
When a sprint starts, Atto detects it and generates test cases automatically.
In Sprints, test case generation is triggered by your sprint workflow, not manually. When a sprint starts in your connected project management tool, Atto detects the new sprint and notifies you. You confirm, and Atto pulls context from the sprint stories and linked artifacts to generate test cases.
This article covers how sprint detection works, how to confirm or defer generation, and how to generate test cases for sprints that were skipped.
Prerequisites
Before you begin, ensure that:
- You have an active project in Test Management by Testsigma.
- Your project management tool (Jira, Azure DevOps, Linear, or ClickUp) is connected to your project.
- The context sources linked in your sprint stories (Confluence pages, Figma designs, PRDs) are either publicly accessible or connected as integrations.
Confirm Generation When a Sprint Starts
When a sprint starts in your connected project management tool, Atto automatically detects it and shows a notification.
- From the left navigation bar, go to QI Home.
- Select the Sprints tab.
- When Atto detects a new sprint, a notification appears: Atto has started to Generate your tests. A new sprint is live. Shall I start creating test cases for this? The notification shows the sprint name and start date.
- Click Start Generating Tests to begin. Atto moves the sprint to In Progress and begins generating test cases.
Click Not Now to skip generation for now. The sprint stays in To Do status and appears in the Sprints sidebar with a Generate Test Cases link. You can trigger generation manually whenever you are ready.
What Atto Uses as Context
Atto automatically pulls context from the sprint stories and their linked artifacts. You do not need to attach anything manually.
Context Atto uses includes:
- Story titles, descriptions, and acceptance criteria from your project management tool
- Confluence pages linked in sprint stories
- Figma designs linked in sprint stories
- PRDs and specification documents linked in sprint stories
- Relevant pull requests linked to sprint stories
Atto can only read artifacts that are either publicly accessible or connected as integrations. If a Confluence page or Figma file is private and the integration is not set up, Atto will not be able to use it as context.
Generate Test Cases for an Unprocessed Sprint
If you clicked Not Now on a sprint or if Atto missed a sprint notification, you can trigger generation manually.
- From the left navigation bar, go to QI Home and select the Sprints tab.
- In the left sidebar, find the sprint with To Do status.
- Click Generate Test Cases next to the sprint name. Atto begins generating test cases using the same process as automatic detection.
What Happens During Generation
Atto uses the same generation process as Ad-Hoc. You can watch the progress in the left panel as each step completes. Generation typically takes one to two minutes.
See Generate Test Cases in the Ad-Hoc section for details on what Atto does during generation and how to read the generation summary.
After Generation
When generation completes, the sprint moves to In Progress status in the sidebar. The main area shows the sprint detail view with three tabs: Tests, Coverage, and Test Plan.
From here you can:
- Review and accept test cases from the Tests tab. See Review and Accept Test Cases.
- Add more context or generate additional test cases by clicking Open Playground. See Use Playground.
- Track coverage and gaps from the Coverage tab. See Coverage and Gaps.
Want to contribute or report missing content?