From fab6d18adde6564c8b571c7353ab00d1175a5e80 Mon Sep 17 00:00:00 2001 From: Bharath Krishna <118433150+bharathk08@users.noreply.github.com> Date: Mon, 10 Aug 2026 11:02:02 +0530 Subject: [PATCH] updated claude code docs --- .../context-mapping/connect-claude-code.md | 38 ++++++++++--------- .../qi-home/context-mapping/connect-codex.md | 16 ++++---- .../qi-home/context-mapping/connect-cursor.md | 16 ++++---- .../context-mapping/connect-github-copilot.md | 16 ++++---- .../qi-home/context-mapping/overview.md | 22 +++++++++++ 5 files changed, 66 insertions(+), 42 deletions(-) diff --git a/src/pages/docs/test-management/qi-home/context-mapping/connect-claude-code.md b/src/pages/docs/test-management/qi-home/context-mapping/connect-claude-code.md index 3e2cef4..b1ed915 100644 --- a/src/pages/docs/test-management/qi-home/context-mapping/connect-claude-code.md +++ b/src/pages/docs/test-management/qi-home/context-mapping/connect-claude-code.md @@ -35,18 +35,23 @@ contextual_links: **Install the Arcus plugin for Claude Code 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. +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. + +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/). --- > ## **Prerequisites** > > Before you begin, ensure that: -> * Claude Code (latest version) is installed. -> * Python 3.9 or later is installed and accessible as python3. +> * Claude Code (latest version recommended) is installed. +> * Python 3.9 or later is available on your PATH as python3. The plugin's lifecycle hooks are Python scripts. Python is installed by default on macOS and Linux. > * Git is configured in your local environment. > * You have an active project in Arcus by Testsigma. +[[info | **NOTE**:]] +| There is nothing to build. The plugin installs directly from the Claude Code plugin marketplace. + --- ## **Install the Plugin** @@ -64,11 +69,9 @@ claude plugin install arcus@testsigma 1. In Claude Code, run **/arcus:login**. - 2. Complete the login flow in the browser. Return to Claude Code 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**. - +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**. To see your available projects, run **/arcus:project** without an argument. 4. Start coding. The plugin begins capturing your context in the background. @@ -85,10 +88,10 @@ Run **/arcus:map <ticket-key>** at any point before pushing to link your c /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. +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 QA maps it from there. See [Map Developer Context](https://testsigma.com/docs/test-management/qi-home/context-mapping/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/). --- @@ -96,7 +99,6 @@ Running **/arcus:map** before pushing means your context arrives in QI Home alre 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). --- @@ -105,14 +107,14 @@ The context appears in QI Home under **Unmapped Context** (if you did not run ** | Command | What it does | |---------|-------------| -| /arcus:help | Lists all available Arcus commands | -| /arcus:login | Authenticates your Arcus account | -| /arcus:logout | Logs out of your Arcus account | -| /arcus:project | Connects the plugin to an Arcus project | -| /arcus:map | Links the current context to a sprint story | -| /arcus:test | Runs tests from QI Home in the current context | -| /arcus:testsigma-tests | Lists existing Testsigma tests for the current project | -| /arcus:push | Uploads the current context to QI Home | +| /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 | --- @@ -123,4 +125,4 @@ If your team has the Arcus GitHub App installed and you raise a pull request for * **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. ---- \ No newline at end of file +--- 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 index 8786c64..73f0a99 100644 --- 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 @@ -96,14 +96,14 @@ The context appears in QI Home under **Unmapped Context** (if you did not run ** | Command | What it does | |---------|-------------| -| /arcus:help | Lists all available Arcus commands | -| /arcus:login | Authenticates your Arcus account | -| /arcus:logout | Logs out of your Arcus account | -| /arcus:project | Connects the plugin to an Arcus project | -| /arcus:map | Links the current context to a sprint story | -| /arcus:test | Runs tests from QI Home in the current context | -| /arcus:testsigma-tests | Lists existing Testsigma tests for the current project | -| /arcus:push | Uploads the current context to QI Home | +| /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 | --- 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 index c82621c..1c2f865 100644 --- 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 @@ -95,14 +95,14 @@ The context appears in QI Home under **Unmapped Context** (if you did not run ** | Command | What it does | |---------|-------------| -| /arcus:help | Lists all available Arcus commands | -| /arcus:login | Authenticates your Arcus account | -| /arcus:logout | Logs out of your Arcus account | -| /arcus:project | Connects the plugin to an Arcus project | -| /arcus:map | Links the current context to a sprint story | -| /arcus:test | Runs tests from QI Home in the current context | -| /arcus:testsigma-tests | Lists existing Testsigma tests for the current project | -| /arcus:push | Uploads the current context to QI Home | +| /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 | --- 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 index d2c73af..9018085 100644 --- 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 @@ -99,14 +99,14 @@ The context appears in QI Home under **Unmapped Context** (if you did not run ** | Command | What it does | |---------|-------------| -| /arcus:help | Lists all available Arcus commands | -| /arcus:login | Authenticates your Arcus account | -| /arcus:logout | Logs out of your Arcus account | -| /arcus:project | Connects the plugin to an Arcus project | -| /arcus:map | Links the current context to a sprint story | -| /arcus:test | Runs tests from QI Home in the current context | -| /arcus:testsigma-tests | Lists existing Testsigma tests for the current project | -| /arcus:push | Uploads the current context to QI Home | +| /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 | --- diff --git a/src/pages/docs/test-management/qi-home/context-mapping/overview.md b/src/pages/docs/test-management/qi-home/context-mapping/overview.md index 8c27426..5acc445 100644 --- a/src/pages/docs/test-management/qi-home/context-mapping/overview.md +++ b/src/pages/docs/test-management/qi-home/context-mapping/overview.md @@ -10,6 +10,12 @@ warning: false contextual_links: - type: section name: 'Contents' + - type: link + name: 'Why Developer Context Mapping Exists' + url: '#why-developer-context-mapping-exists' + - type: link + name: 'Who Uses It' + url: '#who-uses-it' - type: link name: 'What Developer Context Mapping Does' url: '#what-developer-context-mapping-does' @@ -34,6 +40,22 @@ Developer Context Mapping connects the tools your developers already use to the --- +## **Why Developer Context Mapping Exists** + +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. 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. + +--- + +## **Who Uses It** + +* **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/test-management/qi-home/quality-intelligence-metrics/). + +--- + ## **What Developer Context Mapping Does** Developer Context Mapping captures two types of developer activity: