dev >> main

src/pages/docs/test-management/qi-home/ad-hoc/attach-context-sources.md

@@ -63,12 +63,8 @@ You attach context sources inside the Playground, before writing a prompt and tr
 
 2. The **Adhoc** tab opens by default.
 
-   <!-- screenshot: QI Home Ad-Hoc empty state showing the "Generate with Atto" button -->
-
 3. Click **Generate with Atto**. The Playground opens.
 
-   <!-- screenshot: Playground empty state, "What would you like to test?" with Add Context bar at bottom -->
-
 The Playground shows a prompt input area with an **Add Context** bar at the bottom. The bar shows quick-access buttons for connected sources — **Jira**, **Azure DevOps**, **Linear**, **ClickUp**, **Confluence** — and a **+** button that reveals all available sources including Figma, Files and Documents, and Video Recording.
 
 ---
@@ -77,8 +73,6 @@ The Playground shows a prompt input area with an **Add Context** bar at the bott
 
 1. In the **Add Context** bar, click **Jira**. The **Add Context** dialog opens with the Jira panel active.
 
-   <!-- screenshot: Add Context dialog showing the Jira panel with Project and Issue Type fields -->
-
 2. The **Project** field shows your connected Jira project. If you have multiple projects connected, select the one you want.
 
 3. The **Issue Type** defaults to **Story**. Change it if you want to pull in **Epics** or other **Issue Types**.
@@ -125,8 +119,6 @@ The flow for Azure DevOps, Linear, and ClickUp follows the same pattern as Jira.
 
 1. In the **Add Context** bar, click **+** and select **Figma**.
 
-   <!-- screenshot: Add Context dialog showing the Figma panel -->
-
 2. Select the **Team** from the dropdown.
 
 3. Select the **Project**.
@@ -140,8 +132,6 @@ The flow for Azure DevOps, Linear, and ClickUp follows the same pattern as Jira.
 [[info | **NOTE**:]]
 | You can select a maximum of 20 frames per session. If the page has no sections defined, only the first 20 frames are shown for selection.
 
-   <!-- screenshot: Figma frame selection showing available frames with Select Frames button -->
-
 7. Select the frames you want and click **Save**.
 
 ---

src/pages/docs/test-management/qi-home/ad-hoc/generate-test-cases.md

@@ -63,8 +63,6 @@ Atto begins generating test cases. The generation log appears in the left panel,
 
 After you click **Generate with AI**, Atto begins building your test cases. You can watch the progress in the left panel as each step completes. Generation typically takes 5–10 minutes depending on the amount of context attached.
 
-<!-- screenshot: Left panel showing generation progress with steps marked complete -->
-
 [[info | **NOTE**:]]
 | Atto searches your existing test library during generation to avoid duplicating coverage you already have. If you want faster generation without this check, you can disable it in the Playground.
 
@@ -74,8 +72,6 @@ After you click **Generate with AI**, Atto begins building your test cases. You
 
 When generation completes, the left panel shows a summary of what Atto produced.
 
-<!-- screenshot: Generation summary showing test type breakdown and scenario-to-story table -->
-
 The summary includes:
 
 - **Test type breakdown**: The number of test cases by type: Functional, Non-Functional, User Experience, and Integration.

src/pages/docs/test-management/qi-home/ad-hoc/write-effective-prompts.md

@@ -53,8 +53,6 @@ This article covers how to write prompts that get you the right test cases the f
 
 The prompt input area is the large text field in the center of the Playground, below the heading **What would you like to test?**
 
-<!-- screenshot: Playground showing the prompt input area with placeholder text -->
-
 Type your prompt directly into this field. Attached context sources appear as badges above the input. Once your prompt is ready, click **Generate with AI** to start test case generation.
 
 ---

src/pages/docs/test-management/qi-home/automation/agentic-learning/learn-test-case-live-cloud.md

@@ -83,14 +83,10 @@ Atto begins walking through each step on your live application. As each step is
 
 3. In the **Save to Library** dialog, select the folder where this test case belongs.
 
-   <!-- screenshot: Save to Library folder selection dialog -->
-
 4. Click **Save**.
 
 A success screen confirms the test case is now automated, showing the number of steps automated, the time Agentic Learning took, and an estimate of time saved compared to manual execution.
 
-<!-- screenshot: "Your first test is automated" success screen with stats -->
-
 5. Click **Go to Test Case** to return to the test case detail view.
 
 [[info | **NOTE**:]]

src/pages/docs/test-management/qi-home/automation/agentic-learning/learn-test-case-live-local.md

