diff --git a/src/pages/docs/arcus/integrations/azure-devops.md b/src/pages/docs/test-management/integrations/azure-devops.md
similarity index 97%
rename from src/pages/docs/arcus/integrations/azure-devops.md
rename to src/pages/docs/test-management/integrations/azure-devops.md
index fcfe8e1..7fb1b6a 100644
--- a/src/pages/docs/arcus/integrations/azure-devops.md
+++ b/src/pages/docs/test-management/integrations/azure-devops.md
@@ -4,7 +4,7 @@ page_title: 'Azure DevOps Integration with Arcus by Testsigma'
metadesc: 'Arcus by Testsigma integrates with Azure DevOps to link test defects to work items, improving traceability and collaboration.'
noindex: false
order: 10.8
-page_id: 'azure-devops-integration-with-arcus-by-testsigma'
+page_id: 'azure-devops-integration-with-test-management-by-testsigma'
warning: false
contextual_links:
- type: section
diff --git a/src/pages/docs/arcus/integrations/azure-two-way-integration/manage-test-cases-in-azure-devops.md b/src/pages/docs/test-management/integrations/azure-two-way-integration/manage-test-cases-in-azure-devops.md
similarity index 100%
rename from src/pages/docs/arcus/integrations/azure-two-way-integration/manage-test-cases-in-azure-devops.md
rename to src/pages/docs/test-management/integrations/azure-two-way-integration/manage-test-cases-in-azure-devops.md
diff --git a/src/pages/docs/arcus/integrations/azure-two-way-integration/manage-test-runs-in-azure-devops.md b/src/pages/docs/test-management/integrations/azure-two-way-integration/manage-test-runs-in-azure-devops.md
similarity index 100%
rename from src/pages/docs/arcus/integrations/azure-two-way-integration/manage-test-runs-in-azure-devops.md
rename to src/pages/docs/test-management/integrations/azure-two-way-integration/manage-test-runs-in-azure-devops.md
diff --git a/src/pages/docs/arcus/integrations/azure-two-way-integration/testsigma-integration-app-for-azuredevops.md b/src/pages/docs/test-management/integrations/azure-two-way-integration/testsigma-integration-app-for-azuredevops.md
similarity index 100%
rename from src/pages/docs/arcus/integrations/azure-two-way-integration/testsigma-integration-app-for-azuredevops.md
rename to src/pages/docs/test-management/integrations/azure-two-way-integration/testsigma-integration-app-for-azuredevops.md
diff --git a/src/pages/docs/arcus/integrations/clickup.md b/src/pages/docs/test-management/integrations/clickup.md
similarity index 100%
rename from src/pages/docs/arcus/integrations/clickup.md
rename to src/pages/docs/test-management/integrations/clickup.md
diff --git a/src/pages/docs/arcus/integrations/confluence.md b/src/pages/docs/test-management/integrations/confluence.md
similarity index 100%
rename from src/pages/docs/arcus/integrations/confluence.md
rename to src/pages/docs/test-management/integrations/confluence.md
diff --git a/src/pages/docs/arcus/integrations/figma.md b/src/pages/docs/test-management/integrations/figma.md
similarity index 100%
rename from src/pages/docs/arcus/integrations/figma.md
rename to src/pages/docs/test-management/integrations/figma.md
diff --git a/src/pages/docs/arcus/integrations/jira-two-way-integration/install-and-connect-testsigma.md b/src/pages/docs/test-management/integrations/jira-two-way-integration/install-and-connect-testsigma.md
similarity index 98%
rename from src/pages/docs/arcus/integrations/jira-two-way-integration/install-and-connect-testsigma.md
rename to src/pages/docs/test-management/integrations/jira-two-way-integration/install-and-connect-testsigma.md
index 8254068..c5064b3 100644
--- a/src/pages/docs/arcus/integrations/jira-two-way-integration/install-and-connect-testsigma.md
+++ b/src/pages/docs/test-management/integrations/jira-two-way-integration/install-and-connect-testsigma.md
@@ -14,7 +14,7 @@ contextual_links:
url: '#prerequisites'
- type: link
name: 'Install the Arcus by Testsigma app'
- url: '#install-the-arcus-by-testsigma-app'
+ url: '#install-the-test-management-by-testsigma-app'
- type: link
name: 'Connect Testsigma and Jira'
url: '#connect-testsigma-and-jira'
diff --git a/src/pages/docs/arcus/integrations/jira-two-way-integration/manage-test-cases-in-jira.md b/src/pages/docs/test-management/integrations/jira-two-way-integration/manage-test-cases-in-jira.md
similarity index 100%
rename from src/pages/docs/arcus/integrations/jira-two-way-integration/manage-test-cases-in-jira.md
rename to src/pages/docs/test-management/integrations/jira-two-way-integration/manage-test-cases-in-jira.md
diff --git a/src/pages/docs/arcus/integrations/jira-two-way-integration/manage-test-runs-in-jira.md b/src/pages/docs/test-management/integrations/jira-two-way-integration/manage-test-runs-in-jira.md
similarity index 100%
rename from src/pages/docs/arcus/integrations/jira-two-way-integration/manage-test-runs-in-jira.md
rename to src/pages/docs/test-management/integrations/jira-two-way-integration/manage-test-runs-in-jira.md
diff --git a/src/pages/docs/arcus/integrations/jira.md b/src/pages/docs/test-management/integrations/jira.md
similarity index 100%
rename from src/pages/docs/arcus/integrations/jira.md
rename to src/pages/docs/test-management/integrations/jira.md
diff --git a/src/pages/docs/arcus/integrations/linear.md b/src/pages/docs/test-management/integrations/linear.md
similarity index 100%
rename from src/pages/docs/arcus/integrations/linear.md
rename to src/pages/docs/test-management/integrations/linear.md
diff --git a/src/pages/docs/arcus/introduction/getting-started.md b/src/pages/docs/test-management/introduction/getting-started.md
similarity index 64%
rename from src/pages/docs/arcus/introduction/getting-started.md
rename to src/pages/docs/test-management/introduction/getting-started.md
index 20a1bfc..4a3f77b 100644
--- a/src/pages/docs/arcus/introduction/getting-started.md
+++ b/src/pages/docs/test-management/introduction/getting-started.md
@@ -9,6 +9,9 @@ warning: false
contextual_links:
- type: section
name: 'Contents'
+ - type: link
+ name: 'Interactive Demo'
+ url: '#interactive-demo'
- type: link
name: 'Steps to Access Arcus by Testsigma'
url: '#steps-to-access-testsigma-test-management'
@@ -25,7 +28,18 @@ Get started with our platform and streamline how you manage and analyze test cas
> ## **Prerequisites**
>
-> Before you begin, ensure you have an active Testsigma account. If you don’t have one, go to the
Testsigma signup page to create an account.
+> Before you begin, ensure you have an active Testsigma account. If you don’t have one, go to the
Testsigma signup page to create an account.
+
+---
+
+## **Interactive Demo**
+
+
---
@@ -35,7 +49,7 @@ Get started with our platform and streamline how you manage and analyze test cas
2. Sign in with your credentials. If you don't have an account,
sign up.
-3. In your **User Profile Settings**, select **Arcus**.
+3. In your **User Profile Settings**, select **TMS**.
4. You'll be redirected to **Arcus by Testsigma** application.
diff --git a/src/pages/docs/test-management/introduction/overview.md b/src/pages/docs/test-management/introduction/overview.md
new file mode 100644
index 0000000..f3e9f27
--- /dev/null
+++ b/src/pages/docs/test-management/introduction/overview.md
@@ -0,0 +1,62 @@
+---
+title: 'Overview: Arcus by Testsigma'
+page_title: 'Overview of Test Management in Testsigma'
+metadesc: 'This article discusses overview of test management tool in Testsigma | Keep your test cases, test plans, test runs, and reports organized in one place'
+noindex: false
+order: 1.1
+page_id: 'Overview: Arcus by Testsigma'
+warning: false
+contextual_links:
+ - type: section
+ name: 'Contents'
+ - type: link
+ name: 'Benefits of Using Arcus by Testsigma'
+ url: '#benefits-of-using-testsigma-test-management'
+ - type: link
+ name: 'Quality Intelligence'
+ url: '#quality-intelligence'
+---
+
+---
+
+Managing test cases shouldn't be a mess. If you're using traditional Test Management tools or Excel for it, you know the pain! Endless spreadsheets, scattered data, and lots of copy-pasting. As the projects grow, things only get worse.
+
+Arcus by Testsigma changes that. It keeps your test cases, test plans, test runs, and reports organized and accessible in one place. No more digging through tabs or wondering who updated what.
+
+Test Management isn’t just about managing tests, it’s about making testing work for you, not against you!
+
+---
+
+## **Benefits of Using Arcus by Testsigma**
+
+### ⚡ **Faster Testing, Fewer Errors**
+
+Automate repetitive tasks and reduce manual errors to speed up test execution.
+
+### 🤝 **Seamless Collaboration**
+
+Centralize test management so teams and stakeholders always stay aligned.
+
+### 📋 **Better Test Coverage**
+
+Document every test case for thorough and consistent testing.
+
+### 🐞 **Effortless Defect Tracking**
+
+Log and track defects instantly with Jira integration.
+
+### 🧠 **Quality Intelligence, Powered by AI**
+
+Generate test cases from your requirements, track coverage as you go, and get a real-time read on release readiness, all without leaving Arcus.
+
+---
+
+## **Quality Intelligence**
+
+Quality Intelligence is where AI does the heavy lifting for you. Point it at your requirements, whether that's a Jira story, a Confluence page, a Figma design, or your developers' pull requests, and it generates test cases, tracks coverage against your modules, builds test plans, and can even automate execution.
+
+Instead of writing test cases from scratch, you review what Quality Intelligence generates, accept the ones that are accurate, and save them to your library. Coverage, test plans, and five key quality metrics, Coverage, Pass Rate, Confidence, Release Readiness, and Release Gate, update automatically as you go, so you always know how confident you can be in your current build.
+
+See [Overview: QI Home](https://testsigma.com/docs/test-management/qi-home/overview/) to learn how test generation, coverage tracking, and automation work together in Quality Intelligence.
+
+---
diff --git a/src/pages/docs/arcus/manage-users/invite-users.md b/src/pages/docs/test-management/manage-users/invite-users.md
similarity index 100%
rename from src/pages/docs/arcus/manage-users/invite-users.md
rename to src/pages/docs/test-management/manage-users/invite-users.md
diff --git a/src/pages/docs/arcus/projects/manage-projects.md b/src/pages/docs/test-management/projects/manage-projects.md
similarity index 100%
rename from src/pages/docs/arcus/projects/manage-projects.md
rename to src/pages/docs/test-management/projects/manage-projects.md
diff --git a/src/pages/docs/arcus/projects/project-settings.md b/src/pages/docs/test-management/projects/project-settings.md
similarity index 100%
rename from src/pages/docs/arcus/projects/project-settings.md
rename to src/pages/docs/test-management/projects/project-settings.md
diff --git a/src/pages/docs/arcus/qi-home/ad-hoc/attach-context-sources.md b/src/pages/docs/test-management/qi-home/ad-hoc/attach-context-sources.md
similarity index 88%
rename from src/pages/docs/arcus/qi-home/ad-hoc/attach-context-sources.md
rename to src/pages/docs/test-management/qi-home/ad-hoc/attach-context-sources.md
index 4ff4f47..6009f7b 100644
--- a/src/pages/docs/arcus/qi-home/ad-hoc/attach-context-sources.md
+++ b/src/pages/docs/test-management/qi-home/ad-hoc/attach-context-sources.md
@@ -1,8 +1,8 @@
---
title: 'Attach Context Sources'
page_title: 'Attach Context Sources'
-metadesc: 'Attach context sources such as Jira, Confluence, Figma, files, and video recordings so the Generator Agent creates test cases that accurately reflect your feature.'
-description: 'Learn how to attach context sources in the Playground before generating test cases with the Generator Agent.'
+metadesc: 'Attach context sources such as Jira, Confluence, Figma, files, and video recordings so Atto generates test cases that accurately reflect your feature.'
+description: 'Learn how to attach context sources in the Playground before generating test cases with Atto.'
noindex: false
order: 13.21
page_id: 'qi-home-attach-context-sources'
@@ -38,11 +38,11 @@ contextual_links:
-**Give the Generator Agent the right context and it creates test cases that accurately reflect your feature.**
+**Give Atto the right context and it generates test cases that accurately reflect your feature.**
---
-Context sources are the inputs the Generator Agent reads before generating test cases. The more relevant your context, the more accurate and complete the output. You can attach context from your project management tools, design files, images, videos, and documents, all in the same session.
+Context sources are the inputs Atto reads before generating test cases. The more relevant your context, the more accurate and complete the output. You can attach context from your project management tools, design files, images, videos, and documents, all in the same session.
You attach context sources inside the Playground, before writing a prompt and triggering generation. You can attach from multiple sources in a single session and add or remove sources any time before clicking **Generate with AI**.
@@ -83,7 +83,7 @@ The Playground shows a prompt input area with an **Add Context** bar at the bott
3. The **Issue Type** defaults to **Story**. Change it if you want to pull in **Epics** or other **Issue Types**.
-4. In the stories list, select the checkboxes next to the stories you want the Generator Agent to use as context.
+4. In the stories list, select the checkboxes next to the stories you want Atto to use as context.
[[info | **NOTE**:]]
| Use the **Search** icon at the top of the stories list to find specific stories by title or ID.
@@ -112,7 +112,7 @@ The flow for Azure DevOps, Linear, and ClickUp follows the same pattern as Jira.
2. Select the **Space** you want to pull pages from.
-3. Select the **Pages** you want the Generator Agent to read.
+3. Select the **Pages** you want Atto to read.
4. Click **Save**.
@@ -191,6 +191,6 @@ After saving a source, it appears as a badge at the top of the prompt input show
[[info | **NOTE**:]]
| Context is not saved between sessions. Each new Ad-Hoc session starts with no context attached.
-With context attached, the next step is to write your prompt. See [Write Effective Prompts](https://testsigma.com/docs/arcus/qi-home/ad-hoc/write-effective-prompts/).
+With context attached, the next step is to write your prompt. See [Write Effective Prompts](https://testsigma.com/docs/test-management/qi-home/ad-hoc/write-effective-prompts/).
---
diff --git a/src/pages/docs/arcus/qi-home/ad-hoc/generate-test-cases.md b/src/pages/docs/test-management/qi-home/ad-hoc/generate-test-cases.md
similarity index 57%
rename from src/pages/docs/arcus/qi-home/ad-hoc/generate-test-cases.md
rename to src/pages/docs/test-management/qi-home/ad-hoc/generate-test-cases.md
index b482c50..bab4dfb 100644
--- a/src/pages/docs/arcus/qi-home/ad-hoc/generate-test-cases.md
+++ b/src/pages/docs/test-management/qi-home/ad-hoc/generate-test-cases.md
@@ -1,8 +1,8 @@
---
title: 'Generate Test Cases'
page_title: 'Generate Test Cases (Ad-Hoc)'
-metadesc: 'Write your prompt, click Generate with AI, and the Generator Agent builds your test cases. Learn how to trigger Ad-Hoc generation and read the generation summary.'
-description: 'Learn how to trigger test case generation in Ad-Hoc and what the Generator Agent does during the process.'
+metadesc: 'Write your prompt, click Generate with AI, and Atto builds your test cases. Learn how to trigger Ad-Hoc generation and read the generation summary.'
+description: 'Learn how to trigger test case generation in Ad-Hoc and what Atto does during the process.'
noindex: false
order: 13.23
page_id: 'qi-home-ad-hoc-generate-test-cases'
@@ -29,18 +29,18 @@ contextual_links:
-**Write your prompt, click Generate with AI, and the Generator Agent builds your test cases.**
+**Write your prompt, click Generate with AI, and Atto builds your test cases.**
---
-This article covers how to trigger test case generation in Ad-Hoc and what the Generator Agent does during the process. Before generating, make sure you have attached your context sources and written your prompt. See [Attach Context Sources](https://testsigma.com/docs/arcus/qi-home/ad-hoc/attach-context-sources/) and [Write Effective Prompts](https://testsigma.com/docs/arcus/qi-home/ad-hoc/write-effective-prompts/).
+This article covers how to trigger test case generation in Ad-Hoc and what Atto does during the process. Before generating, make sure you have attached your context sources and written your prompt. See [Attach Context Sources](https://testsigma.com/docs/test-management/qi-home/ad-hoc/attach-context-sources/) and [Write Effective Prompts](https://testsigma.com/docs/test-management/qi-home/ad-hoc/write-effective-prompts/).
---
> ## **Prerequisites**
>
> Before you begin, ensure that:
-> - The Playground is open from **QI Home > Adhoc**. See [Attach Context Sources](https://testsigma.com/docs/arcus/qi-home/ad-hoc/attach-context-sources/) and [Write Effective Prompts](https://testsigma.com/docs/arcus/qi-home/ad-hoc/write-effective-prompts/) if you have not done this yet.
+> - The Playground is open from **QI Home > Adhoc**. See [Attach Context Sources](https://testsigma.com/docs/test-management/qi-home/ad-hoc/attach-context-sources/) and [Write Effective Prompts](https://testsigma.com/docs/test-management/qi-home/ad-hoc/write-effective-prompts/) if you have not done this yet.
> - You have attached at least one context source and written your prompt.
---
@@ -55,24 +55,24 @@ This article covers how to trigger test case generation in Ad-Hoc and what the G
4. Click **Generate with AI**.
-The Generator Agent begins generating test cases. The generation log appears in the left panel, showing each step as it progresses.
+Atto begins generating test cases. The generation log appears in the left panel, showing each step as it progresses.
---
## **What Happens During Generation**
-After you click **Generate with AI**, the Generator Agent 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.
+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.
[[info | **NOTE**:]]
-| The Generator Agent 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.
+| 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.
---
## **Review the Generation Summary**
-When generation completes, the left panel shows a summary of what the Generator Agent produced.
+When generation completes, the left panel shows a summary of what Atto produced.
@@ -80,11 +80,11 @@ The summary includes:
- **Test type breakdown**: The number of test cases by type: Functional, Non-Functional, User Experience, and Integration.
- **Scenarios with full test cases**: A table listing each scenario, its mapped story, and the number of test cases generated.
-- **Reusable Step Groups proposed**: Step groups the Generator Agent identified from your test library that apply to the generated scenarios.
+- **Reusable Step Groups proposed**: Step groups Atto identified from your test library that apply to the generated scenarios.
- **Remaining Scenario Outlines**: Scenarios that have been created as stubs but not yet fully filled. These are organized by area (for example, Search, Filters, Checkout). You can fill them later using the Playground.
[[info | **NOTE**:]]
-| Remaining Scenario Outlines are not test cases yet. They are placeholders that flag areas needing coverage. See [Use Playground](https://testsigma.com/docs/arcus/qi-home/use-playground/) to generate full test cases from them.
+| Remaining Scenario Outlines are not test cases yet. They are placeholders Atto created to flag areas that need coverage. See [Use Playground](https://testsigma.com/docs/test-management/qi-home/use-playground/) to generate full test cases from them.
---
@@ -96,8 +96,8 @@ The main area switches to the session detail view with three tabs: **Tests**, **
From here you can:
-- Review and accept test cases from the **Tests** tab. See [Review and Accept Test Cases](https://testsigma.com/docs/arcus/qi-home/review-and-accept-test-cases/).
-- Add more context or generate additional test cases by clicking **Open Playground**. See [Use Playground](https://testsigma.com/docs/arcus/qi-home/use-playground/).
-- Track coverage and gaps from the **Coverage** tab. See [Coverage and Gaps](https://testsigma.com/docs/arcus/qi-home/coverage-and-gaps/).
+- Review and accept test cases from the **Tests** tab. See [Review and Accept Test Cases](https://testsigma.com/docs/test-management/qi-home/review-and-accept-test-cases/).
+- Add more context or generate additional test cases by clicking **Open Playground**. See [Use Playground](https://testsigma.com/docs/test-management/qi-home/use-playground/).
+- Track coverage and gaps from the **Coverage** tab. See [Coverage and Gaps](https://testsigma.com/docs/test-management/qi-home/coverage-and-gaps/).
---
diff --git a/src/pages/docs/arcus/qi-home/ad-hoc/write-effective-prompts.md b/src/pages/docs/test-management/qi-home/ad-hoc/write-effective-prompts.md
similarity index 89%
rename from src/pages/docs/arcus/qi-home/ad-hoc/write-effective-prompts.md
rename to src/pages/docs/test-management/qi-home/ad-hoc/write-effective-prompts.md
index a0c7ce0..e27cfab 100644
--- a/src/pages/docs/arcus/qi-home/ad-hoc/write-effective-prompts.md
+++ b/src/pages/docs/test-management/qi-home/ad-hoc/write-effective-prompts.md
@@ -1,8 +1,8 @@
---
title: 'Write Effective Prompts'
page_title: 'Write Effective Prompts'
-metadesc: 'The quality of your prompt determines the quality of the Generator Agent output. Learn how to write clear, specific prompts that generate accurate, relevant test cases.'
-description: 'Learn how to write effective prompts that generate accurate test cases with the Generator Agent.'
+metadesc: 'The quality of your prompt determines the quality of Atto output. Learn how to write clear, specific prompts that generate accurate, relevant test cases.'
+description: 'Learn how to write effective prompts that generate accurate test cases with Atto.'
noindex: false
order: 13.22
page_id: 'qi-home-write-effective-prompts'
@@ -32,11 +32,11 @@ contextual_links:
-**The quality of your prompt determines the quality of the Generator Agent's output.**
+**The quality of your prompt determines the quality of Atto's output.**
---
-Prompts are how you tell the Generator Agent what to test. A well-written prompt gives it the goal, the context, and the constraints it needs to generate test cases that are accurate and relevant. Vague prompts produce generic test cases. Specific prompts produce test cases that match your feature.
+Prompts are how you tell Atto what to test. A well-written prompt gives Atto the goal, the context, and the constraints it needs to generate test cases that are accurate and relevant. Vague prompts produce generic test cases. Specific prompts produce test cases that match your feature.
This article covers how to write prompts that get you the right test cases the first time.
@@ -45,7 +45,7 @@ This article covers how to write prompts that get you the right test cases the f
> ## **Prerequisites**
>
> Before you begin, ensure that:
-> - The Playground is open with context attached. See [Attach Context Sources](https://testsigma.com/docs/arcus/qi-home/ad-hoc/attach-context-sources/) if you have not done this yet.
+> - The Playground is open with context attached. See [Attach Context Sources](https://testsigma.com/docs/test-management/qi-home/ad-hoc/attach-context-sources/) if you have not done this yet.
---
@@ -81,7 +81,7 @@ You do not need to use all five elements every time. Start with WHAT and add the
Before clicking **Generate with AI**, run through this checklist:
-- **Goal**: Have you stated what you want the Generator Agent to generate?
+- **Goal**: Have you stated what you want Atto to generate?
- **Context**: Have you described the feature, flow, or user story?
- **Inputs**: Have you attached the relevant stories, files, and designs?
- **Edge Cases**: Have you called out tricky or high-risk conditions to include?
@@ -197,11 +197,11 @@ Expected Outcomes:
## **Tips for Better Prompts**
-- **Use personas.** "As a mobile user on a slow connection…" gives the Generator Agent relevant constraints that affect test design.
+- **Use personas.** "As a mobile user on a slow connection…" gives Atto relevant constraints that affect test design.
- **Reference your context.** If you have attached Jira stories, mention the story IDs in the prompt. For example: "Generate test cases for AUTOM-3 and AUTOM-4, focusing on the OAuth login flow."
- **Call out what matters most.** If security, performance, or accessibility is a priority for this feature, say so explicitly.
- **Iterate.** If the first generation does not cover everything you need, open the Playground and refine the prompt with additional context or more specific constraints.
-When your prompt is ready, see [Generate Test Cases](https://testsigma.com/docs/arcus/qi-home/ad-hoc/generate-test-cases/).
+When your prompt is ready, see [Generate Test Cases](https://testsigma.com/docs/test-management/qi-home/ad-hoc/generate-test-cases/).
---
diff --git a/src/pages/docs/arcus/qi-home/automation/agentic-learning/learn-test-case-live-cloud.md b/src/pages/docs/test-management/qi-home/automation/agentic-learning/learn-test-case-live-cloud.md
similarity index 72%
rename from src/pages/docs/arcus/qi-home/automation/agentic-learning/learn-test-case-live-cloud.md
rename to src/pages/docs/test-management/qi-home/automation/agentic-learning/learn-test-case-live-cloud.md
index cb07217..8014ee8 100644
--- a/src/pages/docs/arcus/qi-home/automation/agentic-learning/learn-test-case-live-cloud.md
+++ b/src/pages/docs/test-management/qi-home/automation/agentic-learning/learn-test-case-live-cloud.md
@@ -1,7 +1,7 @@
---
title: 'Learn Test Case Live (Cloud)'
page_title: 'Learn Test Case Live (Cloud)'
-metadesc: 'Let the Runner Agent walk through your test case on a cloud browser on Testsigma Lab and generate automated steps for you — no scripts required.'
+metadesc: 'Let Atto walk through your test case on a cloud browser on Testsigma Lab and generate automated steps for you — no scripts required.'
description: 'Learn how to run Agentic Learning on a cloud browser to automate a test case.'
noindex: false
order: 13.31
@@ -29,7 +29,7 @@ contextual_links:
-**Let the Runner Agent walk through your test case on a cloud browser and generate automated steps for you.**
+**Let Atto walk through your test case on a cloud browser and generate automated steps for you.**
---
@@ -63,15 +63,15 @@ Use Cloud when you do not want to set up anything locally. Testsigma Lab provide
## **During the Learning Session**
-When the browser tab opens, the Runner Agent introduces itself and displays the test case steps in the Agentic Learning panel.
+When the browser tab opens, Atto introduces itself and displays the test case steps in the Agentic Learning panel.
-The Runner Agent begins walking through each step on your live application. As each step is validated, it is marked with a checkmark in the panel.
+Atto begins walking through each step on your live application. As each step is validated, it is marked with a checkmark in the panel.
**What you can do during learning:**
-- Watch the Runner Agent execute each step in the browser.
-- If it gets stuck or waits for your input, a banner appears: "Atto is waiting on your input to continue learning." Click **Go to Session** to provide guidance. See [Live Learning Controls](https://testsigma.com/docs/arcus/qi-home/automation/agentic-learning/live-learning-controls/).
-- Click **Start Learning Live App** to begin interactive learning if it has not started automatically.
+- Watch Atto execute each step in the browser.
+- If Atto gets stuck or waits for your input, a banner appears: "Atto is waiting on your input to continue learning." Click **Go to Session** to provide guidance. See [Live Learning Controls](https://testsigma.com/docs/test-management/qi-home/automation/agentic-learning/live-learning-controls/).
+- Click **Start Learning Live App** to begin interactive learning if Atto has not started automatically.
---
@@ -104,8 +104,8 @@ While Agentic Learning is running, the test case shows a status on the sprint or
| Status | What it means |
| :--- | :--- |
-| **Agentic Learning in progress** | Learning is running. The Runner Agent is walking through the steps. |
-| **Atto needs user's input** | The Runner Agent has paused and is waiting for you to provide guidance in the browser session. |
+| **Agentic Learning in progress** | Learning is running. Atto is walking through the steps. |
+| **Atto needs user's input** | Atto has paused and is waiting for you to provide guidance in the browser session. |
| **Learn and Automated** | Learning completed and automated steps were saved successfully. |
---
diff --git a/src/pages/docs/arcus/qi-home/automation/agentic-learning/learn-test-case-live-local.md b/src/pages/docs/test-management/qi-home/automation/agentic-learning/learn-test-case-live-local.md
similarity index 82%
rename from src/pages/docs/arcus/qi-home/automation/agentic-learning/learn-test-case-live-local.md
rename to src/pages/docs/test-management/qi-home/automation/agentic-learning/learn-test-case-live-local.md
index fc1a23c..c5c2398 100644
--- a/src/pages/docs/arcus/qi-home/automation/agentic-learning/learn-test-case-live-local.md
+++ b/src/pages/docs/test-management/qi-home/automation/agentic-learning/learn-test-case-live-local.md
@@ -33,7 +33,7 @@ contextual_links:
---
-Agentic Learning (Local) works the same way as Cloud — the Runner Agent walks through your test case on a live application and generates automated steps — but the browser or device runs on your local machine instead of Testsigma Lab. Use Local when your application is not publicly accessible, when you need to test against a local build, or when you are automating mobile test cases on a physical device or emulator.
+Agentic Learning (Local) works the same way as Cloud — Atto walks through your test case on a live application and generates automated steps — but the browser or device runs on your local machine instead of Testsigma Lab. Use Local when your application is not publicly accessible, when you need to test against a local build, or when you are automating mobile test cases on a physical device or emulator.
Local execution requires Testsigma Terminal to be running on your desktop.
@@ -70,7 +70,7 @@ Local execution requires Testsigma Terminal to be running on your desktop.
-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/arcus/qi-home/automation/agentic-learning/learn-test-case-live-cloud/) for the learning session flow, generating automated steps, and saving to your library.
+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.
---
@@ -128,8 +128,8 @@ The iOS flow uses the same dialog as Android Local. Select **iOS** as the Applic
## **During the Learning Session**
-The Agentic Learning panel behavior is the same for Local as it is for Cloud. The Runner Agent walks through the steps, marks each one with a checkmark, and waits for your input if it gets stuck. See [Live Learning Controls](https://testsigma.com/docs/arcus/qi-home/automation/agentic-learning/live-learning-controls/) for controls available during the session.
+The Agentic Learning panel behavior is the same for Local as it is for Cloud. Atto walks through the steps, marks each one with a checkmark, and waits for your input if it gets stuck. See [Live Learning Controls](https://testsigma.com/docs/test-management/qi-home/automation/agentic-learning/live-learning-controls/) for controls available during the session.
-After learning completes, generate and save automated steps following the same steps as Cloud. See [Learn Test Case Live (Cloud)](https://testsigma.com/docs/arcus/qi-home/automation/agentic-learning/learn-test-case-live-cloud/).
+After learning completes, generate and save automated steps following the same steps as Cloud. See [Learn Test Case Live (Cloud)](https://testsigma.com/docs/test-management/qi-home/automation/agentic-learning/learn-test-case-live-cloud/).
---
diff --git a/src/pages/docs/arcus/qi-home/automation/agentic-learning/live-learning-controls.md b/src/pages/docs/test-management/qi-home/automation/agentic-learning/live-learning-controls.md
similarity index 62%
rename from src/pages/docs/arcus/qi-home/automation/agentic-learning/live-learning-controls.md
rename to src/pages/docs/test-management/qi-home/automation/agentic-learning/live-learning-controls.md
index 444f39d..9e66347 100644
--- a/src/pages/docs/arcus/qi-home/automation/agentic-learning/live-learning-controls.md
+++ b/src/pages/docs/test-management/qi-home/automation/agentic-learning/live-learning-controls.md
@@ -1,7 +1,7 @@
---
title: 'Live Learning Controls'
page_title: 'Live Learning Controls'
-metadesc: 'The controls available to you during an Agentic Learning session — panel controls, session states, providing input when the Runner Agent gets stuck, and re-learning a test case.'
+metadesc: 'The controls available to you during an Agentic Learning session — panel controls, session states, providing input when Atto gets stuck, and re-learning a test case.'
description: 'Reference for the controls and session states available during an Agentic Learning session.'
noindex: false
order: 13.33
@@ -17,8 +17,8 @@ contextual_links:
name: 'Session States'
url: '#session-states'
- type: link
- name: 'Providing Input When the Runner Agent Gets Stuck'
- url: '#providing-input-when-the-runner-agent-gets-stuck'
+ name: 'Providing Input When Atto Gets Stuck'
+ url: '#providing-input-when-atto-gets-stuck'
- type: link
name: 'Re-Learning a Test Case'
url: '#re-learning-a-test-case'
@@ -40,9 +40,9 @@ The Agentic Learning panel appears alongside the browser during a live learning
| Control | What it does |
| :--- | :--- |
-| **Start Learning Live App** | Start the learning session. The Runner Agent begins walking through the test case steps on the live application. This button appears when the session is ready but has not yet started. |
-| **Record Step** | Manually records the current state of the browser or device as a step. Use this if the Runner Agent misses a step or if you want to add a step that is not in the original test case. |
-| **Pause** | Pauses the Runner Agent's execution. It stops walking through steps and waits for you to resume. |
+| **Start Learning Live App** | Start the learning session. Atto begins walking through the test case steps on the live application. This button appears when the session is ready but has not yet started. |
+| **Record Step** | Manually records the current state of the browser or device as a step. Use this if Atto misses a step or if you want to add a step that is not in the original test case. |
+| **Pause** | Pauses Atto's execution. Atto stops walking through steps and waits for you to resume. |
| **Resume** | Resumes execution after a pause. |
| **Stop** | Ends the learning session without generating automated steps. |
@@ -56,24 +56,24 @@ The panel and the test case view reflect the current state of the learning sessi
| State | What it means | What you see |
| :--- | :--- | :--- |
-| **Learning** | The Runner Agent is actively walking through steps. | Steps list with spinner on the current step. "Learning..." status in the panel. |
-| **Atto needs user's input** | The Runner Agent has reached a step it cannot complete without guidance. The session is paused. | Yellow banner on the test case view: "Atto is waiting on your input to continue learning." **Go to Session** button. |
-| **Completed** | The Runner Agent has walked through all steps. | Steps list with checkmarks. "Generate Automated Steps", "Save to Library", and "Reject" buttons appear. |
-| **Generation Failed** | The Runner Agent could not generate automated steps from the learned session. | "Generation Failed" error with an **Edit** option. |
+| **Learning** | Atto is actively walking through steps. | Steps list with spinner on the current step. "Learning..." status in the panel. |
+| **Atto needs user's input** | Atto has reached a step it cannot complete without guidance. The session is paused. | Yellow banner on the test case view: "Atto is waiting on your input to continue learning." **Go to Session** button. |
+| **Completed** | Atto has walked through all steps. | Steps list with checkmarks. "Generate Automated Steps", "Save to Library", and "Reject" buttons appear. |
+| **Generation Failed** | Atto could not generate automated steps from the learned session. | "Generation Failed" error with an **Edit** option. |
---
-## **Providing Input When the Runner Agent Gets Stuck**
+## **Providing Input When Atto Gets Stuck**
-When the Runner Agent needs your input, a banner appears on the test case view.
+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.
-2. In the browser, complete the action the Runner Agent could not perform. For example, if it stopped at a CAPTCHA or a multi-factor authentication step, complete it manually.
+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, the Runner Agent resumes walking through the remaining steps automatically.
+3. After completing the action, Atto resumes walking through the remaining steps automatically.
[[info | **NOTE**:]]
| If you close the browser tab without completing the required action, the learning session ends and you will need to start a new session.
diff --git a/src/pages/docs/arcus/qi-home/automation/agentic-learning/run-automated-test-case-with-copilot.md b/src/pages/docs/test-management/qi-home/automation/agentic-learning/run-automated-test-case-with-copilot.md
similarity index 89%
rename from src/pages/docs/arcus/qi-home/automation/agentic-learning/run-automated-test-case-with-copilot.md
rename to src/pages/docs/test-management/qi-home/automation/agentic-learning/run-automated-test-case-with-copilot.md
index 85aec54..02b763e 100644
--- a/src/pages/docs/arcus/qi-home/automation/agentic-learning/run-automated-test-case-with-copilot.md
+++ b/src/pages/docs/test-management/qi-home/automation/agentic-learning/run-automated-test-case-with-copilot.md
@@ -36,7 +36,7 @@ This is the final step in the Agentic Learning workflow. The test case moves fro
> ## **Prerequisites**
>
> Before you begin, ensure that:
-> - Agentic Learning has completed and automated steps have been generated. See [Learn Test Case Live (Cloud)](https://testsigma.com/docs/arcus/qi-home/automation/agentic-learning/learn-test-case-live-cloud/) or [Learn Test Case Live (Local)](https://testsigma.com/docs/arcus/qi-home/automation/agentic-learning/learn-test-case-live-local/).
+> - Agentic Learning has completed and automated steps have been generated. See [Learn Test Case Live (Cloud)](https://testsigma.com/docs/test-management/qi-home/automation/agentic-learning/learn-test-case-live-cloud/) or [Learn Test Case Live (Local)](https://testsigma.com/docs/test-management/qi-home/automation/agentic-learning/learn-test-case-live-local/).
---
@@ -56,7 +56,7 @@ This is the final step in the Agentic Learning workflow. The test case moves fro
-For the full Copilot execution experience — including controls, step switching, and saving results — see [Execute Test Case in Cloud](https://testsigma.com/docs/arcus/qi-home/automation/copilot/execute-test-case-in-cloud/).
+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/).
---
diff --git a/src/pages/docs/arcus/qi-home/automation/copilot/execute-test-case-in-cloud.md b/src/pages/docs/test-management/qi-home/automation/copilot/execute-test-case-in-cloud.md
similarity index 93%
rename from src/pages/docs/arcus/qi-home/automation/copilot/execute-test-case-in-cloud.md
rename to src/pages/docs/test-management/qi-home/automation/copilot/execute-test-case-in-cloud.md
index e5967ce..52133e5 100644
--- a/src/pages/docs/arcus/qi-home/automation/copilot/execute-test-case-in-cloud.md
+++ b/src/pages/docs/test-management/qi-home/automation/copilot/execute-test-case-in-cloud.md
@@ -37,7 +37,7 @@ Copilot opens a cloud browser on Testsigma Lab and executes your test case steps
> ## **Prerequisites**
>
> Before you begin, ensure that:
-> - You have a test case with automated steps saved in your library. Automated steps are required for Copilot execution. See [Learn Test Case Live (Cloud)](https://testsigma.com/docs/arcus/qi-home/automation/agentic-learning/learn-test-case-live-cloud/).
+> - You have a test case with automated steps saved in your library. Automated steps are required for Copilot execution. See [Learn Test Case Live (Cloud)](https://testsigma.com/docs/test-management/qi-home/automation/agentic-learning/learn-test-case-live-cloud/).
> - Your application is accessible from a cloud environment.
---
@@ -80,7 +80,7 @@ When the browser is ready, the Copilot panel opens alongside it. Steps execute i
-For the full list of controls available during execution, see [Execution Controls in Copilot](https://testsigma.com/docs/arcus/qi-home/automation/copilot/execution-controls-in-copilot/).
+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/).
---
diff --git a/src/pages/docs/arcus/qi-home/automation/copilot/execute-test-case-in-local.md b/src/pages/docs/test-management/qi-home/automation/copilot/execute-test-case-in-local.md
similarity index 94%
rename from src/pages/docs/arcus/qi-home/automation/copilot/execute-test-case-in-local.md
rename to src/pages/docs/test-management/qi-home/automation/copilot/execute-test-case-in-local.md
index ca9bf4e..6d7bb09 100644
--- a/src/pages/docs/arcus/qi-home/automation/copilot/execute-test-case-in-local.md
+++ b/src/pages/docs/test-management/qi-home/automation/copilot/execute-test-case-in-local.md
@@ -67,7 +67,7 @@ Local execution requires Testsigma Terminal to be running on your desktop.
If Testsigma Terminal is not running, a prompt appears. Start Terminal and return to launch the session.
-The Copilot panel opens in a browser on your machine. The execution flow is the same as Cloud. See [Execution Controls in Copilot](https://testsigma.com/docs/arcus/qi-home/automation/copilot/execution-controls-in-copilot/).
+The Copilot panel opens in a browser on your machine. The execution flow is the same as Cloud. See [Execution Controls in Copilot](https://testsigma.com/docs/test-management/qi-home/automation/copilot/execution-controls-in-copilot/).
---
@@ -116,7 +116,7 @@ The iOS flow uses the same Run with Copilot dialog as Android Local.
## **Complete the Session**
-The completion flow for Local is the same as Cloud. When execution finishes, save your results and end the session. See [Execute Test Case in Cloud](https://testsigma.com/docs/arcus/qi-home/automation/copilot/execute-test-case-in-cloud/) for the save and end steps.
+The completion flow for Local is the same as Cloud. When execution finishes, save your results and end the session. See [Execute Test Case in Cloud](https://testsigma.com/docs/test-management/qi-home/automation/copilot/execute-test-case-in-cloud/) for the save and end steps.
[[info | **NOTE**:]]
| For Local execution, there is no cloud VM to release. The session simply closes when you end it.
diff --git a/src/pages/docs/arcus/qi-home/automation/copilot/execution-controls-in-copilot.md b/src/pages/docs/test-management/qi-home/automation/copilot/execution-controls-in-copilot.md
similarity index 100%
rename from src/pages/docs/arcus/qi-home/automation/copilot/execution-controls-in-copilot.md
rename to src/pages/docs/test-management/qi-home/automation/copilot/execution-controls-in-copilot.md
diff --git a/src/pages/docs/arcus/qi-home/plugins/connect-claude-code.md b/src/pages/docs/test-management/qi-home/context-mapping/connect-claude-code.md
similarity index 51%
rename from src/pages/docs/arcus/qi-home/plugins/connect-claude-code.md
rename to src/pages/docs/test-management/qi-home/context-mapping/connect-claude-code.md
index 36270da..b1ed915 100644
--- a/src/pages/docs/arcus/qi-home/plugins/connect-claude-code.md
+++ b/src/pages/docs/test-management/qi-home/context-mapping/connect-claude-code.md
@@ -10,12 +10,6 @@ warning: false
contextual_links:
- type: section
name: 'Contents'
- - type: link
- name: 'Overview'
- url: '#overview'
- - type: link
- name: 'Why Arcus'
- url: '#why-arcus'
- type: link
name: 'Prerequisites'
url: '#prerequisites'
@@ -25,18 +19,12 @@ contextual_links:
- type: link
name: 'Log In and Connect Your Project'
url: '#log-in-and-connect-your-project'
- - type: link
- name: 'How the Quality Intelligence Loop Works'
- url: '#how-the-quality-intelligence-loop-works'
- type: link
name: 'Map Your Context to a Sprint'
url: '#map-your-context-to-a-sprint'
- type: link
name: 'Push Your Context'
url: '#push-your-context'
- - type: link
- name: "Who It's For"
- url: '#who-its-for'
- type: link
name: 'Commands Reference'
url: '#commands-reference'
@@ -47,28 +35,9 @@ contextual_links:
**Install the Arcus plugin for Claude Code so that your coding context is captured and sent to QI Home for test generation.**
-The plugin hooks into each stage of a Claude Code session and captures it as structured events: your prompts, the tools Claude runs, the files it reads and writes, and subagent boundaries. When you are done, you push the captured context to QI Home with a single command. QA maps the context to the right sprint, and the Generator Agent creates test cases from your development activity.
+The plugin hooks into each stage of a Claude Code session and captures it as structured events: your prompts, the tools Claude runs, the files it reads and writes, and subagent boundaries. When you are done, you push the captured context to QI Home with a single command. QA maps the context to the right sprint, and Atto generates test cases from your development activity.
----
-
-## **Overview**
-
-At a glance, Arcus:
-
-* **Generates test cases from what you actually built**, with no manual authoring.
-* **Finds the gaps** between what changed and what's tested, with a reason for each.
-* **Plans and runs** those tests across Smoke, Feature, Regression, and Deep Regression suites.
-* **Decides with a single Release Readiness score** and a GO / CONDITIONAL GO / NO-GO verdict.
-
----
-
-## **Why Arcus**
-
-AI coding agents have made it trivial to ship large changes fast. The bottleneck has moved: it's no longer writing the code, it's trusting it. Teams using Claude Code routinely merge features, refactors, and fixes faster than their QA process can keep up, and the gap between "the code is written" and "we know it works" keeps widening.
-
-The traditional answer, writing tests by hand after the fact, is slow, always behind, and never tells you with confidence how much of what you just built is actually covered.
-
-Arcus closes that gap by treating your Claude Code session as the source of truth for what changed. It captures the session automatically, turns it into tests you review rather than write, keeps a live map of what's covered, and rolls everything up into an evidence-backed release signal.
+For how mapped context becomes test cases, coverage, and a release signal, see [Overview: Developer Context Mapping](https://testsigma.com/docs/test-management/qi-home/context-mapping/).
---
@@ -111,47 +80,6 @@ claude plugin install arcus@testsigma
---
-## **How the Quality Intelligence Loop Works**
-
-Once you push a session, Arcus runs that context through the Quality Intelligence loop: a continuous cycle that keeps your tests and your release signal in sync with the code.
-
-**1. Generate**
-
-The **Generator Agent** reads the captured session, code changes, the prompts you gave Claude, the tools it ran, and drafts test cases for the behavior you actually built. You review each one and accept, edit, or reject it; accepted cases join your test suite. Nothing is auto-merged behind your back.
-
-**2. Find gaps**
-
-The **Coverage Agent** answers the question manual QA can never keep up with: what did we change that we haven't tested yet? It re-runs whenever context changes, a new Claude Code session or a pull request, or whenever you accept a case, and surfaces untested areas with a reason for each gap.
-
-**3. Plan and execute**
-
-Accepted cases roll up into auto-generated test plans, nested by scope:
-
-| Plan | Scope |
-|------|-------|
-| Smoke | Critical-path sanity checks, fast feedback |
-| Feature | Cases tied to the current feature or session |
-| Regression | Existing behavior that shouldn't have broken |
-| Deep Regression | Broad, exhaustive run across the product |
-
-The **Runner Agent** executes these plans, automated runs against your configured machines and environments, or manual runs for cases that still need a human. See [Test Plans](https://testsigma.com/docs/arcus/qi-home/test-plans/) for how the nested plan hierarchy works.
-
-**4. Measure and decide**
-
-Execution results feed the Quality Intelligence metrics, which build on each other up to a single verdict:
-
-| Metric | Question It Answers |
-|--------|----------------------|
-| Coverage | Of what should be tested, how much is approved and tested? |
-| Pass Rate | Of the tests that ran, how many passed? |
-| Confidence | How trustworthy are the results? |
-| Release Readiness | On a 0 to 100 scale, how shippable is this sprint? |
-| Release Gate | The verdict: GO / CONDITIONAL GO / NO-GO |
-
-See [Quality Intelligence Metrics](https://testsigma.com/docs/arcus/qi-home/quality-intelligence-metrics/) for the full formulas and thresholds behind each metric.
-
----
-
## **Map Your Context to a Sprint**
Run **/arcus:map <ticket-key>** at any point before pushing to link your context to a sprint story. Replace **<ticket-key>** with the Jira ticket ID for the work you are doing.
@@ -163,7 +91,7 @@ Run **/arcus:map <ticket-key>** at any point before pushing to link your c
Running **/arcus:map** before pushing means your context arrives in QI Home already mapped to the correct sprint, and the test cases generated from it trace back to that ticket. QA does not need to route it manually from Unmapped Context.
[[info | **NOTE**:]]
-| You can push without mapping. The context lands in Unmapped Context and waits there with its generated tests until you resolve it, either to a sprint or to an Ad-Hoc session. See [Map Developer Context](https://testsigma.com/docs/arcus/qi-home/plugins/map-developer-context/).
+| You can push without mapping. The context lands in Unmapped Context and waits there with its generated tests until you resolve it, either to a sprint or to an Ad-Hoc session. See [Map Developer Context](https://testsigma.com/docs/test-management/qi-home/context-mapping/map-developer-context/).
---
@@ -175,14 +103,6 @@ The context appears in QI Home under **Unmapped Context** (if you did not run **
---
-## **Who It's For**
-
-* **Developers** shipping with Claude Code who want their changes tested without breaking flow to write tests by hand.
-* **QA and test engineers** who want generated cases to review and refine, plus a coverage map that updates itself instead of a stale spreadsheet.
-* **Engineering leads and release managers** who need an objective, evidence-backed answer to "is this sprint safe to ship?" rather than a status-meeting guess.
-
----
-
## **Commands Reference**
| Command | What it does |
@@ -200,9 +120,9 @@ The context appears in QI Home under **Unmapped Context** (if you did not run **
## **If You Also Use GitHub**
-If your team has the Arcus GitHub App installed and you raise a pull request for the same work you captured in this context, Arcus connects the two automatically:
+If your team has the Arcus GitHub App installed and you raise a pull request for the same work you captured in this context, Atto connects the two automatically:
-* **Context still unmapped**: Arcus converts it into a GitHub context. The Claude Code context and the pull request are unified as a single entry in Unmapped Context.
+* **Context still unmapped**: Atto converts it into a GitHub context. The Claude Code context and the pull request are unified as a single entry in Unmapped Context.
* **Context already mapped**: The pull request is auto-mapped to the same sprint or Ad-Hoc session. No further action is needed.
---
diff --git a/src/pages/docs/test-management/qi-home/context-mapping/connect-codex.md b/src/pages/docs/test-management/qi-home/context-mapping/connect-codex.md
new file mode 100644
index 0000000..73f0a99
--- /dev/null
+++ b/src/pages/docs/test-management/qi-home/context-mapping/connect-codex.md
@@ -0,0 +1,117 @@
+---
+title: 'Connect Codex'
+page_title: 'Connect Codex'
+metadesc: 'How to install and connect the Arcus plugin for Codex so your coding context is captured and sent to QI Home for test generation.'
+description: 'How to install and connect the Arcus plugin for Codex so your coding context is captured and sent to QI Home for test generation.'
+noindex: false
+order: 13.45
+page_id: 'qi-home-connect-codex'
+warning: false
+contextual_links:
+ - type: section
+ name: 'Contents'
+ - type: link
+ name: 'Prerequisites'
+ url: '#prerequisites'
+ - type: link
+ name: 'Install the Plugin'
+ url: '#install-the-plugin'
+ - type: link
+ name: 'Log In and Connect Your Project'
+ url: '#log-in-and-connect-your-project'
+ - type: link
+ name: 'Map Your Context to a Sprint'
+ url: '#map-your-context-to-a-sprint'
+ - type: link
+ name: 'Push Your Context'
+ url: '#push-your-context'
+ - type: link
+ name: 'Commands Reference'
+ url: '#commands-reference'
+ - type: link
+ name: 'If You Also Use GitHub'
+ url: '#if-you-also-use-github'
+---
+
+**Install the Arcus plugin for Codex so that your coding context is captured and sent to QI Home for test generation.**
+
+When the plugin is installed and connected to a project, Atto captures your prompts, tool calls, and file changes as you work. When you are done, you push the context to QI Home with a single command. QA maps the context to the right sprint, and Atto generates test cases based on your development activity.
+
+---
+
+> ## **Prerequisites**
+>
+> Before you begin, ensure that:
+> * Codex is installed.
+> * You have an active project in Arcus by Testsigma.
+
+---
+
+## **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.
+
+---
+
+## **Log In and Connect Your Project**
+
+1. In Codex, run **/arcus:login**.
+
+2. Complete the login flow in the browser. Return to Codex when prompted.
+
+3. Run **/arcus:project <project-id>** to connect the plugin to your Arcus project. Replace **<project-id>** with your project ID from **Arcus > Settings > Project**.
+
+4. Start coding. The plugin begins capturing your context in the background.
+
+[[info | **NOTE**:]]
+| No data is sent to Arcus until you run **/arcus:push**. Logging in and setting your project does not start any upload.
+
+---
+
+## **Map Your Context to a Sprint**
+
+Run **/arcus:map <ticket-key>** at any point before pushing to link your context to a sprint story.
+
+```
+/arcus:map PROJ-123
+```
+
+Running **/arcus:map** before pushing means your context arrives in QI Home already mapped to the correct sprint. QA does not need to route it manually from Unmapped Context.
+
+[[info | **NOTE**:]]
+| You can push without mapping. The context lands in Unmapped Context and QA maps it from there. See [Map Developer Context](https://testsigma.com/docs/test-management/qi-home/context-mapping/map-developer-context/).
+
+---
+
+## **Push Your Context**
+
+1. When you are done, run **/arcus:push** to upload the captured context to QI Home.
+
+The context appears in QI Home under **Unmapped Context** (if you did not run **/arcus:map**) or under the mapped sprint (if you did).
+
+---
+
+## **Commands Reference**
+
+| Command | What it does |
+|---------|-------------|
+| /arcus:help | Lists every Arcus command with a short explanation of what it does and how to use it |
+| /arcus:login | Signs you in to Arcus so it can capture your sessions and use them for test generation |
+| /arcus:logout | Signs you out and deletes the Arcus credentials stored locally on your machine |
+| /arcus:project
| Shows your Arcus projects and sets one as the active project |
+| /arcus:map | Links a ticket key to the current context so it routes to the right sprint |
+| /arcus:test | Generates end-to-end tests for the current repository, validates them, and offers to run them |
+| /arcus:testsigma-tests | Authors new end-to-end tests, saves them under tests/, validates them offline, and offers to run them |
+| /arcus:push | Uploads the test cases captured in this session to Arcus, assigned to a sprint or left unmapped |
+
+---
+
+## **If You Also Use GitHub**
+
+If your team has the Arcus GitHub App installed and you raise a pull request for the same work you captured in this context, Atto connects the two automatically:
+
+* **Context still unmapped**: Atto converts it into a GitHub context. The Codex context and the pull request are unified as a single entry in Unmapped Context.
+* **Context already mapped**: The pull request is auto-mapped to the same sprint or Ad-Hoc session. No further action is needed.
+
+---
diff --git a/src/pages/docs/test-management/qi-home/context-mapping/connect-cursor.md b/src/pages/docs/test-management/qi-home/context-mapping/connect-cursor.md
new file mode 100644
index 0000000..1c2f865
--- /dev/null
+++ b/src/pages/docs/test-management/qi-home/context-mapping/connect-cursor.md
@@ -0,0 +1,116 @@
+---
+title: 'Connect Cursor'
+page_title: 'Connect Cursor'
+metadesc: 'How to install and connect the Arcus plugin for Cursor so your coding context is captured and sent to QI Home for test generation.'
+description: 'How to install and connect the Arcus plugin for Cursor so your coding context is captured and sent to QI Home for test generation.'
+noindex: false
+order: 13.43
+page_id: 'qi-home-connect-cursor'
+warning: false
+contextual_links:
+ - type: section
+ name: 'Contents'
+ - type: link
+ name: 'Prerequisites'
+ url: '#prerequisites'
+ - type: link
+ name: 'Install the Plugin'
+ url: '#install-the-plugin'
+ - type: link
+ name: 'Log In and Connect Your Project'
+ url: '#log-in-and-connect-your-project'
+ - type: link
+ name: 'Map Your Context to a Sprint'
+ url: '#map-your-context-to-a-sprint'
+ - type: link
+ name: 'Push Your Context'
+ url: '#push-your-context'
+ - type: link
+ name: 'Commands Reference'
+ url: '#commands-reference'
+ - type: link
+ name: 'If You Also Use GitHub'
+ url: '#if-you-also-use-github'
+---
+
+**Install the Arcus plugin for Cursor so that your coding context is captured and sent to QI Home for test generation.**
+
+When the plugin is installed and connected to a project, Atto captures your prompts, tool calls, and file changes as you work. When you are done, you push the context to QI Home with a single command. QA maps the context to the right sprint, and Atto generates test cases based on your development activity.
+
+---
+
+> ## **Prerequisites**
+>
+> Before you begin, ensure that:
+> * Cursor is installed.
+> * You have an active project in Arcus by Testsigma.
+
+---
+
+## **Install the Plugin**
+
+The install Arcus plugin from Cursor marketplace.
+
+---
+
+## **Log In and Connect Your Project**
+
+1. In Cursor, run **/arcus:login**.
+
+2. Complete the login flow in the browser. Return to Cursor when prompted.
+
+3. Run **/arcus:project <project-id>** to connect the plugin to your Arcus project. Replace **<project-id>** with your project ID from **Arcus > Settings > Project**.
+
+4. Start coding. The plugin begins capturing your context in the background.
+
+[[info | **NOTE**:]]
+| No data is sent to Arcus until you run **/arcus:push**. Logging in and setting your project does not start any upload.
+
+---
+
+## **Map Your Context to a Sprint**
+
+Run **/arcus:map <ticket-key>** at any point before pushing to link your context to a sprint story.
+
+```
+/arcus:map PROJ-123
+```
+
+Running **/arcus:map** before pushing means your context arrives in QI Home already mapped to the correct sprint. QA does not need to route it manually from Unmapped Context.
+
+[[info | **NOTE**:]]
+| You can push without mapping. The context lands in Unmapped Context and QA maps it from there. See [Map Developer Context](https://testsigma.com/docs/test-management/qi-home/context-mapping/map-developer-context/).
+
+---
+
+## **Push Your Context**
+
+1. When you are done, run **/arcus:push** to upload the captured context to QI Home.
+
+The context appears in QI Home under **Unmapped Context** (if you did not run **/arcus:map**) or under the mapped sprint (if you did).
+
+---
+
+## **Commands Reference**
+
+| Command | What it does |
+|---------|-------------|
+| /arcus:help | Lists every Arcus command with a short explanation of what it does and how to use it |
+| /arcus:login | Signs you in to Arcus so it can capture your sessions and use them for test generation |
+| /arcus:logout | Signs you out and deletes the Arcus credentials stored locally on your machine |
+| /arcus:project | Shows your Arcus projects and sets one as the active project |
+| /arcus:map | Links a ticket key to the current context so it routes to the right sprint |
+| /arcus:test | Generates end-to-end tests for the current repository, validates them, and offers to run them |
+| /arcus:testsigma-tests | Authors new end-to-end tests, saves them under tests/, validates them offline, and offers to run them |
+| /arcus:push | Uploads the test cases captured in this session to Arcus, assigned to a sprint or left unmapped |
+
+---
+
+## **If You Also Use GitHub**
+
+If your team has the Arcus GitHub App installed and you raise a pull request for the same work you captured in this context, Atto connects the two automatically:
+
+* **Context still unmapped**: Atto converts it into a GitHub context. The Cursor context and the pull request are unified as a single entry in Unmapped Context.
+* **Context already mapped**: The pull request is auto-mapped to the same sprint or Ad-Hoc session. No further action is needed.
+
+---
diff --git a/src/pages/docs/test-management/qi-home/context-mapping/connect-github-copilot.md b/src/pages/docs/test-management/qi-home/context-mapping/connect-github-copilot.md
new file mode 100644
index 0000000..9018085
--- /dev/null
+++ b/src/pages/docs/test-management/qi-home/context-mapping/connect-github-copilot.md
@@ -0,0 +1,120 @@
+---
+title: 'Connect GitHub Copilot'
+page_title: 'Connect GitHub Copilot'
+metadesc: 'How to install and connect the Arcus plugin for GitHub Copilot so your coding context is captured and sent to QI Home for test generation.'
+description: 'How to install and connect the Arcus plugin for GitHub Copilot so your coding context is captured and sent to QI Home for test generation.'
+noindex: false
+order: 13.44
+page_id: 'qi-home-connect-github-copilot'
+warning: false
+contextual_links:
+ - type: section
+ name: 'Contents'
+ - type: link
+ name: 'Prerequisites'
+ url: '#prerequisites'
+ - type: link
+ name: 'Install the Plugin'
+ url: '#install-the-plugin'
+ - type: link
+ name: 'Log In and Connect Your Project'
+ url: '#log-in-and-connect-your-project'
+ - type: link
+ name: 'Map Your Context to a Sprint'
+ url: '#map-your-context-to-a-sprint'
+ - type: link
+ name: 'Push Your Context'
+ url: '#push-your-context'
+ - type: link
+ name: 'Commands Reference'
+ url: '#commands-reference'
+ - type: link
+ name: 'If You Also Use GitHub'
+ url: '#if-you-also-use-github'
+---
+
+**Install the Arcus plugin for GitHub Copilot so that your coding context is captured and sent to QI Home for test generation.**
+
+When the plugin is installed and connected to a project, Atto captures your prompts, tool calls, and file changes as you work. When you are done, you push the context to QI Home with a single command. QA maps the context to the right sprint, and Atto generates test cases based on your development activity.
+
+[[info | **NOTE**:]]
+| This doc refers to the GitHub Copilot CLI plugin for Arcus, not Testsigma Copilot (the test execution feature). They are separate tools.
+
+---
+
+> ## **Prerequisites**
+>
+> Before you begin, ensure that:
+> * GitHub Copilot is installed.
+> * You have an active project in Arcus by Testsigma.
+
+---
+
+## **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.
+
+---
+
+## **Log In and Connect Your Project**
+
+1. In GitHub Copilot, run **/arcus:login**.
+
+2. Complete the login flow in the browser. Return to GitHub Copilot when prompted.
+
+3. Run **/arcus:project <project-id>** to connect the plugin to your Arcus project. Replace **<project-id>** with your project ID from **Arcus > Settings > Project**.
+
+4. Start coding. The plugin begins capturing your context in the background.
+
+[[info | **NOTE**:]]
+| No data is sent to Arcus until you run **/arcus:push**. Logging in and setting your project does not start any upload.
+
+---
+
+## **Map Your Context to a Sprint**
+
+Run **/arcus:map <ticket-key>** at any point before pushing to link your context to a sprint story.
+
+```
+/arcus:map PROJ-123
+```
+
+Running **/arcus:map** before pushing means your context arrives in QI Home already mapped to the correct sprint. QA does not need to route it manually from Unmapped Context.
+
+[[info | **NOTE**:]]
+| You can push without mapping. The context lands in Unmapped Context and QA maps it from there. See [Map Developer Context](https://testsigma.com/docs/test-management/qi-home/context-mapping/map-developer-context/).
+
+---
+
+## **Push Your Context**
+
+1. When you are done, run **/arcus:push** to upload the captured context to QI Home.
+
+The context appears in QI Home under **Unmapped Context** (if you did not run **/arcus:map**) or under the mapped sprint (if you did).
+
+---
+
+## **Commands Reference**
+
+| Command | What it does |
+|---------|-------------|
+| /arcus:help | Lists every Arcus command with a short explanation of what it does and how to use it |
+| /arcus:login | Signs you in to Arcus so it can capture your sessions and use them for test generation |
+| /arcus:logout | Signs you out and deletes the Arcus credentials stored locally on your machine |
+| /arcus:project | Shows your Arcus projects and sets one as the active project |
+| /arcus:map | Links a ticket key to the current context so it routes to the right sprint |
+| /arcus:test | Generates end-to-end tests for the current repository, validates them, and offers to run them |
+| /arcus:testsigma-tests | Authors new end-to-end tests, saves them under tests/, validates them offline, and offers to run them |
+| /arcus:push | Uploads the test cases captured in this session to Arcus, assigned to a sprint or left unmapped |
+
+---
+
+## **If You Also Use GitHub**
+
+If your team has the Arcus GitHub App installed and you raise a pull request for the same work you captured in this context, Atto connects the two automatically:
+
+* **Context still unmapped**: Atto converts it into a GitHub context. The GitHub Copilot context and the pull request are unified as a single entry in Unmapped Context.
+* **Context already mapped**: The pull request is auto-mapped to the same sprint or Ad-Hoc session. No further action is needed.
+
+---
diff --git a/src/pages/docs/arcus/qi-home/plugins/connect-github.md b/src/pages/docs/test-management/qi-home/context-mapping/connect-github.md
similarity index 84%
rename from src/pages/docs/arcus/qi-home/plugins/connect-github.md
rename to src/pages/docs/test-management/qi-home/context-mapping/connect-github.md
index 1444ae9..7eb4452 100644
--- a/src/pages/docs/arcus/qi-home/plugins/connect-github.md
+++ b/src/pages/docs/test-management/qi-home/context-mapping/connect-github.md
@@ -29,7 +29,7 @@ contextual_links:
**Connect the Arcus GitHub App to your repositories so that every pull request your team raises flows into QI Home for test generation.**
-When the Arcus GitHub App is installed and connected to a project, the Coverage Agent detects every pull request raised in the connected repositories and surfaces it in the Unmapped Context view. QA maps each PR to a sprint or Ad-Hoc session, and the Generator Agent creates test cases based on the code changes. Developers do not change how they work.
+When the Arcus GitHub App is installed and connected to a project, Atto detects every pull request raised in the connected repositories and surfaces it in the Unmapped Context view. QA maps each PR to a sprint or Ad-Hoc session, and Atto generates test cases based on the code changes. Developers do not change how they work.
---
@@ -61,7 +61,7 @@ The GitHub App is now installed. All pull requests raised in the connected repos
## **Connect Jira for Auto-Mapping**
-If your project is connected to Jira, the Coverage Agent can auto-map pull requests to the correct sprint when the PR title or description contains a Jira ticket ID.
+If your project is connected to Jira, Atto can auto-map pull requests to the correct sprint when the PR title or description contains a Jira ticket ID.
1. In Arcus, go to **Settings > Integrations**.
@@ -71,7 +71,7 @@ If your project is connected to Jira, the Coverage Agent can auto-map pull reque
Once Jira is connected, any PR with a ticket ID such as **PROJ-123** in the title or description is routed directly to the sprint that contains that story. The PR does not land in Unmapped Context. QA does not need to map it manually.
[[info | **NOTE**:]]
-| If a PR does not contain a Jira ticket ID, it lands in Unmapped Context regardless of whether Jira is connected. QA maps it manually from there. See [Map GitHub Context](https://testsigma.com/docs/arcus/qi-home/plugins/map-github/).
+| If a PR does not contain a Jira ticket ID, it lands in Unmapped Context regardless of whether Jira is connected. QA maps it manually from there. See [Map GitHub Context](https://testsigma.com/docs/test-management/qi-home/context-mapping/map-github/).
---
@@ -89,7 +89,7 @@ Once Jira is connected, any PR with a ticket ID such as **PROJ-123** in the titl
## **What Happens Next**
-After a PR appears in Unmapped Context, a QA team member maps it to a sprint or Ad-Hoc session. The Generator Agent then creates test cases based on the PR diff.
+After a PR appears in Unmapped Context, a QA team member maps it to a sprint or Ad-Hoc session. Atto then generates test cases based on the PR diff.
If your developers also use a CLI tool (Claude Code, Cursor, GitHub Copilot, or Codex), their context unifies with the PR automatically when it is raised.
diff --git a/src/pages/docs/arcus/qi-home/plugins/map-developer-context.md b/src/pages/docs/test-management/qi-home/context-mapping/map-developer-context.md
similarity index 71%
rename from src/pages/docs/arcus/qi-home/plugins/map-developer-context.md
rename to src/pages/docs/test-management/qi-home/context-mapping/map-developer-context.md
index 4a04dde..9701f07 100644
--- a/src/pages/docs/arcus/qi-home/plugins/map-developer-context.md
+++ b/src/pages/docs/test-management/qi-home/context-mapping/map-developer-context.md
@@ -1,8 +1,8 @@
---
title: 'Map Developer Context'
page_title: 'Map Developer Context'
-metadesc: 'Map Claude Code, Cursor, GitHub Copilot, and Codex context to sprints or Ad-Hoc sessions so the Generator Agent can create or update test cases based on development activity.'
-description: 'Map Claude Code, Cursor, GitHub Copilot, and Codex context to sprints or Ad-Hoc sessions so the Generator Agent can create or update test cases based on development activity.'
+metadesc: 'Map Claude Code, Cursor, GitHub Copilot, and Codex context to sprints or Ad-Hoc sessions so Atto can generate or update test cases based on development activity.'
+description: 'Map Claude Code, Cursor, GitHub Copilot, and Codex context to sprints or Ad-Hoc sessions so Atto can generate or update test cases based on development activity.'
noindex: false
order: 13.47
page_id: 'qi-home-map-developer-context'
@@ -36,11 +36,11 @@ contextual_links:
url: '#view-mapped-context'
---
-**Map Claude Code, Cursor, GitHub Copilot, and Codex context to sprints or Ad-Hoc sessions so the Generator Agent can create or update test cases based on development activity.**
+**Map Claude Code, Cursor, GitHub Copilot, and Codex context to sprints or Ad-Hoc sessions so Atto can generate or update test cases based on development activity.**
-When developers work in Claude Code, Cursor, GitHub Copilot, or Codex with the Arcus plugin installed and push context using `/arcus:push`, the Coverage Agent surfaces it in the **Unmapped Context** view in QI Home. Each context entry includes an AI-generated suggestion for which module and sprint it belongs to. Once mapped, the Generator Agent creates test cases based on the development activity captured in that context.
+When developers work in Claude Code, Cursor, GitHub Copilot, or Codex with the Arcus plugin installed and push context using `/arcus:push`, Atto surfaces it in the **Unmapped Context** view in QI Home. Each context entry includes an AI-generated suggestion for which module and sprint it belongs to. Once mapped, Atto generates test cases based on the development activity captured in that context.
-For plugin setup on the developer side, see [Connect Claude Code](https://testsigma.com/docs/arcus/qi-home/plugins/connect-claude-code/), [Connect Cursor](https://testsigma.com/docs/arcus/qi-home/plugins/connect-cursor/), [Connect GitHub Copilot](https://testsigma.com/docs/arcus/qi-home/plugins/connect-github-copilot/), or [Connect Codex](https://testsigma.com/docs/arcus/qi-home/plugins/connect-codex/).
+For plugin setup on the developer side, see [Connect Claude Code](https://testsigma.com/docs/test-management/qi-home/context-mapping/connect-claude-code/), [Connect Cursor](https://testsigma.com/docs/test-management/qi-home/context-mapping/connect-cursor/), [Connect GitHub Copilot](https://testsigma.com/docs/test-management/qi-home/context-mapping/connect-github-copilot/), or [Connect Codex](https://testsigma.com/docs/test-management/qi-home/context-mapping/connect-codex/).
---
@@ -65,9 +65,9 @@ Each CLI context entry shows:
* **Context title**
* **Author** — the developer whose activity produced this context
* **Service** — the module or service area this context relates to
-* **Tests explored** — areas the Coverage Agent identified in this context
+* **Tests explored** — areas Atto identified in this context
* **Time** the context was pushed
-* **AI Suggestion** — the module and sprint the Coverage Agent recommends
+* **AI Suggestion** — the module and sprint Atto recommends
[[info | **NOTE**:]]
| The mapping flow is identical for Claude Code, Cursor, GitHub Copilot, and Codex context. The steps below apply to all four tools.
@@ -88,7 +88,7 @@ Each CLI context entry shows:
6. Review the **What happens next** message and click **Map**.
-The Generator Agent triggers test generation for the selected sprint.
+Atto triggers test generation for the selected sprint.
---
@@ -124,9 +124,9 @@ If a context entry is not relevant to your test coverage, click **Dismiss**. It
## **When a Developer Also Uses GitHub**
-If your team has GitHub connected and a developer raises a pull request for the same work they captured in CLI context, the Coverage Agent handles the overlap automatically:
+If your team has GitHub connected and a developer raises a pull request for the same work they captured in CLI context, Atto handles the overlap automatically:
-* **Context still unmapped**: The Coverage Agent converts it into a GitHub context. The CLI context and the pull request unify as a single entry. You map it as a GitHub PR, not as separate CLI context.
+* **Context still unmapped**: Atto converts it into a GitHub context. The CLI context and the pull request unify as a single entry. You map it as a GitHub PR, not as separate CLI context.
* **Context already mapped**: The pull request is auto-mapped to the same sprint or Ad-Hoc session. No further action is needed.
diff --git a/src/pages/docs/arcus/qi-home/plugins/map-github.md b/src/pages/docs/test-management/qi-home/context-mapping/map-github.md
similarity index 79%
rename from src/pages/docs/arcus/qi-home/plugins/map-github.md
rename to src/pages/docs/test-management/qi-home/context-mapping/map-github.md
index 4ceabc6..223bea9 100644
--- a/src/pages/docs/arcus/qi-home/plugins/map-github.md
+++ b/src/pages/docs/test-management/qi-home/context-mapping/map-github.md
@@ -1,7 +1,7 @@
---
title: 'Map GitHub Context'
page_title: 'Map GitHub Context'
-metadesc: 'Map GitHub pull requests to sprints or Ad-Hoc sessions so the Generator Agent can create or update test cases based on code changes.'
+metadesc: 'Map GitHub pull requests to sprints or Ad-Hoc sessions so Atto can generate or update test cases based on code changes.'
description: 'Learn how to map GitHub pull requests to sprints or Ad-Hoc sessions for coverage tracking.'
noindex: false
order: 13.46
@@ -30,15 +30,15 @@ contextual_links:
url: '#view-mapped-context'
---
-**Map GitHub pull requests to sprints or Ad-Hoc sessions so the Generator Agent can create or update test cases based on code changes.**
+**Map GitHub pull requests to sprints or Ad-Hoc sessions so Atto can generate or update test cases based on code changes.**
-For GitHub App setup on the developer side, see [Connect GitHub](https://testsigma.com/docs/arcus/qi-home/plugins/connect-github/).
+For GitHub App setup on the developer side, see [Connect GitHub](https://testsigma.com/docs/test-management/qi-home/context-mapping/connect-github/).
---
-When your developers open or update pull requests in GitHub, the Coverage Agent detects them and shows them in the **Unmapped Context** view in QI Home. Each pull request appears with an AI-generated suggestion for which module and sprint it belongs to. You review the suggestion and map it with a few clicks.
+When your developers open or update pull requests in GitHub, Atto detects them and shows them in the **Unmapped Context** view in QI Home. Each pull request appears with an AI-generated suggestion for which module and sprint it belongs to. You review the suggestion and map it with a few clicks.
-Once mapped, the Generator Agent creates new test cases or updates existing ones based on the code changes in that pull request.
+Once mapped, Atto generates new test cases or updates existing ones based on the code changes in that pull request.
---
@@ -65,7 +65,7 @@ Each GitHub PR entry shows:
- **Author**: The developer who opened the PR.
- **Lines changed**: Lines added and removed.
- **Time**: When the PR was opened or last updated.
-- **AI Suggestion**: The module the Coverage Agent recommends mapping this PR to.
+- **AI Suggestion**: The module Atto recommends mapping this PR to.
---
@@ -85,7 +85,7 @@ Each GitHub PR entry shows:
7. Click **Map**.
-The Generator Agent triggers test generation for the selected sprint. New test cases are generated or existing ones are updated based on the PR's changes.
+Atto triggers test generation for the selected sprint. New test cases are generated or existing ones are updated based on the PR's changes.
---
diff --git a/src/pages/docs/arcus/qi-home/plugins/overview.md b/src/pages/docs/test-management/qi-home/context-mapping/overview.md
similarity index 62%
rename from src/pages/docs/arcus/qi-home/plugins/overview.md
rename to src/pages/docs/test-management/qi-home/context-mapping/overview.md
index 496e587..5acc445 100644
--- a/src/pages/docs/arcus/qi-home/plugins/overview.md
+++ b/src/pages/docs/test-management/qi-home/context-mapping/overview.md
@@ -23,8 +23,8 @@ contextual_links:
name: 'The Mapping Model'
url: '#the-mapping-model'
- type: link
- name: 'What Gets Generated After Mapping'
- url: '#what-gets-generated-after-mapping'
+ name: 'What Atto Generates After Mapping'
+ url: '#what-atto-generates-after-mapping'
- type: link
name: 'When CLI Context and a Pull Request Overlap'
url: '#when-cli-context-and-a-pull-request-overlap'
@@ -36,7 +36,7 @@ contextual_links:
url: '#prerequisite'
---
-Developer Context Mapping connects the tools your developers already use to the Quality Intelligence loop in Arcus. When a developer opens a pull request or finishes working in a CLI tool, the Coverage Agent captures that context and surfaces it in QI Home for test generation. Developers keep their existing workflow. QA reviews what arrives and maps it to the right sprint or Ad-Hoc session.
+Developer Context Mapping connects the tools your developers already use to the Quality Intelligence loop in Arcus. When a developer opens a pull request or finishes working in a CLI tool, Atto captures that context and surfaces it in QI Home for test generation. Developers keep their existing workflow. QA reviews what arrives and maps it to the right sprint or Ad-Hoc session.
---
@@ -44,7 +44,7 @@ Developer Context Mapping connects the tools your developers already use to the
AI coding tools let developers write and merge changes faster than tests can be authored by hand. Test coverage trails the code, and there is no direct measure of how much of a recent change has been tested.
-Developer Context Mapping treats the coding session as the record of what changed. The Coverage Agent captures the session and identifies changed areas with no corresponding tests, the Generator Agent creates test cases from it for you to review, and QI Home reports the result through the Quality Intelligence Metrics. Developers continue working in their existing tool, and the test suite is built from the work they have already done rather than reconstructed afterwards.
+Developer Context Mapping treats the coding session as the record of what changed. Atto captures the session, generates test cases from it for you to review, identifies changed areas with no corresponding tests, and reports the result through the Quality Intelligence Metrics. Developers continue working in their existing tool, and the test suite is built from the work they have already done rather than reconstructed afterwards.
---
@@ -52,7 +52,7 @@ Developer Context Mapping treats the coding session as the record of what change
* **Developers** work in their existing CLI tool. The plugin captures context in the background, and they push it when a task is complete.
* **QA and test engineers** review the generated test cases, accept, edit, or reject each one, and map incoming context to the correct sprint or Ad-Hoc session.
-* **Engineering leads and release managers** read the Coverage, Release Readiness, and Release Gate values that result. See [Quality Intelligence Metrics](https://testsigma.com/docs/arcus/qi-home/quality-intelligence-metrics/).
+* **Engineering leads and release managers** read the Coverage, Release Readiness, and Release Gate values that result. See [Quality Intelligence Metrics](https://testsigma.com/docs/test-management/qi-home/quality-intelligence-metrics/).
---
@@ -74,11 +74,11 @@ Every incoming context entry, whether a pull request or captured coding activity
**Unmapped**
-All context lands here first. The Coverage Agent shows an AI-generated suggestion for which sprint and story the context belongs to. You review the suggestion and map it manually, or dismiss it if it is not relevant.
+All context lands here first. Atto shows an AI-generated suggestion for which sprint and story the context belongs to. You review the suggestion and map it manually, or dismiss it if it is not relevant.
**Sprint**
-Context mapped to a sprint contributes to test generation for that sprint. The Generator Agent creates new test cases or updates existing ones based on the context content. The sprint's coverage, pass rate, and release readiness metrics update accordingly.
+Context mapped to a sprint contributes to test generation for that sprint. Atto generates new test cases or updates existing ones based on the context content. The sprint's coverage, pass rate, and release readiness metrics update accordingly.
Context routes to a sprint automatically when:
@@ -91,23 +91,23 @@ Context mapped to an Ad-Hoc session is for work not tied to a sprint, such as ho
---
-## **What Gets Generated After Mapping**
+## **What Atto Generates After Mapping**
-Mapping is the trigger. Once context is assigned to a sprint or Ad-Hoc session:
+Mapping is the trigger. Once context is assigned to a sprint or Ad-Hoc session, Atto produces:
-* The **Generator Agent** creates **test cases** based on the pull request diff or captured context. You review each case and accept, edit, or reject it before it is added to the sprint.
-* The **Coverage Agent** identifies **coverage gaps**, areas of the change with no corresponding tests.
-* The **Runner Agent** organizes **a test plan** into Smoke, Feature, Regression, and Deep Regression suites.
+* **Test cases** based on the pull request diff or captured context. You review each case and accept, edit, or reject it before it is added to the sprint.
+* **Coverage gaps** identifying areas of the change with no corresponding tests.
+* **A test plan** organized into Smoke, Feature, Regression, and Deep Regression suites.
-Execution results from these test plans feed the Quality Intelligence Metrics. See [Quality Intelligence Metrics](https://testsigma.com/docs/arcus/qi-home/quality-intelligence-metrics/) for how Coverage, Pass Rate, Confidence, Release Readiness, and Release Gate are calculated.
+Execution results from these test plans feed the Quality Intelligence Metrics. See [Quality Intelligence Metrics](https://testsigma.com/docs/test-management/qi-home/quality-intelligence-metrics/) for how Coverage, Pass Rate, Confidence, Release Readiness, and Release Gate are calculated.
---
## **When CLI Context and a Pull Request Overlap**
-Developers using a CLI tool often raise a pull request for the same work they captured as context. The Coverage Agent handles this automatically:
+Developers using a CLI tool often raise a pull request for the same work they captured as context. Atto handles this automatically:
-* **Context still unmapped when the PR is raised** — The Coverage Agent converts it into a GitHub context. The CLI context and the pull request are unified as a single entry in Unmapped Context. Its prompt history and code changes are analyzed together with the PR diff.
+* **Context still unmapped when the PR is raised** — Atto converts it into a GitHub context. The CLI context and the pull request are unified as a single entry in Unmapped Context. Its prompt history and code changes are analyzed together with the PR diff.
* **Context already mapped when the PR is raised** — The pull request is auto-mapped to the same sprint or Ad-Hoc session. No further action is needed.
@@ -119,11 +119,11 @@ Developers who run `/arcus:map` early do not need to take any action when they r
| Tool | What it captures | Setup |
|------|-----------------|-------|
-| GitHub | Pull requests from connected repositories | [Connect GitHub](https://testsigma.com/docs/arcus/qi-home/plugins/connect-github/) |
-| Claude Code | Coding context: prompts, tool calls, file changes | [Connect Claude Code](https://testsigma.com/docs/arcus/qi-home/plugins/connect-claude-code/) |
-| Cursor | Coding context: prompts, tool calls, file changes | [Connect Cursor](https://testsigma.com/docs/arcus/qi-home/plugins/connect-cursor/) |
-| GitHub Copilot | Coding context: prompts, tool calls, file changes | [Connect GitHub Copilot](https://testsigma.com/docs/arcus/qi-home/plugins/connect-github-copilot/) |
-| Codex | Coding context: prompts, tool calls, file changes | [Connect Codex](https://testsigma.com/docs/arcus/qi-home/plugins/connect-codex/) |
+| GitHub | Pull requests from connected repositories | [Connect GitHub](https://testsigma.com/docs/test-management/qi-home/context-mapping/connect-github/) |
+| Claude Code | Coding context: prompts, tool calls, file changes | [Connect Claude Code](https://testsigma.com/docs/test-management/qi-home/context-mapping/connect-claude-code/) |
+| Cursor | Coding context: prompts, tool calls, file changes | [Connect Cursor](https://testsigma.com/docs/test-management/qi-home/context-mapping/connect-cursor/) |
+| GitHub Copilot | Coding context: prompts, tool calls, file changes | [Connect GitHub Copilot](https://testsigma.com/docs/test-management/qi-home/context-mapping/connect-github-copilot/) |
+| Codex | Coding context: prompts, tool calls, file changes | [Connect Codex](https://testsigma.com/docs/test-management/qi-home/context-mapping/connect-codex/) |
You can connect any combination of tools. Most teams connect GitHub and at least one CLI tool.
diff --git a/src/pages/docs/arcus/qi-home/coverage-and-gaps.md b/src/pages/docs/test-management/qi-home/coverage-and-gaps.md
similarity index 83%
rename from src/pages/docs/arcus/qi-home/coverage-and-gaps.md
rename to src/pages/docs/test-management/qi-home/coverage-and-gaps.md
index 4354d8d..2139923 100644
--- a/src/pages/docs/arcus/qi-home/coverage-and-gaps.md
+++ b/src/pages/docs/test-management/qi-home/coverage-and-gaps.md
@@ -1,7 +1,7 @@
---
title: 'Coverage and Gaps'
page_title: 'Coverage and Gaps'
-metadesc: 'Track how much of your feature is covered by accepted test cases and where the gaps are. Learn how the Coverage Agent calculates coverage at the session and module level.'
+metadesc: 'Track how much of your feature is covered by accepted test cases and where the gaps are. Learn how Atto calculates coverage at the session and module level.'
description: 'Learn how coverage is calculated and how to review gaps by module in QI Home.'
noindex: false
order: 13.27
@@ -33,7 +33,7 @@ contextual_links:
---
-Coverage tells you what percentage of your generated test cases have been accepted. Gaps are the test cases that have not been accepted yet. The more test cases you accept, the higher your coverage. Both coverage and gaps update in real time as you review test cases, tracked by the Coverage Agent.
+Coverage tells you what percentage of your generated test cases have been accepted. Gaps are the test cases that have not been accepted yet. The more test cases you accept, the higher your coverage. Both coverage and gaps update in real time as you review test cases.
---
@@ -43,7 +43,7 @@ Coverage is calculated using this formula:
**Coverage = Accepted ÷ (Accepted + Pending) × 100**
-For example, if the Generator Agent generated 10 test cases and you have accepted 3, your coverage is 30%. The remaining 7 test cases are gaps.
+For example, if Atto generated 10 test cases and you have accepted 3, your coverage is 30%. The remaining 7 test cases are gaps.
Coverage appears at two levels:
@@ -87,7 +87,7 @@ The Coverage tab shows test cases grouped by module. Each module row shows:
2. Click a gap to open the test case detail view. From there you can accept or reject it.
[[info | **NOTE**:]]
-| Gaps are not failed tests. They are pending test cases that the Generator Agent created but you have not reviewed yet. Accepting a gap removes it from the gaps list and increases your coverage percentage.
+| Gaps are not failed tests. They are pending test cases that Atto generated but you have not reviewed yet. Accepting a gap removes it from the gaps list and increases your coverage percentage.
---
@@ -100,8 +100,8 @@ The session header always shows your current coverage at a glance.
- **Pass Rate, Confidence, and Release Readiness**: These show "Awaiting execution" until test runs are executed.
- **Release Gate**: Shows "**Not Ready**" until the configured thresholds are met.
-For details on all five metrics, see [Quality Intelligence Metrics](https://testsigma.com/docs/arcus/qi-home/quality-intelligence-metrics/).
+For details on all five metrics, see [Quality Intelligence Metrics](https://testsigma.com/docs/test-management/qi-home/quality-intelligence-metrics/).
-To generate test cases for modules with gaps, open the Playground from the session header. See [Use Playground](https://testsigma.com/docs/arcus/qi-home/use-playground/).
+To generate test cases for modules with gaps, open the Playground from the session header. See [Use Playground](https://testsigma.com/docs/test-management/qi-home/use-playground/).
---
diff --git a/src/pages/docs/arcus/qi-home/faqs.md b/src/pages/docs/test-management/qi-home/faqs.md
similarity index 63%
rename from src/pages/docs/arcus/qi-home/faqs.md
rename to src/pages/docs/test-management/qi-home/faqs.md
index 33af113..6ae0435 100644
--- a/src/pages/docs/arcus/qi-home/faqs.md
+++ b/src/pages/docs/test-management/qi-home/faqs.md
@@ -31,65 +31,65 @@ contextual_links:
### **1. What is the difference between Ad-Hoc and Sprints?**
-Both generate test cases using the Generator Agent. The difference is in how generation is triggered and where the context comes from. In Ad-Hoc, you manually attach context sources and click Generate. In Sprints, the Generator Agent detects when a sprint starts in your connected project management tool and offers to generate automatically using the sprint stories and linked artifacts. Everything after generation — reviewing test cases, coverage, test plans, and quality metrics — is the same for both. See the [Overview](https://testsigma.com/docs/arcus/qi-home/overview/).
+Both generate test cases using Atto. The difference is in how generation is triggered and where the context comes from. In Ad-Hoc, you manually attach context sources and click Generate. In Sprints, Atto detects when a sprint starts in your connected project management tool and offers to generate automatically using the sprint stories and linked artifacts. Everything after generation — reviewing test cases, coverage, test plans, and quality metrics — is the same for both. See the [Overview](https://testsigma.com/docs/test-management/qi-home/overview/).
-### **2. Why did generation skip some scenarios or leave scenario outlines empty?**
+### **2. Why did Atto skip some scenarios or leave scenario outlines empty?**
-The Generator Agent creates full test cases for the scenarios it can complete based on your context. For areas where the context was incomplete, or where the Coverage Agent flagged that coverage was needed but the scenario could not be fully expanded, the Generator Agent creates Remaining Scenario Outlines instead. These are stubs that mark areas needing coverage. Open the Playground and describe the missing scenarios to fill them. See [Use Playground](https://testsigma.com/docs/arcus/qi-home/use-playground/).
+Atto generates full test cases for the scenarios it can complete based on your context. For areas where the context was incomplete or where Atto identified coverage was needed but could not fully expand the scenario, it creates Remaining Scenario Outlines. These are stubs that mark areas needing coverage. Open the Playground and describe the missing scenarios to fill them. See [Use Playground](https://testsigma.com/docs/test-management/qi-home/use-playground/).
### **3. I clicked Not Now on a sprint notification. Can I still generate test cases?**
-Yes. Go to **QI Home > Sprints** tab. Find the sprint with **To Do** status and click **Generate Test Cases** next to it. See [Generate Test Cases](https://testsigma.com/docs/arcus/qi-home/sprints/generate-test-cases/).
+Yes. Go to **QI Home > Sprints** tab. Find the sprint with **To Do** status and click **Generate Test Cases** next to it. See [Generate Test Cases](https://testsigma.com/docs/test-management/qi-home/sprints/generate-test-cases/).
### **4. Why is my coverage showing 0%?**
-Coverage reflects accepted test cases, not generated ones. Generated test cases start in Pending status. You need to review them and click Save to Library to accept them. Once you accept test cases, coverage updates in real time. See [Review and Accept Test Cases](https://testsigma.com/docs/arcus/qi-home/review-and-accept-test-cases/).
+Coverage reflects accepted test cases, not generated ones. Generated test cases start in Pending status. You need to review them and click Save to Library to accept them. Once you accept test cases, coverage updates in real time. See [Review and Accept Test Cases](https://testsigma.com/docs/test-management/qi-home/review-and-accept-test-cases/).
### **5. What happens to test cases I do not accept?**
-Unaccepted test cases remain in Pending status and are counted as gaps. They count against your coverage percentage until you either accept or reject them. Rejecting a test case removes it from the gaps count. Leaving it as Pending keeps it as a gap. See [Coverage and Gaps](https://testsigma.com/docs/arcus/qi-home/coverage-and-gaps/).
+Unaccepted test cases remain in Pending status and are counted as gaps. They count against your coverage percentage until you either accept or reject them. Rejecting a test case removes it from the gaps count. Leaving it as Pending keeps it as a gap. See [Coverage and Gaps](https://testsigma.com/docs/test-management/qi-home/coverage-and-gaps/).
-### **6. Can I edit a test case the Generator Agent created?**
+### **6. Can I edit a test case Atto generated?**
Yes. Open the test case from the session detail view or from your library. You can edit the title, steps, preconditions, and expected results directly on the test case page.
### **7. Can I regenerate test cases for a sprint after the initial generation?**
-Yes. Open the Playground from the session header and write a new prompt describing what you want to add or change. The Generator Agent creates additional test cases and adds them to the existing session. You can also add new context sources before generating. See [Use Playground](https://testsigma.com/docs/arcus/qi-home/use-playground/).
+Yes. Open the Playground from the session header and write a new prompt describing what you want to add or change. Atto generates additional test cases and adds them to the existing session. You can also add new context sources before generating. See [Use Playground](https://testsigma.com/docs/test-management/qi-home/use-playground/).
### **8. What is a test library?**
-Your test library is where accepted test cases are stored. When you click Save to Library, you select a folder and QI Home saves the test case there. Saved test cases are available for automation, test plan inclusion, and re-use across sessions.
+Your test library is where accepted test cases are stored. When you click Save to Library, you select a folder and Atto saves the test case there. Saved test cases are available for automation, test plan inclusion, and re-use across sessions.
### **9. Why does the Release Gate show "Not Ready" even though I have accepted test cases?**
-The Release Gate evaluates Release Readiness, which requires test runs to have been executed. Accepting test cases updates Coverage but does not affect Pass Rate, Confidence, or Release Readiness until test runs complete. Execute at least one test plan to activate the remaining metrics. See [Quality Intelligence Metrics](https://testsigma.com/docs/arcus/qi-home/quality-intelligence-metrics/).
+The Release Gate evaluates Release Readiness, which requires test runs to have been executed. Accepting test cases updates Coverage but does not affect Pass Rate, Confidence, or Release Readiness until test runs complete. Execute at least one test plan to activate the remaining metrics. See [Quality Intelligence Metrics](https://testsigma.com/docs/test-management/qi-home/quality-intelligence-metrics/).
### **10. What is the difference between Release Readiness and Release Gate?**
-Release Readiness is a 0 to 100 score that combines Coverage, Pass Rate, and Confidence. Release Gate translates that score into a decision: GO, CONDITIONAL, or NO-GO, based on configurable thresholds. Release Readiness tells you how ready you are. Release Gate tells you whether that readiness meets your project's release standard. See [Quality Intelligence Metrics](https://testsigma.com/docs/arcus/qi-home/quality-intelligence-metrics/).
+Release Readiness is a 0 to 100 score that combines Coverage, Pass Rate, and Confidence. Release Gate translates that score into a decision: GO, CONDITIONAL, or NO-GO, based on configurable thresholds. Release Readiness tells you how ready you are. Release Gate tells you whether that readiness meets your project's release standard. See [Quality Intelligence Metrics](https://testsigma.com/docs/test-management/qi-home/quality-intelligence-metrics/).
### **11. Do I need the Testsigma Terminal for Agentic Learning?**
-Only for Local execution. Cloud execution uses Testsigma Lab and requires nothing on your machine. If you choose Local Devices in the Learn and Automate dialog, Testsigma Terminal must be running on your desktop. See [Learn Test Case Live (Cloud)](https://testsigma.com/docs/arcus/qi-home/automation/agentic-learning/learn-test-case-live-cloud/) and [Learn Test Case Live (Local)](https://testsigma.com/docs/arcus/qi-home/automation/agentic-learning/learn-test-case-live-local/).
+Only for Local execution. Cloud execution uses Testsigma Lab and requires nothing on your machine. If you choose Local Devices in the Learn and Automate dialog, Testsigma Terminal must be running on your desktop. See [Learn Test Case Live (Cloud)](https://testsigma.com/docs/test-management/qi-home/automation/agentic-learning/learn-test-case-live-cloud/) and [Learn Test Case Live (Local)](https://testsigma.com/docs/test-management/qi-home/automation/agentic-learning/learn-test-case-live-local/).
### **12. What happens to the cloud VM when I end a Copilot session?**
-The cloud VM is released and any unsaved changes are lost. Use Save and End to save your results before the VM closes. If you click Dismiss, the VM stays running and continues to consume resources until you end the session. See [Execute Test Case in Cloud](https://testsigma.com/docs/arcus/qi-home/automation/copilot/execute-test-case-in-cloud/).
+The cloud VM is released and any unsaved changes are lost. Use Save and End to save your results before the VM closes. If you click Dismiss, the VM stays running and continues to consume resources until you end the session. See [Execute Test Case in Cloud](https://testsigma.com/docs/test-management/qi-home/automation/copilot/execute-test-case-in-cloud/).
### **13. Can I map a GitHub PR to an Ad-Hoc session instead of a sprint?**
-Yes. In the Map to Module dialog, select Adhoc under Map to, then select an existing Ad-Hoc session or create a new one. See [Map GitHub Context](https://testsigma.com/docs/arcus/qi-home/plugins/map-github/).
+Yes. In the Map to Module dialog, select Adhoc under Map to, then select an existing Ad-Hoc session or create a new one. See [Map GitHub Context](https://testsigma.com/docs/test-management/qi-home/context-mapping/map-github/).
### **14. How do I connect Jira, GitHub, or a CLI tool to my project?**
-Go to **Settings > Integrations** from the left navigation. Each integration has its own connection flow. Jira, Azure DevOps, Linear, ClickUp, and Confluence are used as context sources for test generation. GitHub, Claude Code, Cursor, GitHub Copilot, and Codex are used for Developer Context Mapping. Each has a dedicated setup guide. See [Connect GitHub](https://testsigma.com/docs/arcus/qi-home/plugins/connect-github/), [Connect Claude Code](https://testsigma.com/docs/arcus/qi-home/plugins/connect-claude-code/), [Connect Cursor](https://testsigma.com/docs/arcus/qi-home/plugins/connect-cursor/), [Connect GitHub Copilot](https://testsigma.com/docs/arcus/qi-home/plugins/connect-github-copilot/), or [Connect Codex](https://testsigma.com/docs/arcus/qi-home/plugins/connect-codex/).
+Go to **Settings > Integrations** from the left navigation. Each integration has its own connection flow. Jira, Azure DevOps, Linear, ClickUp, and Confluence are used as context sources for test generation. GitHub, Claude Code, Cursor, GitHub Copilot, and Codex are used for Developer Context Mapping. Each has a dedicated setup guide. See [Connect GitHub](https://testsigma.com/docs/test-management/qi-home/context-mapping/connect-github/), [Connect Claude Code](https://testsigma.com/docs/test-management/qi-home/context-mapping/connect-claude-code/), [Connect Cursor](https://testsigma.com/docs/test-management/qi-home/context-mapping/connect-cursor/), [Connect GitHub Copilot](https://testsigma.com/docs/test-management/qi-home/context-mapping/connect-github-copilot/), or [Connect Codex](https://testsigma.com/docs/test-management/qi-home/context-mapping/connect-codex/).
---
### **15. What CLI tools does Developer Context Mapping support?**
-Developer Context Mapping supports Claude Code, Cursor, GitHub Copilot, and Codex. All four capture coding activity through an Arcus plugin and push it to QI Home as context using the `/arcus:push` command. The mapping flow in QI Home is identical for all four. Context appears in Unmapped Context with a tool-specific badge, and you map it to a sprint or Ad-Hoc session the same way. See [Map Developer Context](https://testsigma.com/docs/arcus/qi-home/plugins/map-developer-context/).
+Developer Context Mapping supports Claude Code, Cursor, GitHub Copilot, and Codex. All four capture coding activity through an Arcus plugin and push it to QI Home as context using the `/arcus:push` command. The mapping flow in QI Home is identical for all four. Context appears in Unmapped Context with a tool-specific badge, and you map it to a sprint or Ad-Hoc session the same way. See [Map Developer Context](https://testsigma.com/docs/test-management/qi-home/context-mapping/map-developer-context/).
---
diff --git a/src/pages/docs/test-management/qi-home/overview.md b/src/pages/docs/test-management/qi-home/overview.md
new file mode 100644
index 0000000..f769ddb
--- /dev/null
+++ b/src/pages/docs/test-management/qi-home/overview.md
@@ -0,0 +1,194 @@
+---
+title: "Overview: QI Home"
+page_title: "Overview of QI Home"
+metadesc: 'QI Home is where Atto generates test cases from your requirements, tracks coverage, builds test plans, and automates test execution in Arcus by Testsigma.'
+description: 'An overview of QI Home, where Atto generates test cases, tracks coverage, builds test plans, and automates test execution.'
+noindex: false
+order: 13.20
+page_id: 'qi-home-overview'
+warning: false
+contextual_links:
+ - type: section
+ name: 'Contents'
+ - type: link
+ name: 'Two Ways to Start Test Generation'
+ url: '#two-ways-to-start-test-generation'
+ - type: link
+ name: 'After Test Cases Are Generated'
+ url: '#after-test-cases-are-generated'
+ - type: link
+ name: 'Automation'
+ url: '#automation'
+ - type: link
+ name: 'Developer Context Mapping'
+ url: '#developer-context-mapping'
+ - type: link
+ name: 'Overview: Developer Context Mapping'
+ url: 'https://testsigma.com/docs/test-management/qi-home/context-mapping/overview/'
+ - type: link
+ name: 'Connect GitHub'
+ url: 'https://testsigma.com/docs/test-management/qi-home/context-mapping/connect-github/'
+ - type: link
+ name: 'Connect Claude Code'
+ url: 'https://testsigma.com/docs/test-management/qi-home/context-mapping/connect-claude-code/'
+ - type: link
+ name: 'Connect Cursor'
+ url: 'https://testsigma.com/docs/test-management/qi-home/context-mapping/connect-cursor/'
+ - type: link
+ name: 'Connect GitHub Copilot'
+ url: 'https://testsigma.com/docs/test-management/qi-home/context-mapping/connect-github-copilot/'
+ - type: link
+ name: 'Connect Codex'
+ url: 'https://testsigma.com/docs/test-management/qi-home/context-mapping/connect-codex/'
+ - type: link
+ name: 'Map GitHub Context'
+ url: 'https://testsigma.com/docs/test-management/qi-home/context-mapping/map-github/'
+ - type: link
+ name: 'Map Developer Context'
+ url: 'https://testsigma.com/docs/test-management/qi-home/context-mapping/map-developer-context/'
+ - type: link
+ name: "What's in This Section"
+ url: '#whats-in-this-section'
+ - type: link
+ name: 'Getting Help'
+ url: '#getting-help'
+---
+
+
+
+**QI Home is where you generate test cases, track coverage, and automate with AI.**
+
+---
+
+QI Home is where Atto, the AI feature in Arcus by Testsigma, generates test cases from your requirements, tracks coverage against your modules, builds test plans, and automates test execution. It also detects developer activity from connected Claude Code, Cursor, GitHub Copilot, and Codex context and GitHub pull requests, so your test coverage stays current with what your team is building.
+
+You do not write test cases from scratch. You give Atto the context it needs, and it generates test cases for you. You review what was generated, accept the cases that are accurate, and save them to your library. Coverage, test plans, and quality metrics update as you go.
+
+There are two ways to start: Ad-Hoc, where you attach context manually and trigger generation yourself, and Sprints, where Atto detects a sprint start and begins generation automatically. Everything after generation works the same for both.
+
+---
+
+## **Two Ways to Start Test Generation**
+
+QI Home gives you two starting points depending on how your team works. The generation trigger is different for each, but the rest of the workflow is identical.
+
+### **Ad-Hoc**
+
+Ad-Hoc lets you generate test cases on demand by attaching your own context sources, without tying them to a sprint. You open a new session, attach context sources, write a prompt, and click Generate. Atto reads what you have provided and generates test cases mapped to your features.
+
+Context sources you can attach include:
+
+- **Jira, Azure DevOps, Linear, or ClickUp** for user stories and requirements (requires the respective integration to be connected)
+- **Confluence** for PRDs and specification documents (requires Confluence integration)
+- **Figma** for UI designs and flows (requires Figma integration)
+- **Files and Documents** such as PDFs, Word docs, or text files
+- **Video Recording** for walkthroughs or recorded user flows
+
+Use Ad-Hoc when:
+
+- You are generating test cases outside a sprint cycle
+- You want to control exactly what context Atto uses
+- You are exploring coverage for a new feature, release, or exploratory session
+
+### **Sprints**
+
+Sprints mode generates test coverage automatically at the start of each sprint, pulling context straight from your linked stories. When a sprint starts in your connected project management tool, Atto detects it and shows a notification. You confirm generation, and Atto pulls in the context linked to the sprint stories, including Figma designs, Confluence pages, PRDs, and relevant pull requests, and begins generating test cases.
+
+Use Sprints when:
+
+- Your team works in agile sprints
+- You want test coverage to start as soon as a sprint kicks off, without manually attaching anything
+- You want Atto to use your Jira, Linear, ClickUp, or Azure DevOps stories as the primary source of truth
+
+---
+
+## **After Test Cases Are Generated**
+
+Whether you use **Ad-Hoc** or **Sprints**, the next steps are the same. You review the test cases Atto generated, accept the ones that are accurate, and save them to your library. Coverage, test plans, and quality metrics update as you go.
+
+[**Review and Accept Test Cases**](https://testsigma.com/docs/test-management/qi-home/review-and-accept-test-cases/) allows you to browse the generated test cases grouped by scenario, view step-by-step details for each case, and accept or reject them individually or in bulk. Test cases you save go into your library. Test cases you do not accept are tracked as gaps.
+
+[**Coverage and Gaps**](https://testsigma.com/docs/test-management/qi-home/coverage-and-gaps/) shows you the coverage percentage per module. Coverage is calculated as accepted test cases divided by accepted plus pending test cases, and rejected cases are excluded. Gaps are pending test cases that have not been accepted yet. They are your signal that certain areas of the application are not yet covered.
+
+[**Test Plans**](https://testsigma.com/docs/test-management/qi-home/test-plans/) are generated automatically by Atto in four types: Smoke, Feature, Regression, and Deep Regression. Each type is a superset of the previous one. Smoke is always included in Feature, Feature in Regression, and Regression in Deep Regression. Plans are ready to run as soon as you have accepted test cases.
+
+[**Quality Intelligence Metrics**](https://testsigma.com/docs/test-management/qi-home/quality-intelligence-metrics/) are five metrics shown in the session header that together tell you how confident you can be in the current build. The metrics are Coverage, Pass Rate, Confidence, Release Readiness, and Release Gate. They update as test cases are accepted and test runs are executed.
+
+---
+
+## **Automation**
+
+Once a test case exists in your library, Atto can automate it without you writing any code or scripts.
+
+**Agentic Learning** opens a browser, either on Testsigma Lab in the cloud or on your local device, and walks through the test case steps on your live application. Atto observes how the application behaves at each step, learns the element interactions, and generates automated steps. You review the output and save it to your library. The test case moves from manual to automated in a few minutes.
+
+**Copilot** takes those automated steps and executes them in a browser with a live panel showing each step as it runs. You can pause the execution, add new steps mid-run, switch between manual and automated steps, and save the results when done. Copilot also works without Agentic Learning for running any test case interactively, which is useful for quick sanity checks or exploratory runs.
+
+---
+
+## **Developer Context Mapping**
+
+Developer Context Mapping keeps your test coverage aligned with what your team is actually building.
+
+When your developers work in Claude Code, Cursor, GitHub Copilot, or Codex, or open pull requests in GitHub, Atto detects that context and surfaces it in the **Unmapped Context** view in QI Home. Each context entry includes an AI-generated suggestion for which module and sprint it belongs to. You review the suggestion and map it with a few clicks. Once mapped, Atto generates new test cases or updates existing ones based on the code changes or development activity captured.
+
+See [Overview: Developer Context Mapping](https://testsigma.com/docs/test-management/qi-home/context-mapping/overview/) for how the Unmapped Context model works, when to use GitHub versus a CLI tool, and what happens when a developer raises a PR for work already captured as CLI context.
+
+---
+
+## **What's in This Section**
+
+**Ad-Hoc**
+
+- [Attach Context Sources](https://testsigma.com/docs/test-management/qi-home/ad-hoc/attach-context-sources/)
+- [Write Effective Prompts](https://testsigma.com/docs/test-management/qi-home/ad-hoc/write-effective-prompts/)
+- [Generate Test Cases](https://testsigma.com/docs/test-management/qi-home/ad-hoc/generate-test-cases/)
+
+**Sprints**
+
+- [Generate Test Cases](https://testsigma.com/docs/test-management/qi-home/sprints/generate-test-cases/)
+
+**Shared Workflows**
+
+- [Use Playground](https://testsigma.com/docs/test-management/qi-home/use-playground/)
+- [Review and Accept Test Cases](https://testsigma.com/docs/test-management/qi-home/review-and-accept-test-cases/)
+- [Coverage and Gaps](https://testsigma.com/docs/test-management/qi-home/coverage-and-gaps/)
+- [Test Plans](https://testsigma.com/docs/test-management/qi-home/test-plans/)
+- [Quality Intelligence Metrics](https://testsigma.com/docs/test-management/qi-home/quality-intelligence-metrics/)
+
+**Automation**
+
+- [Learn Test Case Live (Cloud)](https://testsigma.com/docs/test-management/qi-home/automation/agentic-learning/learn-test-case-live-cloud/)
+- [Learn Test Case Live (Local)](https://testsigma.com/docs/test-management/qi-home/automation/agentic-learning/learn-test-case-live-local/)
+- [Live Learning Controls](https://testsigma.com/docs/test-management/qi-home/automation/agentic-learning/live-learning-controls/)
+- [Run Automated Test Case with Copilot](https://testsigma.com/docs/test-management/qi-home/automation/agentic-learning/run-automated-test-case-with-copilot/)
+- [Execute Test Case in Cloud](https://testsigma.com/docs/test-management/qi-home/automation/copilot/execute-test-case-in-cloud/)
+- [Execute Test Case in Local](https://testsigma.com/docs/test-management/qi-home/automation/copilot/execute-test-case-in-local/)
+- [Execution Controls in Copilot](https://testsigma.com/docs/test-management/qi-home/automation/copilot/execution-controls-in-copilot/)
+
+**Developer Context Mapping**
+
+- [Overview](https://testsigma.com/docs/test-management/qi-home/context-mapping/overview/)
+- [Connect GitHub](https://testsigma.com/docs/test-management/qi-home/context-mapping/connect-github/)
+- [Connect Claude Code](https://testsigma.com/docs/test-management/qi-home/context-mapping/connect-claude-code/)
+- [Connect Cursor](https://testsigma.com/docs/test-management/qi-home/context-mapping/connect-cursor/)
+- [Connect GitHub Copilot](https://testsigma.com/docs/test-management/qi-home/context-mapping/connect-github-copilot/)
+- [Connect Codex](https://testsigma.com/docs/test-management/qi-home/context-mapping/connect-codex/)
+- [Map GitHub Context](https://testsigma.com/docs/test-management/qi-home/context-mapping/map-github/)
+- [Map Developer Context](https://testsigma.com/docs/test-management/qi-home/context-mapping/map-developer-context/)
+
+**Others**
+
+- Best Practices
+- [FAQs](https://testsigma.com/docs/test-management/qi-home/faqs/)
+
+[[info | **NOTE**:]]
+| QI Home requires an active project in Arcus by Testsigma. To attach context from Jira, Azure DevOps, Linear, ClickUp, Confluence, or Figma in Ad-Hoc, you need the respective integration connected to your project. Files, documents, and video recordings can be attached without any external integration. For Sprints, connect your project to a supported project management tool. For Developer Context Mapping, connect your Claude or GitHub account.
+
+---
+
+## **Getting Help**
+
+For questions or support, reach out to the Testsigma team at **support@testsigma.com**.
+
+---
diff --git a/src/pages/docs/arcus/qi-home/quality-intelligence-metrics.md b/src/pages/docs/test-management/qi-home/quality-intelligence-metrics.md
similarity index 91%
rename from src/pages/docs/arcus/qi-home/quality-intelligence-metrics.md
rename to src/pages/docs/test-management/qi-home/quality-intelligence-metrics.md
index cffe30c..7caf417 100644
--- a/src/pages/docs/arcus/qi-home/quality-intelligence-metrics.md
+++ b/src/pages/docs/test-management/qi-home/quality-intelligence-metrics.md
@@ -69,7 +69,7 @@ Pending includes AI-discovered gaps and test cases still in Pending status. Reje
| **Gap Risk** | 60% – 79% | Material untested surface. |
| **Critical Gap** | < 60% | Majority of testing surface unaddressed. |
-See [Coverage and Gaps](https://testsigma.com/docs/arcus/qi-home/coverage-and-gaps/) for the module-level breakdown.
+See [Coverage and Gaps](https://testsigma.com/docs/test-management/qi-home/coverage-and-gaps/) for the module-level breakdown.
---
@@ -103,7 +103,7 @@ Total Weight is the sum of priority weights for all test units in the topmost ge
**When it appears:** Confidence shows "Awaiting execution" until test runs have been executed.
-**How it works in practice:** If the Runner Agent generated a Deep Regression plan but you only ran Smoke, Confidence reflects the gap. The 40 units you did not run are in the denominator but contribute zero to the numerator. The score reports honestly: "you committed to Regression-level validation but validated only Smoke." If you explicitly reject the higher plans and keep only Smoke, the scope adjusts and Confidence can reach 100%.
+**How it works in practice:** If Atto generated a Deep Regression plan but you only ran Smoke, Confidence reflects the gap. The 40 units you did not run are in the denominator but contribute zero to the numerator. The score reports honestly: "you committed to Regression-level validation but validated only Smoke." If you explicitly reject the higher plans and keep only Smoke, the scope adjusts and Confidence can reach 100%.
**Bands:**
@@ -114,7 +114,7 @@ Total Weight is the sum of priority weights for all test units in the topmost ge
| **Low** | < 50% | Significant trust or commitment-fulfillment issues. Pass Rate cannot be relied on. |
[[info | **NOTE**:]]
-| Confidence depends on the nested test plan hierarchy. See [Test Plans](https://testsigma.com/docs/arcus/qi-home/test-plans/) for how the topmost generated and topmost executed plan affect this calculation.
+| Confidence depends on the nested test plan hierarchy. See [Test Plans](https://testsigma.com/docs/test-management/qi-home/test-plans/) for how the topmost generated and topmost executed plan affect this calculation.
---
diff --git a/src/pages/docs/arcus/qi-home/review-and-accept-test-cases.md b/src/pages/docs/test-management/qi-home/review-and-accept-test-cases.md
similarity index 79%
rename from src/pages/docs/arcus/qi-home/review-and-accept-test-cases.md
rename to src/pages/docs/test-management/qi-home/review-and-accept-test-cases.md
index b4ec53a..d6a0277 100644
--- a/src/pages/docs/arcus/qi-home/review-and-accept-test-cases.md
+++ b/src/pages/docs/test-management/qi-home/review-and-accept-test-cases.md
@@ -1,8 +1,8 @@
---
title: 'Review and Accept Test Cases'
page_title: 'Review and Accept Test Cases'
-metadesc: 'Review the test cases the Generator Agent created, accept the ones that look right, and save them to your library. Learn the review workflow for sprints and Ad-Hoc sessions.'
-description: 'Learn how to review, accept or reject, and save Generator Agent test cases to your library.'
+metadesc: 'Review the test cases Atto generated, accept the ones that look right, and save them to your library. Learn the review workflow for sprints and Ad-Hoc sessions.'
+description: 'Learn how to review, accept or reject, and save Atto-generated test cases to your library.'
noindex: false
order: 13.26
page_id: 'qi-home-review-and-accept-test-cases'
@@ -32,11 +32,11 @@ contextual_links:
-**Review the test cases the Generator Agent created, accept the ones that look right, and save them to your library.**
+**Review the test cases Atto generated, accept the ones that look right, and save them to your library.**
---
-After generation completes, the Generator Agent's test cases are in **Pending** status. They are not part of your library yet. Your job is to review them, accept the ones that are accurate and relevant, and save them. Test cases that are not accepted remain as gaps and count against your coverage.
+After generation completes, Atto's test cases are in **Pending** status. They are not part of your library yet. Your job is to review them, accept the ones that are accurate and relevant, and save them. Test cases that are not accepted remain as gaps and count against your coverage.
The review experience is the same whether you generated test cases from a sprint or an Ad-Hoc session.
@@ -114,7 +114,7 @@ When you save a test case, you select the folder where it will be stored.
3. Click **Save**. The test cases are saved and their status changes from **Pending** to **Accepted**.
[[info | **NOTE**:]]
-| The Generator Agent suggests a folder based on the feature taxonomy of your project. You can accept the suggestion or choose a different folder.
+| Atto suggests a folder based on the feature taxonomy of your project. You can accept the suggestion or choose a different folder.
---
@@ -123,6 +123,6 @@ When you save a test case, you select the folder where it will be stored.
- **Rejected** test cases are dismissed and do not count toward coverage.
- **Pending** test cases (not yet reviewed) are treated as gaps. They count against your coverage percentage until they are accepted or rejected.
-Your coverage percentage updates in real time as you accept test cases. See [Coverage and Gaps](https://testsigma.com/docs/arcus/qi-home/coverage-and-gaps/) for how coverage is calculated.
+Your coverage percentage updates in real time as you accept test cases. See [Coverage and Gaps](https://testsigma.com/docs/test-management/qi-home/coverage-and-gaps/) for how coverage is calculated.
---
diff --git a/src/pages/docs/arcus/qi-home/sprints/generate-test-cases.md b/src/pages/docs/test-management/qi-home/sprints/generate-test-cases.md
similarity index 57%
rename from src/pages/docs/arcus/qi-home/sprints/generate-test-cases.md
rename to src/pages/docs/test-management/qi-home/sprints/generate-test-cases.md
index 3325b63..bb5898d 100644
--- a/src/pages/docs/arcus/qi-home/sprints/generate-test-cases.md
+++ b/src/pages/docs/test-management/qi-home/sprints/generate-test-cases.md
@@ -1,7 +1,7 @@
---
title: 'Generate Test Cases'
page_title: 'Generate Test Cases (Sprints)'
-metadesc: 'When a sprint starts, the Generator Agent detects it and creates test cases automatically from the sprint stories and linked artifacts. Learn how sprint detection works.'
+metadesc: 'When a sprint starts, Atto detects it and generates test cases automatically from the sprint stories and linked artifacts. Learn how sprint detection works.'
description: 'Learn how sprint detection triggers automatic test case generation, and how to generate test cases for skipped sprints.'
noindex: false
order: 13.24
@@ -17,8 +17,8 @@ contextual_links:
name: 'Confirm Generation When a Sprint Starts'
url: '#confirm-generation-when-a-sprint-starts'
- type: link
- name: 'What the Generator Agent Uses as Context'
- url: '#what-the-generator-agent-uses-as-context'
+ name: 'What Atto Uses as Context'
+ url: '#what-atto-uses-as-context'
- type: link
name: 'Generate Test Cases for an Unprocessed Sprint'
url: '#generate-test-cases-for-an-unprocessed-sprint'
@@ -32,11 +32,11 @@ contextual_links:
-**When a sprint starts, the Generator Agent detects it and generates test cases automatically.**
+**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, the Generator Agent detects the new sprint and notifies you. You confirm, and it pulls context from the sprint stories and linked artifacts to generate test cases.
+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.
@@ -53,26 +53,26 @@ This article covers how sprint detection works, how to confirm or defer generati
## **Confirm Generation When a Sprint Starts**
-When a sprint starts in your connected project management tool, the Generator Agent automatically detects it and shows a notification.
+When a sprint starts in your connected project management tool, Atto automatically detects it and shows a notification.
1. From the left navigation bar, go to **QI Home**.
2. Select the **Sprints** tab.
-3. When the Generator Agent detects a new sprint, a notification appears: **A new sprint is live. Start creating test cases for it?** The notification shows the sprint name and start date.
+3. 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.
-4. Click **Start Generating Tests** to begin. The Generator Agent moves the sprint to **In Progress** and begins generating test cases.
+4. Click **Start Generating Tests** to begin. Atto moves the sprint to **In Progress** and begins generating test cases.
[[info | **NOTE**:]]
| 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 the Generator Agent Uses as Context**
+## **What Atto Uses as Context**
-The Generator Agent automatically pulls context from the sprint stories and their linked artifacts. You do not need to attach anything manually.
+Atto automatically pulls context from the sprint stories and their linked artifacts. You do not need to attach anything manually.
-Context the Generator Agent uses includes:
+Context Atto uses includes:
- Story titles, descriptions, and acceptance criteria from your project management tool
- Confluence pages linked in sprint stories
@@ -81,29 +81,29 @@ Context the Generator Agent uses includes:
- Relevant pull requests linked to sprint stories
[[info | **NOTE**:]]
-| The Generator Agent 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, it will not be able to use it as context.
+| 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 the Generator Agent missed a sprint notification, you can trigger generation manually.
+If you clicked **Not Now** on a sprint or if Atto missed a sprint notification, you can trigger generation manually.
1. From the left navigation bar, go to **QI Home** and select the **Sprints** tab.
2. In the left sidebar, find the sprint with **To Do** status.
-3. Click **Generate Test Cases** next to the sprint name. The Generator Agent begins generating test cases using the same process as automatic detection.
+3. 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**
-The Generator Agent 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.
+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](https://testsigma.com/docs/arcus/qi-home/ad-hoc/generate-test-cases/) in the Ad-Hoc section for details on what the Generator Agent does during generation and how to read the generation summary.
+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.
---
@@ -113,8 +113,8 @@ When generation completes, the sprint moves to **In Progress** status in the sid
From here you can:
-- Review and accept test cases from the **Tests** tab. See [Review and Accept Test Cases](https://testsigma.com/docs/arcus/qi-home/review-and-accept-test-cases/).
-- Add more context or generate additional test cases by clicking **Open Playground**. See [Use Playground](https://testsigma.com/docs/arcus/qi-home/use-playground/).
-- Track coverage and gaps from the **Coverage** tab. See [Coverage and Gaps](https://testsigma.com/docs/arcus/qi-home/coverage-and-gaps/).
+- Review and accept test cases from the **Tests** tab. See [Review and Accept Test Cases](https://testsigma.com/docs/test-management/qi-home/review-and-accept-test-cases/).
+- Add more context or generate additional test cases by clicking **Open Playground**. See [Use Playground](https://testsigma.com/docs/test-management/qi-home/use-playground/).
+- Track coverage and gaps from the **Coverage** tab. See [Coverage and Gaps](https://testsigma.com/docs/test-management/qi-home/coverage-and-gaps/).
---
diff --git a/src/pages/docs/arcus/qi-home/test-plans.md b/src/pages/docs/test-management/qi-home/test-plans.md
similarity index 71%
rename from src/pages/docs/arcus/qi-home/test-plans.md
rename to src/pages/docs/test-management/qi-home/test-plans.md
index 3e6ca91..ad63f21 100644
--- a/src/pages/docs/arcus/qi-home/test-plans.md
+++ b/src/pages/docs/test-management/qi-home/test-plans.md
@@ -1,8 +1,8 @@
---
title: 'Test Plans'
page_title: 'Test Plans'
-metadesc: 'The Runner Agent automatically generates four nested test plan types for every sprint and Ad-Hoc session: Smoke, Feature, Regression, and Deep Regression. Learn how to review and run them.'
-description: 'Learn how the Runner Agent auto-generates the four test plan types, and how to review, accept, and link them.'
+metadesc: 'Atto automatically generates four nested test plan types for every sprint and Ad-Hoc session: Smoke, Feature, Regression, and Deep Regression. Learn how to review and run them.'
+description: 'Learn how Atto auto-generates the four test plan types, and how to review, accept, and link them.'
noindex: false
order: 13.28
page_id: 'qi-home-test-plans'
@@ -35,25 +35,25 @@ contextual_links:
-**The Runner Agent automatically generates test plans for every sprint and Ad-Hoc session. Review them, understand their scope, and run them when you are ready.**
+**Atto automatically generates test plans for every sprint and Ad-Hoc session. Review them, understand their scope, and run them when you are ready.**
---
-The Runner Agent generates four types of test plans as soon as test cases exist in your session. You do not create or configure them manually. Each plan type covers a different scope of your test cases, and they are always generated as a nested set, meaning the narrowest plan is always a subset of the next broader one.
+Atto generates four types of test plans as soon as test cases exist in your session. You do not create or configure them manually. Each plan type covers a different scope of your test cases, and they are always generated as a nested set, meaning the narrowest plan is always a subset of the next broader one.
---
> ## **Prerequisites**
>
> Before you begin, ensure that:
-> - Test cases have been generated and accepted for the session. See [Review and Accept Test Cases](https://testsigma.com/docs/arcus/qi-home/review-and-accept-test-cases/).
+> - Test cases have been generated and accepted for the session. See [Review and Accept Test Cases](https://testsigma.com/docs/test-management/qi-home/review-and-accept-test-cases/).
> - You are viewing a sprint or Ad-Hoc session in QI Home.
---
## **The Four Plan Types**
-The Runner Agent generates these four test plan types automatically. Each is a superset of the one before it.
+Atto generates these four test plan types automatically. Each is a superset of the one before it.
| Plan Type | Scope |
| :--- | :--- |
@@ -65,7 +65,7 @@ The Runner Agent generates these four test plan types automatically. Each is a s
Smoke is always included in Feature, Feature in Regression, and Regression in Deep Regression. Running Deep Regression validates everything that Smoke, Feature, and Regression would have covered.
[[info | **NOTE**:]]
-| The topmost plan type that the Runner Agent generates defines the scope used to calculate the Confidence metric. The topmost plan type you actually execute provides the pass rate results. If the Runner Agent generates all four types but you only run Smoke, Confidence reflects that the narrowest coverage was validated. See [Quality Intelligence Metrics](https://testsigma.com/docs/arcus/qi-home/quality-intelligence-metrics/).
+| The topmost plan type that Atto generates defines the scope used to calculate the Confidence metric. The topmost plan type you actually execute provides the pass rate results. If Atto generates all four types but you only run Smoke, Confidence reflects that the narrowest coverage was validated. See [Quality Intelligence Metrics](https://testsigma.com/docs/test-management/qi-home/quality-intelligence-metrics/).
---
@@ -103,10 +103,10 @@ Smoke is always included in Feature, Feature in Regression, and Regression in De
## **Machine Configuration Detection**
-The Runner Agent detects the application type from your test cases and suggests a machine configuration for each test plan. The detected types include Web, Android, and iOS.
+Atto detects the application type from your test cases and suggests a machine configuration for each test plan. The detected types include Web, Android, and iOS.
[[info | **NOTE**:]]
-| Machine configuration detection uses the test case steps and context to determine the application type. If your session includes test cases for multiple application types, the Runner Agent may suggest separate configurations for each plan.
+| Machine configuration detection uses the test case steps and context to determine the application type. If your session includes test cases for multiple application types, Atto may suggest separate configurations for each plan.
---
@@ -114,7 +114,7 @@ The Runner Agent detects the application type from your test cases and suggests
Accepting is a single global action. Clicking Accept Plan accepts all four plans at once — Smoke, Feature, Regression, and Deep Regression. You cannot accept individual plan types separately.
-When you accept, the Runner Agent creates the following in your project:
+When you accept, Atto creates the following in your project:
- All four test plans under Plans, each named **[Sprint Name] | [Plan Type] Testing** (for example, **Sprint 2 — Hotel Discovery | Smoke Testing**), with an auto-generated description summarizing the feature areas and scenario count.
- A set of test runs under each plan, one run per feature area or module (for example, **Sprint 2 — Hotel Discovery | Smoke Testing | Amenities, Category Filter, Navigation**, and so on).
@@ -130,7 +130,7 @@ To accept the test plans:
3. Click **Accept Plan**.
-4. The Runner Agent creates all four plans and their test runs in your project.
+4. Atto creates all four plans and their test runs in your project.
5. To reject the test plans, click **Reject**.
@@ -138,7 +138,7 @@ To accept the test plans:
## **Link an Automated Test Plan**
-After accepting the test plans, you can link each plan type to an existing test plan in Testsigma. Linking connects the Runner Agent's generated plan to your automation setup so that automated run results flow back into QI Home.
+After accepting the test plans, you can link each plan type to an existing test plan in Testsigma. Linking connects the Atto-generated plan to your automation setup so that automated run results flow back into Atto.
[[info | **NOTE**:]]
| Linking is done per plan type. You can link the Smoke plan to a Testsigma smoke plan, the Feature plan to a feature plan, and so on.
@@ -160,7 +160,7 @@ After accepting the test plans, you can link each plan type to an existing test
## **Understand Test Runs**
-Each test run represents a set of test cases grouped by feature area or module within a plan. When you accept the test plans, the Runner Agent creates one test run per feature area across all four plan types. These runs appear both inside their respective plan and in the global Test Runs list.
+Each test run represents a set of test cases grouped by feature area or module within a plan. When you accept the test plans, Atto creates one test run per feature area across all four plan types. These runs appear both inside their respective plan and in the global Test Runs list.
Each run in the plan shows the run ID, name, number of tests, scheduled date range, and an overall progress bar.
diff --git a/src/pages/docs/arcus/qi-home/use-playground.md b/src/pages/docs/test-management/qi-home/use-playground.md
similarity index 76%
rename from src/pages/docs/arcus/qi-home/use-playground.md
rename to src/pages/docs/test-management/qi-home/use-playground.md
index c7698cc..278ff6e 100644
--- a/src/pages/docs/arcus/qi-home/use-playground.md
+++ b/src/pages/docs/test-management/qi-home/use-playground.md
@@ -1,8 +1,8 @@
---
title: 'Use Playground'
page_title: 'Use Playground'
-metadesc: 'Open the Playground to add context, generate more test cases, and refine what the Generator Agent produced for any sprint or Ad-Hoc session.'
-description: 'Learn how to use the Playground to add context, generate more test cases, and refine Generator Agent output.'
+metadesc: 'Open the Playground to add context, generate more test cases, and refine what Atto produced for any sprint or Ad-Hoc session.'
+description: 'Learn how to use the Playground to add context, generate more test cases, and refine Atto output.'
noindex: false
order: 13.25
page_id: 'qi-home-use-playground'
@@ -29,11 +29,11 @@ contextual_links:
-**Open the Playground to add context, generate more test cases, and refine what the Generator Agent produced.**
+**Open the Playground to add context, generate more test cases, and refine what Atto produced.**
---
-The Playground is the interactive workspace where you work with the Generator Agent after the initial test case generation. Use it to add context you missed the first time, describe specific flows you want the Generator Agent to cover, fill scenario outlines that are still empty, or trigger an additional round of generation for the same sprint or session.
+The Playground is the interactive workspace where you work with Atto after the initial test case generation. Use it to add context you missed the first time, describe specific flows you want Atto to cover, fill scenario outlines that are still empty, or trigger an additional round of generation for the same sprint or session.
The Playground is available from any sprint or Ad-Hoc session detail view after generation completes.
@@ -66,15 +66,15 @@ If the initial generation missed something or you have new artifacts to share, a
2. Select the items and click **Save**.
-For details on each source type, see [Attach Context Sources](https://testsigma.com/docs/arcus/qi-home/ad-hoc/attach-context-sources/).
+For details on each source type, see [Attach Context Sources](https://testsigma.com/docs/test-management/qi-home/ad-hoc/attach-context-sources/).
---
## **Generate More Test Cases**
-1. Follow the same steps mentioned in the above section, and in the prompt input area, describe the feature or flow you want the Generator Agent to cover.
+1. Follow the same steps mentioned in the above section, and in the prompt input area, describe the feature or flow you want Atto to cover.
-2. Click **Generate with AI**. The Generator Agent creates additional test cases and adds them to the current session.
+2. Click **Generate with AI**. Atto generates additional test cases and adds them to the current session.
---
@@ -89,6 +89,6 @@ The right panel shows all test cases for the current session. Use the filter tab
Select individual test cases, then accept or reject them directly from the Playground.
-For the full review workflow, including saving test cases to your library, see [Review and Accept Test Cases](https://testsigma.com/docs/arcus/qi-home/review-and-accept-test-cases/).
+For the full review workflow, including saving test cases to your library, see [Review and Accept Test Cases](https://testsigma.com/docs/test-management/qi-home/review-and-accept-test-cases/).
---
diff --git a/src/pages/docs/arcus/reports/create-report.md b/src/pages/docs/test-management/reports/create-report.md
similarity index 100%
rename from src/pages/docs/arcus/reports/create-report.md
rename to src/pages/docs/test-management/reports/create-report.md
diff --git a/src/pages/docs/arcus/reports/dashboard-reports.md b/src/pages/docs/test-management/reports/dashboard-reports.md
similarity index 100%
rename from src/pages/docs/arcus/reports/dashboard-reports.md
rename to src/pages/docs/test-management/reports/dashboard-reports.md
diff --git a/src/pages/docs/arcus/reports/requirement-traceability-report.md b/src/pages/docs/test-management/reports/requirement-traceability-report.md
similarity index 100%
rename from src/pages/docs/arcus/reports/requirement-traceability-report.md
rename to src/pages/docs/test-management/reports/requirement-traceability-report.md
diff --git a/src/pages/docs/arcus/reports/view-reports.md b/src/pages/docs/test-management/reports/view-reports.md
similarity index 100%
rename from src/pages/docs/arcus/reports/view-reports.md
rename to src/pages/docs/test-management/reports/view-reports.md
diff --git a/src/pages/docs/arcus/settings/api-keys.md b/src/pages/docs/test-management/settings/api-keys.md
similarity index 100%
rename from src/pages/docs/arcus/settings/api-keys.md
rename to src/pages/docs/test-management/settings/api-keys.md
diff --git a/src/pages/docs/arcus/settings/audit-logs.md b/src/pages/docs/test-management/settings/audit-logs.md
similarity index 100%
rename from src/pages/docs/arcus/settings/audit-logs.md
rename to src/pages/docs/test-management/settings/audit-logs.md
diff --git a/src/pages/docs/arcus/settings/custom-fields.md b/src/pages/docs/test-management/settings/custom-fields.md
similarity index 100%
rename from src/pages/docs/arcus/settings/custom-fields.md
rename to src/pages/docs/test-management/settings/custom-fields.md
diff --git a/src/pages/docs/arcus/settings/labels.md b/src/pages/docs/test-management/settings/labels.md
similarity index 100%
rename from src/pages/docs/arcus/settings/labels.md
rename to src/pages/docs/test-management/settings/labels.md
diff --git a/src/pages/docs/arcus/settings/manage-access.md b/src/pages/docs/test-management/settings/manage-access.md
similarity index 100%
rename from src/pages/docs/arcus/settings/manage-access.md
rename to src/pages/docs/test-management/settings/manage-access.md
diff --git a/src/pages/docs/arcus/settings/manage-properties.md b/src/pages/docs/test-management/settings/manage-properties.md
similarity index 100%
rename from src/pages/docs/arcus/settings/manage-properties.md
rename to src/pages/docs/test-management/settings/manage-properties.md
diff --git a/src/pages/docs/arcus/settings/notifications/email.md b/src/pages/docs/test-management/settings/notifications/email.md
similarity index 100%
rename from src/pages/docs/arcus/settings/notifications/email.md
rename to src/pages/docs/test-management/settings/notifications/email.md
diff --git a/src/pages/docs/arcus/settings/notifications/microsoft-teams.md b/src/pages/docs/test-management/settings/notifications/microsoft-teams.md
similarity index 100%
rename from src/pages/docs/arcus/settings/notifications/microsoft-teams.md
rename to src/pages/docs/test-management/settings/notifications/microsoft-teams.md
diff --git a/src/pages/docs/arcus/settings/notifications/overview.md b/src/pages/docs/test-management/settings/notifications/overview.md
similarity index 100%
rename from src/pages/docs/arcus/settings/notifications/overview.md
rename to src/pages/docs/test-management/settings/notifications/overview.md
diff --git a/src/pages/docs/arcus/settings/notifications/slack.md b/src/pages/docs/test-management/settings/notifications/slack.md
similarity index 100%
rename from src/pages/docs/arcus/settings/notifications/slack.md
rename to src/pages/docs/test-management/settings/notifications/slack.md
diff --git a/src/pages/docs/arcus/settings/smtp-configuration.md b/src/pages/docs/test-management/settings/smtp-configuration.md
similarity index 100%
rename from src/pages/docs/arcus/settings/smtp-configuration.md
rename to src/pages/docs/test-management/settings/smtp-configuration.md
diff --git a/src/pages/docs/arcus/step-groups/create-step-groups.md b/src/pages/docs/test-management/step-groups/create-step-groups.md
similarity index 100%
rename from src/pages/docs/arcus/step-groups/create-step-groups.md
rename to src/pages/docs/test-management/step-groups/create-step-groups.md
diff --git a/src/pages/docs/arcus/step-groups/manage-step-groups.md b/src/pages/docs/test-management/step-groups/manage-step-groups.md
similarity index 100%
rename from src/pages/docs/arcus/step-groups/manage-step-groups.md
rename to src/pages/docs/test-management/step-groups/manage-step-groups.md
diff --git a/src/pages/docs/arcus/test-capture/capture-logs.md b/src/pages/docs/test-management/test-capture/capture-logs.md
similarity index 100%
rename from src/pages/docs/arcus/test-capture/capture-logs.md
rename to src/pages/docs/test-management/test-capture/capture-logs.md
diff --git a/src/pages/docs/arcus/test-capture/install-and-configure.md b/src/pages/docs/test-management/test-capture/install-and-configure.md
similarity index 99%
rename from src/pages/docs/arcus/test-capture/install-and-configure.md
rename to src/pages/docs/test-management/test-capture/install-and-configure.md
index aea8484..6c95d5f 100644
--- a/src/pages/docs/arcus/test-capture/install-and-configure.md
+++ b/src/pages/docs/test-management/test-capture/install-and-configure.md
@@ -14,7 +14,7 @@ contextual_links:
url: '#install-test-capture-extension'
- type: link
name: 'Install from Arcus by Testsigma'
- url: '#install-from-arcus-by-testsigma'
+ url: '#install-from-test-management-by-testsigma'
- type: link
name: 'Install from Chrome Web Store'
url: '#install-from-chrome-web-store'
diff --git a/src/pages/docs/arcus/test-capture/overview.md b/src/pages/docs/test-management/test-capture/overview.md
similarity index 100%
rename from src/pages/docs/arcus/test-capture/overview.md
rename to src/pages/docs/test-management/test-capture/overview.md
diff --git a/src/pages/docs/arcus/test-cases/clone-test-cases.md b/src/pages/docs/test-management/test-cases/clone-test-cases.md
similarity index 100%
rename from src/pages/docs/arcus/test-cases/clone-test-cases.md
rename to src/pages/docs/test-management/test-cases/clone-test-cases.md
diff --git a/src/pages/docs/arcus/test-cases/comment-in-test-cases.md b/src/pages/docs/test-management/test-cases/comment-in-test-cases.md
similarity index 100%
rename from src/pages/docs/arcus/test-cases/comment-in-test-cases.md
rename to src/pages/docs/test-management/test-cases/comment-in-test-cases.md
diff --git a/src/pages/docs/arcus/test-cases/customize-test-case-list-view.md b/src/pages/docs/test-management/test-cases/customize-test-case-list-view.md
similarity index 100%
rename from src/pages/docs/arcus/test-cases/customize-test-case-list-view.md
rename to src/pages/docs/test-management/test-cases/customize-test-case-list-view.md
diff --git a/src/pages/docs/arcus/test-cases/filter-test-cases.md b/src/pages/docs/test-management/test-cases/filter-test-cases.md
similarity index 100%
rename from src/pages/docs/arcus/test-cases/filter-test-cases.md
rename to src/pages/docs/test-management/test-cases/filter-test-cases.md
diff --git a/src/pages/docs/arcus/test-cases/folders.md b/src/pages/docs/test-management/test-cases/folders.md
similarity index 100%
rename from src/pages/docs/arcus/test-cases/folders.md
rename to src/pages/docs/test-management/test-cases/folders.md
diff --git a/src/pages/docs/arcus/test-cases/manage-test-cases.md b/src/pages/docs/test-management/test-cases/manage-test-cases.md
similarity index 100%
rename from src/pages/docs/arcus/test-cases/manage-test-cases.md
rename to src/pages/docs/test-management/test-cases/manage-test-cases.md
diff --git a/src/pages/docs/arcus/test-cases/review-management.md b/src/pages/docs/test-management/test-cases/review-management.md
similarity index 100%
rename from src/pages/docs/arcus/test-cases/review-management.md
rename to src/pages/docs/test-management/test-cases/review-management.md
diff --git a/src/pages/docs/arcus/test-cases/run-history.md b/src/pages/docs/test-management/test-cases/run-history.md
similarity index 100%
rename from src/pages/docs/arcus/test-cases/run-history.md
rename to src/pages/docs/test-management/test-cases/run-history.md
diff --git a/src/pages/docs/arcus/test-cases/test-case-templates.md b/src/pages/docs/test-management/test-cases/test-case-templates.md
similarity index 100%
rename from src/pages/docs/arcus/test-cases/test-case-templates.md
rename to src/pages/docs/test-management/test-cases/test-case-templates.md
diff --git a/src/pages/docs/arcus/test-cases/versions.md b/src/pages/docs/test-management/test-cases/versions.md
similarity index 100%
rename from src/pages/docs/arcus/test-cases/versions.md
rename to src/pages/docs/test-management/test-cases/versions.md
diff --git a/src/pages/docs/arcus/test-plans/manage-test-plans.md b/src/pages/docs/test-management/test-plans/manage-test-plans.md
similarity index 100%
rename from src/pages/docs/arcus/test-plans/manage-test-plans.md
rename to src/pages/docs/test-management/test-plans/manage-test-plans.md
diff --git a/src/pages/docs/arcus/test-plans/share-test-plans.md b/src/pages/docs/test-management/test-plans/share-test-plans.md
similarity index 100%
rename from src/pages/docs/arcus/test-plans/share-test-plans.md
rename to src/pages/docs/test-management/test-plans/share-test-plans.md
diff --git a/src/pages/docs/arcus/test-runs/create-test-runs.md b/src/pages/docs/test-management/test-runs/create-test-runs.md
similarity index 100%
rename from src/pages/docs/arcus/test-runs/create-test-runs.md
rename to src/pages/docs/test-management/test-runs/create-test-runs.md
diff --git a/src/pages/docs/arcus/test-runs/manage-test-runs.md b/src/pages/docs/test-management/test-runs/manage-test-runs.md
similarity index 100%
rename from src/pages/docs/arcus/test-runs/manage-test-runs.md
rename to src/pages/docs/test-management/test-runs/manage-test-runs.md
diff --git a/src/pages/docs/arcus/test-runs/share-test-runs.md b/src/pages/docs/test-management/test-runs/share-test-runs.md
similarity index 100%
rename from src/pages/docs/arcus/test-runs/share-test-runs.md
rename to src/pages/docs/test-management/test-runs/share-test-runs.md
diff --git a/src/pages/docs/arcus/test-runs/test-run-properties.md b/src/pages/docs/test-management/test-runs/test-run-properties.md
similarity index 100%
rename from src/pages/docs/arcus/test-runs/test-run-properties.md
rename to src/pages/docs/test-management/test-runs/test-run-properties.md
diff --git a/src/pages/docs/arcus/testsigma-two-way-integration/automate-manual-test-cases.md b/src/pages/docs/test-management/testsigma-two-way-integration/automate-manual-test-cases.md
similarity index 100%
rename from src/pages/docs/arcus/testsigma-two-way-integration/automate-manual-test-cases.md
rename to src/pages/docs/test-management/testsigma-two-way-integration/automate-manual-test-cases.md
diff --git a/src/pages/docs/arcus/testsigma-two-way-integration/connect-testsigma.md b/src/pages/docs/test-management/testsigma-two-way-integration/connect-testsigma.md
similarity index 97%
rename from src/pages/docs/arcus/testsigma-two-way-integration/connect-testsigma.md
rename to src/pages/docs/test-management/testsigma-two-way-integration/connect-testsigma.md
index 3d9bcbe..414969a 100644
--- a/src/pages/docs/arcus/testsigma-two-way-integration/connect-testsigma.md
+++ b/src/pages/docs/test-management/testsigma-two-way-integration/connect-testsigma.md
@@ -17,7 +17,7 @@ contextual_links:
url: '#interactive-demo'
- type: link
name: 'Integrate Arcus by Testsigma with Testsigma'
- url: '#integrate-arcus-by-testsigma-with-testsigma'
+ url: '#integrate-test-management-by-testsigma-with-testsigma'
---
diff --git a/src/pages/docs/arcus/testsigma-two-way-integration/create-and-sync-test-cases.md b/src/pages/docs/test-management/testsigma-two-way-integration/create-and-sync-test-cases.md
similarity index 100%
rename from src/pages/docs/arcus/testsigma-two-way-integration/create-and-sync-test-cases.md
rename to src/pages/docs/test-management/testsigma-two-way-integration/create-and-sync-test-cases.md
diff --git a/src/pages/docs/arcus/testsigma-two-way-integration/execute-test-plans.md b/src/pages/docs/test-management/testsigma-two-way-integration/execute-test-plans.md
similarity index 96%
rename from src/pages/docs/arcus/testsigma-two-way-integration/execute-test-plans.md
rename to src/pages/docs/test-management/testsigma-two-way-integration/execute-test-plans.md
index 506c159..50a2724 100644
--- a/src/pages/docs/arcus/testsigma-two-way-integration/execute-test-plans.md
+++ b/src/pages/docs/test-management/testsigma-two-way-integration/execute-test-plans.md
@@ -17,10 +17,10 @@ contextual_links:
url: '#interactive-demo'
- type: link
name: 'Execute a Linked Test Plan in Arcus by Testsigma'
- url: '#execute-a-linked-test-plan-in-arcus-by-testsigma'
+ url: '#execute-a-linked-test-plan-in-test-management-by-testsigma'
- type: link
name: 'View Automated Reports in Arcus by Testsigma'
- url: '#view-automated-reports-in-arcus-by-testsigma'
+ url: '#view-automated-reports-in-test-management-by-testsigma'
---
diff --git a/src/pages/docs/arcus/testsigma-two-way-integration/link-test-cases.md b/src/pages/docs/test-management/testsigma-two-way-integration/link-test-cases.md
similarity index 98%
rename from src/pages/docs/arcus/testsigma-two-way-integration/link-test-cases.md
rename to src/pages/docs/test-management/testsigma-two-way-integration/link-test-cases.md
index 68eeb95..da0421f 100644
--- a/src/pages/docs/arcus/testsigma-two-way-integration/link-test-cases.md
+++ b/src/pages/docs/test-management/testsigma-two-way-integration/link-test-cases.md
@@ -17,7 +17,7 @@ contextual_links:
url: '#interactive-demo'
- type: link
name: 'Link Test Cases in Arcus by Testsigma'
- url: '#link-test-cases-in-arcus-by-testsigma'
+ url: '#link-test-cases-in-test-management-by-testsigma'
- type: link
name: 'Link Test Cases in Testsigma'
url: '#link-test-cases-in-testsigma'
diff --git a/src/pages/docs/arcus/testsigma-two-way-integration/link-test-plans.md b/src/pages/docs/test-management/testsigma-two-way-integration/link-test-plans.md
similarity index 98%
rename from src/pages/docs/arcus/testsigma-two-way-integration/link-test-plans.md
rename to src/pages/docs/test-management/testsigma-two-way-integration/link-test-plans.md
index 61e0ea9..8819409 100644
--- a/src/pages/docs/arcus/testsigma-two-way-integration/link-test-plans.md
+++ b/src/pages/docs/test-management/testsigma-two-way-integration/link-test-plans.md
@@ -17,7 +17,7 @@ contextual_links:
url: '#interactive-demo'
- type: link
name: 'Link Test Plans in Arcus by Testsigma'
- url: '#link-test-plans-in-arcus-by-testsigma'
+ url: '#link-test-plans-in-test-management-by-testsigma'
- type: link
name: 'Link Test Plans in Testsigma'
url: '#link-test-plans-in-testsigma'
diff --git a/src/pages/docs/arcus/testsigma-two-way-integration/manage-user.md b/src/pages/docs/test-management/testsigma-two-way-integration/manage-user.md
similarity index 98%
rename from src/pages/docs/arcus/testsigma-two-way-integration/manage-user.md
rename to src/pages/docs/test-management/testsigma-two-way-integration/manage-user.md
index aa1896a..445d269 100644
--- a/src/pages/docs/arcus/testsigma-two-way-integration/manage-user.md
+++ b/src/pages/docs/test-management/testsigma-two-way-integration/manage-user.md
@@ -17,7 +17,7 @@ contextual_links:
url: '#interactive-demo'
- type: link
name: 'Add Users in Arcus by Testsigma'
- url: '#add-users-in-arcus-by-testsigma'
+ url: '#add-users-in-test-management-by-testsigma'
- type: link
name: 'Add Users in Testsigma'
url: '#add-users-in-testsigma'