You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/pages/docs/test-management/atto/best-practices/generating-test-cases.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -177,19 +177,19 @@ After generating test cases with Atto, you can curate and enhance the test cases
177
177
- Verification steps
178
178
- Flow & UI context
179
179
180
-
180
+
181
181
182
182
Refining ensures each test case is actionable, traceable, and ready for manual execution or automation.
183
183
184
184
### **2. Work Within a Single Feature Context**
185
185
To get accurate, focused, and manageable test case generation from Atto, always create a session in Atto’s Home around a single feature or a group of closely related features.
186
186
- Group relevant assets such as user stories, Figma designs, API endpoints, and files related to that one feature.
187
-
187
+
188
188
- Avoid mixing unrelated contexts in the same session to prevent confusing or inaccurate outputs.
189
189
- Use the prompt area effectively by clearly stating:
190
190
- The feature under test
191
191
- The context you’re providing (stories, designs, workflows, etc.)
192
192
- The expected outcomes from the AI-generated test cases
-**Inactive:** Displays sprints that are imported from Azure DevOps but are not yet active in Testsigma. You can activate these sprints for test case generation.
77
77
-**Completed:** Displays sprints that were previously activated and done with the test case generation.
@@ -90,7 +90,7 @@ The Sprint Planner Agent helps you manage and organize your Azure DevOps sprints
90
90
**c.** Search by title box to find a specific story.
91
91
92
92
**d.** Story list with **ID**, **Title**, and **Current Status** (e.g., **To Do**).
93
-
93
+
94
94
95
95
6. Click **Activate** next to the sprint for which you want to generate test cases
96
96
@@ -104,7 +104,7 @@ The Sprint Planner Agent helps you manage and organize your Azure DevOps sprints
104
104
| - At this stage, the **Generator Agent** takes over and starts generating test cases automatically based on the selected user stories. You can review, edit, and organize these cases before saving them.
105
105
106
106
2. Click **Start Generating Tests** to start generating tests for the attached stories.
When a work item is updated after test generation, Atto marks it as **Modified**. A **Modified** label appears next to the work item in the sprint view.
When the sprint is closed in Azure DevOps, a **Sprint Closed in Azure devops** pop-up appears. Click **Mark as Done** to close the sprint in Test Management by Testsigma.
If a sprint is deleted in Azure DevOps, a **Sprint Deleted in Azure devops** pop-up appears in Atto. The sprint becomes read-only, you can view the content, but cannot make changes.
When a story is deleted from a sprint, it is only available in **View Mode**. Any test cases already generated for the story remain visible and accessible.
-**Inactive**: Displays cycles that are imported from Linear but are not yet active in Testsigma. You can activate these cycles for test case generation.
87
87
-**Completed**: Displays cycles that were previously activated and done with the test case generation.
88
88
-**Deleted**: Displays cycles that are deleted in the Linear project.
@@ -92,7 +92,7 @@ The **Sprint Planner Agent** helps you manage and organize your Linear cycles in
92
92
4. Review the list of cycles. Each cycle card shows the **Cycle ID**, **Name**, **Number of stories** waiting for test generation, and the **Last Updated Date**.
93
93
94
94
5. Select a cycle to view the list of stories associated with that cycle. The cycle view shows the following details:
Copy file name to clipboardExpand all lines: src/pages/docs/test-management/atto/sprint-planner/manage-sprints.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -121,7 +121,7 @@ The **Sprint Planner Agent** helps you manage and organize your Jira sprints in
121
121
| At this stage, the **Generator Agent** takes over and starts generating test cases automatically based on the selected user stories. You can review, edit, and organize these cases before saving them.
122
122
123
123
2. Click **Start Generating Tests** to start generating tests for the attached stories.
When a test case is generated, you can review and refine it using AI. After finalizing the test case, click **Accept** to save it.
174
-
174
+
175
175
176
176
**4. Sprint Completion** <br>
177
177
When the sprint is closed in Jira, a "**Sprint Closed in Jira**" popup appears. Click **Mark as Done** to close the sprint in Test Management by Testsigma.
If a sprint is deleted in Jira, a "**Sprint Deleted in Jira**" popup appears in Atto. The sprint becomes read-only, you can view the content but cannot make changes.
182
-
182
+
183
183
184
184
**6. Story Movement Between Sprints** <br>
185
185
If a story is moved from one sprint to another, Atto displays a "**Moved**" label and shows a popup indicating the change.
When a story is deleted from a sprint, it is only available in **View Mode**. Any test cases already generated for the story remain visible and accessible.
0 commit comments