@@ -62,14 +62,10 @@ Local execution requires Testsigma Terminal to be running on your desktop.
 
 6. Select the **Browser** you want to use.
 
-   <!-- screenshot: Learn and Automate dialog with Local Devices selected and Browser field visible -->
-
 7. Click **Launch**.
 
    If Testsigma Terminal is not running, a prompt appears with a **Launch Terminal** button and a download link for your operating system.
 
-   <!-- screenshot: Testsigma Terminal required prompt with Launch Terminal button and download link -->
-
 Once Terminal is running and connected, the learning session opens in a browser on your machine. The Agentic Learning panel behavior is the same as Cloud. See [Learn Test Case Live (Cloud)](https://testsigma.com/docs/test-management/qi-home/automation/agentic-learning/learn-test-case-live-cloud/) for the learning session flow, generating automated steps, and saving to your library.
 
 ---
@@ -92,8 +88,6 @@ Once Terminal is running and connected, the learning session opens in a browser
    - **Uploaded apps**: Select an app you have already uploaded to Testsigma.
    - **Add Manually**: Enter the app details by hand.
 
-   <!-- screenshot: Learn and Automate dialog for Android Local showing Test Machines, Device, and App Details fields -->
-
 7. Select the **Environment** from the dropdown.
 
 8. Click **Launch**.
@@ -120,8 +114,6 @@ The iOS flow uses the same dialog as Android Local. Select **iOS** as the Applic
    - **Uploaded apps**: Select a previously uploaded .ipa.
    - **Add Manually**: Enter app details by hand.
 
-   <!-- screenshot: Learn and Automate dialog for iOS Local showing Device and App Details fields -->
-
 7. Select the **Environment** and click **Launch**.
 
 ---

src/pages/docs/test-management/qi-home/automation/agentic-learning/live-learning-controls.md

@@ -46,8 +46,6 @@ The Agentic Learning panel appears alongside the browser during a live learning
 | **Resume** | Resumes execution after a pause. |
 | **Stop** | Ends the learning session without generating automated steps. |
 
-<!-- screenshot: Agentic Learning panel during learning showing Start Learning Live App button and Record Step option -->
-
 ---
 
 ## **Session States**
@@ -69,8 +67,6 @@ When Atto needs your input, a banner appears on the test case view in Atto.
 
 1. On the test case view, click **Go to Session** in the banner. The browser tab with the learning session opens.
 
-   <!-- screenshot: Test case view showing the "Atto is waiting on your input to continue learning" banner with Go to Session button -->
-
 2. In the browser, complete the action Atto could not perform. For example, if Atto stopped at a CAPTCHA or a multi-factor authentication step, complete it manually.
 
 3. After completing the action, Atto resumes walking through the remaining steps automatically.
@@ -86,8 +82,6 @@ If a test case has already been automated and the application has changed, use *
 
 1. On the test case view, click **Re-learn and Automate** in the top action bar. This button replaces **Learn and Automate** after a test case has been automated.
 
-   <!-- screenshot: Test case view showing the Re-learn and Automate button in the action bar -->
-
 2. The **Learn and Automate** dialog opens with the same configuration options as the initial learning session. Select your Application type, Test Lab, and Environment, then click **Launch**.
 
 3. The new learning session runs the same way as the original. When it completes, save the new automated steps to your library. The previous automated steps are replaced.

src/pages/docs/test-management/qi-home/automation/agentic-learning/run-automated-test-case-with-copilot.md

@@ -44,18 +44,12 @@ This is the final step in the Agentic Learning workflow. The test case moves fro
 
 1. After Agentic Learning generates automated steps, click **Run with Copilot** in the panel.
 
-   <!-- screenshot: Agentic Learning panel showing Run with Copilot, Save to Library, and Reject buttons after steps are generated -->
-
    A confirmation dialog appears: "This ends your Agentic Learning session and opens Copilot in a fresh machine."
 
 2. Click **Continue** to proceed. The Agentic Learning session closes.
 
-   <!-- screenshot: Confirmation dialog with Continue and Dismiss buttons -->
-
 3. A new browser tab opens with the Copilot panel. The Copilot begins executing the automated steps.
 
-   <!-- screenshot: Copilot execution showing steps running with checkmarks -->
-
 For the full Copilot execution experience — including controls, step switching, and saving results — see [Execute Test Case in Cloud](https://testsigma.com/docs/test-management/qi-home/automation/copilot/execute-test-case-in-cloud/).
 
 ---
@@ -70,8 +64,6 @@ When Copilot finishes executing all steps, a confirmation dialog appears: "Test
 
 3. To end the session, click **Save and End** or **Reject and End**.
 
-   <!-- screenshot: "Test Case Executed Successfully" dialog with Save Test Case button -->
-
 [[info | **NOTE**:]]
 | The cloud VM is released when you end the session. Any unsaved changes are lost.
 

src/pages/docs/test-management/qi-home/automation/copilot/execute-test-case-in-cloud.md

@@ -54,8 +54,6 @@ Copilot opens a cloud browser on Testsigma Lab and executes your test case steps
 
 3. Click **Run with Copilot**.
 
-   <!-- screenshot: Test case page showing Run button hover dropdown with three options -->
-
 4. In the **Run with Copilot** dialog, confirm the settings:
 
    - **Test Lab**: Testsigma Lab (pre-selected for Cloud)
@@ -64,8 +62,6 @@ Copilot opens a cloud browser on Testsigma Lab and executes your test case steps
    - **Run till failed step**: Toggle on if you want execution to stop at the first failed step.
    - **Additional Settings** and **Desired Capabilities**: Expand if needed.
 
-   <!-- screenshot: Run with Copilot dialog for Cloud showing Test Lab, Debug Point, Environment, and toggles -->
-
 5. Click **Launch**.
 
 ---
@@ -74,12 +70,8 @@ Copilot opens a cloud browser on Testsigma Lab and executes your test case steps
 
 The cloud VM takes 10 to 20 seconds to provision.
 
-<!-- screenshot: "Spinning up your cloud browser" loading screen -->
-
 When the browser is ready, the Copilot panel opens alongside it. Steps execute in sequence. Each completed step is marked with a green checkmark.
 
-<!-- screenshot: Copilot panel showing steps executing with checkmarks and the browser in the background -->
-
 For the full list of controls available during execution, see [Execution Controls in Copilot](https://testsigma.com/docs/test-management/qi-home/automation/copilot/execution-controls-in-copilot/).
 
 ---
@@ -90,8 +82,6 @@ When all steps have been executed, a dialog confirms the result.
 
 1. Click **Save Test Case** to save the execution results.
 
-   <!-- screenshot: "Test Case Executed Successfully" dialog with Save Test Case and Reject buttons -->
-
 2. In the **Save to Library** dialog, select the folder and click **Save**.
 
 3. To end the session and release the cloud VM:
@@ -100,8 +90,6 @@ When all steps have been executed, a dialog confirms the result.
    - Click **Reject and End** to close the browser without saving.
    - Click **Dismiss** to keep the browser open.
 
-   <!-- screenshot: End session dialog showing Save and End, Reject and End, and Dismiss options -->
-
 [[info | **NOTE**:]]
 | The cloud VM is released when you end the session. Dismissing the dialog keeps the VM running and continues to consume resources.
 

src/pages/docs/test-management/qi-home/automation/copilot/execute-test-case-in-local.md

@@ -61,8 +61,6 @@ Local execution requires Testsigma Terminal to be running on your desktop.
    - **Environment**: Select the test environment.
    - **Run till failed step**: Toggle on if needed.
 
-   <!-- screenshot: Run with Copilot dialog for Local Web showing Test Lab set to Local Devices -->
-
 4. Click **Launch**.
 
    If Testsigma Terminal is not running, a prompt appears. Start Terminal and return to launch the session.
@@ -87,8 +85,6 @@ The Copilot panel opens in a browser on your machine. The execution flow is the
      - **Add Manually**: Enter app details by hand.
    - **Environment**: Select the test environment.
 
-   <!-- screenshot: Run with Copilot dialog for Android Local showing Test Machines, Device, and App Source fields -->
-
 3. Click **Launch**.
 
 ---
@@ -108,8 +104,6 @@ The iOS flow uses the same Run with Copilot dialog as Android Local.
    - **App Source**: Select how to specify the app (External link, Uploaded apps, or Add Manually). iOS apps use .ipa format.
    - **Environment**: Select the test environment.
 
-   <!-- screenshot: Run with Copilot dialog for iOS Local showing Device and App Source fields -->
-
 3. Click **Launch**.
 
 ---

src/pages/docs/test-management/qi-home/automation/copilot/execution-controls-in-copilot.md

@@ -51,8 +51,6 @@ The Copilot panel appears alongside the browser during execution. These controls
 | **Restart** | Restarts execution from the first step. Shown after steps have been generated. |
 | **Stop** | Ends the execution session. |
 
-<!-- screenshot: Copilot panel header showing Pause, Back, Forward, Settings, and Rec controls -->
-
 ---
 
 ## **Step Tabs**
@@ -64,8 +62,6 @@ The Copilot panel shows two tabs:
 | **Manual Steps** | The original manual test case steps. Use this to follow along or to compare with what Copilot is executing. |
 | **Automated Steps** | The automated steps Copilot is executing. Each step shows its current status. |
 
-<!-- screenshot: Copilot panel showing Manual Steps and Automated Steps tabs -->
-
 [[info | **NOTE**:]]
 | Switching to the Automated Steps tab while execution is running does not pause execution.
 
@@ -93,8 +89,6 @@ The bottom of the Copilot browser shows two debug indicators.
 | **Execution Point** | Marks the step where execution is currently paused or running. |
 | **Debug Point** | A step you configured before launch where execution automatically pauses. Useful for investigating a specific step. |
 
-<!-- screenshot: Bottom of Copilot browser showing Execution Point and Debug Point indicators -->
-
 ---
 
 ## **Switching Between Manual and Automated Steps**
@@ -106,8 +100,6 @@ The Copilot panel shows two view tabs that you can switch between at any time du
 
 Switching between tabs only changes what you see in the panel. It does not pause or stop execution.
 
-<!-- screenshot: Copilot panel showing Manual Steps and Automated Steps tabs during execution -->
-
 ---
 
 ## **Adding a New Step**
@@ -120,6 +112,4 @@ You can add a step during execution from the Automated Steps panel.
 
 3. The new step is added to the current session.
 
-<!-- screenshot: Copilot panel showing Add new step option at the bottom of the steps list -->
-
 ---

src/pages/docs/test-management/qi-home/context-mapping/connect-codex.md

@@ -49,8 +49,7 @@ When the plugin is installed and connected to a project, Atto captures your prom
 
 ## **Install the Plugin**
 
-[[info | **NOTE**:]]
-| The install command for the Codex Arcus plugin is pending confirmation from the dev team. This step will be updated before publication.
+Install the Arcus plugin from the Codex marketplace.
 
 ---
 

src/pages/docs/test-management/qi-home/context-mapping/connect-cursor.md

@@ -49,7 +49,7 @@ When the plugin is installed and connected to a project, Atto captures your prom
 
 ## **Install the Plugin**
 
-The install Arcus plugin from Cursor marketplace.
+Install the Arcus plugin from the Cursor marketplace.
 
 ---
 

src/pages/docs/test-management/qi-home/context-mapping/connect-github-copilot.md

@@ -52,8 +52,7 @@ When the plugin is installed and connected to a project, Atto captures your prom
 
 ## **Install the Plugin**
 
-[[info | **NOTE**:]]
-| The install command for the GitHub Copilot Arcus plugin is pending confirmation from the dev team. This step will be updated before publication.
+Install the Arcus plugin from the GitHub Copilot marketplace.
 
 ---
 

src/pages/docs/test-management/qi-home/quality-intelligence-metrics.md

@@ -47,8 +47,6 @@ QI Home displays five metrics in the session header that together give you a rea
 
 The metrics are displayed left to right in the session header in evaluation order. Each metric builds on the previous one: Coverage answers whether enough has been tested, Pass Rate answers whether what was tested is working, Confidence answers whether those results can be trusted, Release Readiness combines all three into a single score, and Release Gate converts that score into a decision.
 
-<!-- screenshot: Session header showing all five QI metrics with their current values and band labels -->
-
 ---
 
 ## **Coverage**

src/pages/docs/test-management/qi-home/sprints/generate-test-cases.md

@@ -101,8 +101,6 @@ If you clicked **Not Now** on a sprint or if Atto missed a sprint notification,
 
 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.
 
-<!-- screenshot: Generation progress log in left panel showing steps completing -->
-
 See [Generate Test Cases](https://testsigma.com/docs/test-management/qi-home/ad-hoc/generate-test-cases/) in the Ad-Hoc section for details on what Atto does during generation and how to read the generation summary.
 
 ---

src/pages/docs/test-management/reports/view-reports.md

@@ -35,7 +35,7 @@ Reports in Arcus by Testsigma provide dynamic, visual insights into test executi
 
 > ## **Prerequisites**
 >
-> Before you begin, ensure that you have one or more created reports. For steps to create a report, see [Creating a Report]().
+> Before you begin, ensure that you have one or more created reports. For steps to create a report, see [Creating Reports](https://testsigma.com/docs/test-management/reports/create-report/).
 
 ---