Updated the docs under the "Atto" section#846
Conversation
WalkthroughDocumentation updates across AI agents and Atto test-generation guides: dialog and button relabeling (e.g., "Jira Requirements" → "Add Jira Tickets", "Generate" → "Generate with AI"), image path replacements, step renumbering and reordering, and modifications to form fields and file/video upload flows. Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant UI as UI Dialog
participant Engine as Generation System
rect rgb(240,245,255)
Note over User,UI: Old condensed flow
User->>UI: Select source (Jira / Files / Design)
User->>UI: Add Input / Add Files
User->>UI: Generate
UI->>Engine: triggerGenerate()
Engine->>User: showGeneratedTests()
end
rect rgb(245,255,240)
Note over User,UI: New review-centric flow
User->>UI: Select source (Add Jira Tickets / Files Upload / Figma)
User->>UI: Add Files / Save selection
User->>UI: Generate with AI
UI->>Engine: triggerGenerateWithAI()
Engine->>User: presentCategories()
User->>UI: openManualStepsTab()
User->>UI: editOrRefineSteps()
User->>UI: generateAutomatedSteps()
User->>UI: acceptAndSave()
end
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes
Possibly related PRs
Suggested reviewers
Poem
Pre-merge checks and finishing touches❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 4
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
src/pages/docs/atto/generative-ai/generate-tests/desktop.md (1)
3-3: Update page title to reflect actual content.The
page_titlein the frontmatter says "Prerequsites for GenAI & Agentic AI" but the content is a how-to guide for generating test cases for Desktop applications. This creates a disconnect for readers.Apply this diff:
-page_title: "Prerequsites for GenAI & Agentic AI" +page_title: "Generate Test Cases for Desktop"
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (8)
src/pages/docs/ai-agents/bug-reporter.md(1 hunks)src/pages/docs/ai-agents/generator.md(2 hunks)src/pages/docs/atto/generative-ai/generate-tests/automate-test-cases.md(1 hunks)src/pages/docs/atto/generative-ai/generate-tests/desktop.md(1 hunks)src/pages/docs/atto/generative-ai/generate-tests/mobile.md(1 hunks)src/pages/docs/atto/generative-ai/generate-tests/requirements.md(4 hunks)src/pages/docs/atto/generative-ai/generate-tests/salesforce.md(2 hunks)src/pages/docs/atto/generative-ai/generate-tests/web-mobile-web.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
src/pages/docs/ai-agents/generator.md
[style] ~47-~47: You have already used this phrasing in nearby sentences. Consider replacing it to add variety to your writing.
Context: ...*, choose all the stories for which you want to generate test cases. ![Jira Inp...
(REP_WANT_TO_VB)
[style] ~58-~58: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...d files. - Click Add Files. - Click Save. 
src/pages/docs/atto/generative-ai/generate-tests/salesforce.md
[style] ~49-~49: You have already used this phrasing in nearby sentences. Consider replacing it to add variety to your writing.
Context: ... Select the stories/epics for which you want to generate test cases and click Save....
(REP_WANT_TO_VB)
[style] ~53-~53: You have already used this phrasing in nearby sentences. Consider replacing it to add variety to your writing.
Context: ...tailed prompt that describes test cases want to generate. 5. Click *Generate with AI...
(REP_WANT_TO_VB)
src/pages/docs/atto/generative-ai/generate-tests/web-mobile-web.md
[style] ~47-~47: You have already used this phrasing in nearby sentences. Consider replacing it to add variety to your writing.
Context: ...*, choose all the stories for which you want to generate test cases. ![Jira Inp...
(REP_WANT_TO_VB)
[style] ~58-~58: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...d files. - Click Add Files. - Click Save. 
src/pages/docs/atto/generative-ai/generate-tests/requirements.md
[style] ~61-~61: You have already used this phrasing in nearby sentences. Consider replacing it to add variety to your writing.
Context: ...scriptive prompt for the test cases you want to generate. 6. Click *Generate with AI...
(REP_WANT_TO_VB)
[style] ~118-~118: You have already used this phrasing in nearby sentences. Consider replacing it to add variety to your writing.
Context: ...scriptive prompt for the test cases you want to generate. 6. Click *Generate with AI...
(REP_WANT_TO_VB)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: CI
| 4. In the **Add Jira Tickets** dialog, | ||
| - From the **Jira Project** dropdown, select a project. | ||
| - Under **Issue Type**, select either **Epic** or **Story**: | ||
| - If you select **Epic**, choose the stories under that epic. | ||
| - If you select **Story**, choose the stories you want to generate test cases for. | ||
| - Click **Add Input**. | ||
| - Click **Save**. | ||
|
|
||
|  | ||
|  | ||
|
|
||
| [[info | **NOTE**:]] | ||
| | You can add more input sources for test case generation by selecting necessary option in the **Generate Test Cases** section. | ||
|
|
||
| 5. In the Prompt box, enter a detailed prompt that describes test cases want to generate. | ||
| 1. In the Prompt box, enter a detailed prompt that describes test cases want to generate. | ||
|
|
||
| 6. Click **Generate**. | ||
| 2. Click **Generate with AI**. | ||
|
|
||
| 6. Wait for **Generator Agent** to generate the test cases based on the selected stories and prompt. | ||
| 3. Wait for **Generator Agent** to generate the test cases based on the selected stories and prompt. | ||
|
|
||
| 7. Click a test case to open it. | ||
| 4. After the test cases are generated, expand a category and select a test case. | ||
|
|
||
| 8. In the **Test Case Details** overlay, review the manual test steps. | ||
| 5. In the **Test Case Details** dialog, go to the **Manual Steps** tab and review the generated steps. | ||
|
|
||
| 9. Click **Generate NLPs** to convert the manual steps to NLP-based steps. | ||
| 6. Click **Edit** to manually add a step or block, or to modify existing steps. | ||
|
|
||
| [[info | **NOTE**:]] | ||
| | You can add or remove test steps by clicking **Edit**. | ||
| 7. If you want to refine the steps using **Atto**, enter a prompt and click **Refine manual steps**. | ||
|
|
||
| 9. Click **Accept** to save the test case. | ||
| 8. Click **Generate Automated Steps** to convert the manual steps into NLP-based automated steps. | ||
|
|
||
| 10. Repeat steps 7–9 for all the test cases you want to add. | ||
| 9. Click **Accept** to save the test case. | ||
|
|
||
| 10. Repeat steps 8–13 for all the test cases you want to add. |
There was a problem hiding this comment.
Fix critical step numbering reset that breaks workflow clarity.
The step numbering resets from 4 back to 1, creating confusion in the workflow documentation. Steps should continue sequentially from 1 to 10 (or however many exist in the complete workflow).
Apply this diff to fix the step numbering:
4. In the **Add Jira Tickets** dialog,
- From the **Jira Project** dropdown, select a project.
- Under **Issue Type**, select either **Epic** or **Story**:
- If you select **Epic**, choose the stories under that epic.
- If you select **Story**, choose the stories you want to generate test cases for.
- Click **Save**.
[[info | **NOTE**:]]
| You can add more input sources for test case generation by selecting necessary option in the **Generate Test Cases** section.
-1. In the Prompt box, enter a detailed prompt that describes test cases want to generate.
+5. In the Prompt box, enter a detailed prompt that describes test cases want to generate.
-2. Click **Generate with AI**.
+6. Click **Generate with AI**.
-3. Wait for **Generator Agent** to generate the test cases based on the selected stories and prompt.
+7. Wait for **Generator Agent** to generate the test cases based on the selected stories and prompt.
-4. After the test cases are generated, expand a category and select a test case.
+8. After the test cases are generated, expand a category and select a test case.
-5. In the **Test Case Details** dialog, go to the **Manual Steps** tab and review the generated steps.
+9. In the **Test Case Details** dialog, go to the **Manual Steps** tab and review the generated steps.
-6. Click **Edit** to manually add a step or block, or to modify existing steps.
+10. Click **Edit** to manually add a step or block, or to modify existing steps.
-7. If you want to refine the steps using **Atto**, enter a prompt and click **Refine manual steps**.
+11. If you want to refine the steps using **Atto**, enter a prompt and click **Refine manual steps**.
-8. Click **Generate Automated Steps** to convert the manual steps into NLP-based automated steps.
+12. Click **Generate Automated Steps** to convert the manual steps into NLP-based automated steps.
-9. Click **Accept** to save the test case.
+13. Click **Accept** to save the test case.
-10. Repeat steps 8–13 for all the test cases you want to add.
+14. Repeat steps 8–13 for all the test cases you want to add.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| 4. In the **Add Jira Tickets** dialog, | |
| - From the **Jira Project** dropdown, select a project. | |
| - Under **Issue Type**, select either **Epic** or **Story**: | |
| - If you select **Epic**, choose the stories under that epic. | |
| - If you select **Story**, choose the stories you want to generate test cases for. | |
| - Click **Add Input**. | |
| - Click **Save**. | |
|  | |
|  | |
| [[info | **NOTE**:]] | |
| | You can add more input sources for test case generation by selecting necessary option in the **Generate Test Cases** section. | |
| 5. In the Prompt box, enter a detailed prompt that describes test cases want to generate. | |
| 1. In the Prompt box, enter a detailed prompt that describes test cases want to generate. | |
| 6. Click **Generate**. | |
| 2. Click **Generate with AI**. | |
| 6. Wait for **Generator Agent** to generate the test cases based on the selected stories and prompt. | |
| 3. Wait for **Generator Agent** to generate the test cases based on the selected stories and prompt. | |
| 7. Click a test case to open it. | |
| 4. After the test cases are generated, expand a category and select a test case. | |
| 8. In the **Test Case Details** overlay, review the manual test steps. | |
| 5. In the **Test Case Details** dialog, go to the **Manual Steps** tab and review the generated steps. | |
| 9. Click **Generate NLPs** to convert the manual steps to NLP-based steps. | |
| 6. Click **Edit** to manually add a step or block, or to modify existing steps. | |
| [[info | **NOTE**:]] | |
| | You can add or remove test steps by clicking **Edit**. | |
| 7. If you want to refine the steps using **Atto**, enter a prompt and click **Refine manual steps**. | |
| 9. Click **Accept** to save the test case. | |
| 8. Click **Generate Automated Steps** to convert the manual steps into NLP-based automated steps. | |
| 10. Repeat steps 7–9 for all the test cases you want to add. | |
| 9. Click **Accept** to save the test case. | |
| 10. Repeat steps 8–13 for all the test cases you want to add. | |
| 4. In the **Add Jira Tickets** dialog, | |
| - From the **Jira Project** dropdown, select a project. | |
| - Under **Issue Type**, select either **Epic** or **Story**: | |
| - If you select **Epic**, choose the stories under that epic. | |
| - If you select **Story**, choose the stories you want to generate test cases for. | |
| - Click **Save**. | |
|  | |
| [[info | **NOTE**:]] | |
| | You can add more input sources for test case generation by selecting necessary option in the **Generate Test Cases** section. | |
| 5. In the Prompt box, enter a detailed prompt that describes test cases want to generate. | |
| 6. Click **Generate with AI**. | |
| 7. Wait for **Generator Agent** to generate the test cases based on the selected stories and prompt. | |
| 8. After the test cases are generated, expand a category and select a test case. | |
| 9. In the **Test Case Details** dialog, go to the **Manual Steps** tab and review the generated steps. | |
| 10. Click **Edit** to manually add a step or block, or to modify existing steps. | |
| 11. If you want to refine the steps using **Atto**, enter a prompt and click **Refine manual steps**. | |
| 12. Click **Generate Automated Steps** to convert the manual steps into NLP-based automated steps. | |
| 13. Click **Accept** to save the test case. | |
| 14. Repeat steps 8–13 for all the test cases you want to add. |
🤖 Prompt for AI Agents
In src/pages/docs/atto/generative-ai/generate-tests/desktop.md around lines
40-70 the ordered list resets from step 4 back to 1, breaking sequence; renumber
the subsequent items so the list continues sequentially (i.e., change the
repeated 1–10 block to start at 5 and continue through the correct final number,
or otherwise adjust the numbering to reflect a continuous sequence matching the
total number of steps).
src/pages/docs/atto/generative-ai/generate-tests/requirements.md
Outdated
Show resolved
Hide resolved
| - Select the flows you want to generate test cases for, and click **Save**. | ||
|
|
||
|  | ||
| ) |
There was a problem hiding this comment.
Fix malformed image markdown syntax.
Line 85 has double parentheses in the image URL, which breaks image rendering. Markdown image syntax requires single parentheses: , not ).
Apply this diff to fix the syntax error:
- )
+ 📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| ) | |
|  |
🤖 Prompt for AI Agents
In src/pages/docs/atto/generative-ai/generate-tests/salesforce.md around line
85, the image markdown uses double parentheses around the URL (")"), which is malformed; remove the extra parenthesis so the line
uses single parentheses for the URL (i.e., change ")" to
"") so the image renders correctly.
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (1)
src/pages/docs/atto/generative-ai/generate-tests/desktop.md (1)
52-52: Minor: Address pre-existing grammatical issue.Line 52 contains a grammatical inconsistency: "enter a detailed prompt that describes test cases want to generate" should read "describes the test cases you want to generate" or "describes what test cases you want to generate" for clarity and correctness. This appears to be pre-existing (not marked as changed in this PR), but worth fixing in a follow-up commit or separate issue to maintain documentation quality.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
src/pages/docs/atto/generative-ai/generate-tests/desktop.md(1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: CI
🔇 Additional comments (2)
src/pages/docs/atto/generative-ai/generate-tests/desktop.md (2)
40-70: ✅ Critical step numbering issue has been resolved.The previous review flagged that step numbering reset from 4 back to 1, breaking the workflow sequence. The current version correctly numbers steps 5–14 as a continuation from the initial steps 1–4, maintaining a clear, sequential flow throughout the entire workflow. This is a solid fix that restores clarity to the documentation.
The terminology updates ("Add Jira Tickets" dialog, "Generate with AI" button, and the refined workflow steps) are consistent with the PR objectives and the enriched summary.
47-47: Image asset verified and accessible.The S3 URL returns a 200 OK response, confirming the new image asset is available and properly referenced.
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
src/pages/docs/atto/generative-ai/generate-tests/requirements.md (1)
49-65: Consider rewording repeated phrases for variety.Lines 61 and 118 both use "enter a clear and descriptive prompt for the test cases you want to generate," which is flagged by the style checker. Consider varying the phrasing in one of these instances to improve readability.
For example, you could use: "In the Prompt box, provide specific instructions for the test cases you'd like generated" on line 118.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
src/pages/docs/atto/generative-ai/generate-tests/requirements.md(5 hunks)
🧰 Additional context used
🪛 LanguageTool
src/pages/docs/atto/generative-ai/generate-tests/requirements.md
[style] ~61-~61: You have already used this phrasing in nearby sentences. Consider replacing it to add variety to your writing.
Context: ...scriptive prompt for the test cases you want to generate. 6. Click *Generate with AI...
(REP_WANT_TO_VB)
[style] ~118-~118: You have already used this phrasing in nearby sentences. Consider replacing it to add variety to your writing.
Context: ...scriptive prompt for the test cases you want to generate. 6. Click *Generate with AI...
(REP_WANT_TO_VB)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: CI
🔇 Additional comments (4)
src/pages/docs/atto/generative-ai/generate-tests/requirements.md (4)
22-26: Navigation links correctly reflect section updates.The table of contents updates align with the new section heading on line 127 ("Generate Test Cases from Video Recording") and the corrected QTest capitalization.
73-99: Figma section step numbering is now correct.The previously flagged numbering reset issue (steps resetting from 4 to 1) has been resolved. Steps now continue sequentially (4→5→6→7) as expected.
161-167: Verify the Files Upload workflow against the actual product UI.The documentation does show a confusing pattern. Looking at the complete context, steps 4–7 read:
- Step 4: "Click Add Files"
- Step 5: "Click Browse and select files"
- Step 6: "Once files are loaded, click Add Files"
- Step 7: "Click Save"
This is genuinely unclear: two separate "click Add Files" actions suggest either a documentation error or a non-standard UX pattern. Additionally, the Video section above has a similar redundancy (steps 6–7 both say "Click Save").
To resolve this, you need to:
- Verify the actual button labels and workflow in the Files Upload dialog UI
- Confirm whether step 6 should reference a different button (e.g., "Save" or "Confirm") or if the step sequence should be consolidated
- Check if similar redundancy in the Video section also needs clarification
The codebase does not contain UI implementation or screenshots to validate the button flow programmatically.
135-141: Clarify the purpose of each Save action in Video Recording flow—pattern confirmed but poorly explained.Verification confirms the double "Save" pattern is intentional and consistent across the codebase (appears identically in both
requirements.mdandmobile.md). However, the documentation fails to explain what each save operation does, making it unclear to users.The concern in the original review is valid: steps 6-7 need clarification. The phrase "Click Save again" provides no context about why a second save is required or what it confirms.
Recommended action: Clarify the purpose of each Save button. The proposed diff in the original review is a reasonable starting point, but should be verified against the actual UI behavior (the screenshot
requirements_4.pngwould clarify the dialog structure and button labels).Additionally,
mobile.mdhas step numbering errors (duplicate step 6 and step 8) that should be corrected.
| ## **Generate Test Cases from QTest** | ||
|
|
||
| 1. From the left navigation bar, go to **Atto’s Home**. | ||
|
|
||
| 2. Click **Generate with AI**. | ||
|
|
||
| 3. On the **Generate Test Cases** page, click **qTest Tests**. | ||
| 3. On the **Generate Test Cases** page, click **QTest**. | ||
|
|
||
| 4. In the **Add qTest Tests** modal dialog, | ||
| 4. In the **Qtest** dialog, | ||
| - From the **Project** dropdown, select a project. | ||
| - From the **Module** dropdown, select a module. | ||
| - Select the test cases you want to use as input. | ||
| - Click **Add Input**. | ||
| - Click **Save**. | ||
|
|
||
|  | ||
|  | ||
|
|
||
| 5. In the Prompt box, enter a clear and descriptive prompt for the test cases you want to generate. | ||
|
|
||
| 6. Click **Generate**. | ||
| 6. Click **Generate with AI**. | ||
|
|
||
| 7. Wait for **Generator Agent** to generate multiple test cases. | ||
|
|
There was a problem hiding this comment.
🧩 Analysis chain
Fix dialog name capitalization inconsistency.
The section heading uses "QTest" (line 102), but the dialog on line 110 is labeled "Qtest" (only first letter capitalized). This inconsistency may confuse users about the correct dialog name they should be looking for in the UI.
Ensure the dialog name matches the section heading for clarity:
-4. In the **Qtest** dialog,
+4. In the **QTest** dialog,Verify that the actual UI dialog in Testsigma is named "Qtest" or "QTest" so the documentation matches the product.
I'll verify the naming convention by checking the repository for other references and consulting official documentation.
---
🏁 Script executed:
```shell
#!/bin/bash
# Search for QTest and Qtest references across the repository to establish pattern
echo "=== Searching for QTest references ==="
rg -n "QTest|Qtest" --type md -C 2
echo ""
echo "=== Checking file structure and related docs ==="
fd -t f "requirements\|qtest\|QTest" --type f
Length of output: 2221
🌐 Web query:
Testsigma QTest integration documentation
💡 Result:
Here’s the official Testsigma documentation for qTest integration and a short summary.
-
qTest integration docs (setup, prerequisites, steps to enable and use): Testsigma Documentation — “qTest Integration with Testsigma”. [1]
- Key points: you need your qTest Host URL and a Bearer Token (copy token without the word “Bearer”), enable the qTest widget under Settings → Integrations, enter Host URL and token, then Save & Enable. [1]
-
Testsigma Integrations overview (other integration context and links to related docs): Testsigma Integrations/Overview. [2]
If you want, I can open the qTest doc and copy the exact step-by-step instructions or provide troubleshooting tips.
Sources:
[1] Testsigma — qTest Integration with Testsigma.
[2] Testsigma — Integrations overview.
Confirmed: Fix dialog name capitalization inconsistency at line 110.
The repository search confirms an internal inconsistency in requirements.md:
- Line 102 (heading): "Generate Test Cases from QTest"
- Line 108 (button reference): "click QTest"
- Line 110 (dialog reference): "In the Qtest dialog," ← inconsistent
The dialog name should match the established "QTest" pattern used throughout the same file:
-4. In the **Qtest** dialog,
+4. In the **QTest** dialog,📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| ## **Generate Test Cases from QTest** | |
| 1. From the left navigation bar, go to **Atto’s Home**. | |
| 2. Click **Generate with AI**. | |
| 3. On the **Generate Test Cases** page, click **qTest Tests**. | |
| 3. On the **Generate Test Cases** page, click **QTest**. | |
| 4. In the **Add qTest Tests** modal dialog, | |
| 4. In the **Qtest** dialog, | |
| - From the **Project** dropdown, select a project. | |
| - From the **Module** dropdown, select a module. | |
| - Select the test cases you want to use as input. | |
| - Click **Add Input**. | |
| - Click **Save**. | |
|  | |
|  | |
| 5. In the Prompt box, enter a clear and descriptive prompt for the test cases you want to generate. | |
| 6. Click **Generate**. | |
| 6. Click **Generate with AI**. | |
| 7. Wait for **Generator Agent** to generate multiple test cases. | |
| ## **Generate Test Cases from QTest** | |
| 1. From the left navigation bar, go to **Atto's Home**. | |
| 2. Click **Generate with AI**. | |
| 3. On the **Generate Test Cases** page, click **QTest**. | |
| 4. In the **QTest** dialog, | |
| - From the **Project** dropdown, select a project. | |
| - From the **Module** dropdown, select a module. | |
| - Select the test cases you want to use as input. | |
| - Click **Save**. | |
|  | |
| 5. In the Prompt box, enter a clear and descriptive prompt for the test cases you want to generate. | |
| 6. Click **Generate with AI**. | |
| 7. Wait for **Generator Agent** to generate multiple test cases. |
🧰 Tools
🪛 LanguageTool
[style] ~118-~118: You have already used this phrasing in nearby sentences. Consider replacing it to add variety to your writing.
Context: ...scriptive prompt for the test cases you want to generate. 6. Click *Generate with AI...
(REP_WANT_TO_VB)
🤖 Prompt for AI Agents
In src/pages/docs/atto/generative-ai/generate-tests/requirements.md around lines
102 to 123, the dialog name "Qtest" at line 110 is capitalized inconsistently
with the rest of the document ("QTest"); update the dialog reference to "QTest"
so it matches the established casing used elsewhere in the file and ensure any
other occurrences in this block use the same "QTest" capitalization for
consistency.
There was a problem hiding this comment.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
src/pages/docs/atto/generative-ai/generate-tests/mobile.md(1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: CI
🔇 Additional comments (2)
src/pages/docs/atto/generative-ai/generate-tests/mobile.md (2)
44-72: Step numbering is now correct, and Team selection has been added.The previously flagged inconsistent numbering (duplicate steps 6 and 8) has been fixed. Steps now flow sequentially from 5 through 12. The addition of Team selection in the Figma Designs dialog (line 45) is a clear enhancement to the workflow.
75-87: Verify that the rewritten Next Steps workflow matches current product behavior.The Next Steps section has been significantly restructured to introduce a manual-to-automated steps workflow (review → edit → refine with Atto → generate automated steps → accept). Ensure that the UI labels, tab names, and button names accurately reflect the current product:
- "Manual Steps" tab (line 79)
- "Refine manual steps" prompt/button (line 83)
- "Generate Automated Steps" button (line 85)
Additionally, verify that this workflow aligns with related documentation updates mentioned in the enriched summary (desktop, web-mobile, and automate-test-cases guides).
| 9. Click **Save** again. | ||
|
|
||
| 8. In the Prompt box, enter a detailed prompt that describes test cases want to generate. | ||
| 10. In the Prompt box, enter a detailed prompt that describes test cases want to generate. |
There was a problem hiding this comment.
Fix grammatical error in prompt instruction.
Line 67 is missing a subject: "describes test cases want to generate" should be "describes test cases you want to generate" or "describes the test cases to generate".
-10. In the Prompt box, enter a detailed prompt that describes test cases want to generate.
+10. In the Prompt box, enter a detailed prompt that describes the test cases you want to generate.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| 10. In the Prompt box, enter a detailed prompt that describes test cases want to generate. | |
| 10. In the Prompt box, enter a detailed prompt that describes the test cases you want to generate. |
🤖 Prompt for AI Agents
In src/pages/docs/atto/generative-ai/generate-tests/mobile.md around line 67,
the sentence "In the Prompt box, enter a detailed prompt that describes test
cases want to generate." is missing a subject; change it to a grammatically
correct form such as "In the Prompt box, enter a detailed prompt that describes
the test cases you want to generate." or "In the Prompt box, enter a detailed
prompt that describes the test cases to generate." to fix the grammar.
2 participants
Updated the docs under the "Atto" section as per the ticket https://testsigma.atlassian.net/browse/DOC-452
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.