- Projects
- Test Cases
- Data Sets
- Imports and Exports
- Step Groups
- Test Runs
- Test Plans
- Integrations
- Testsigma Two-way Integration
- Settings
- Manage Users
- Reports & Analytics
- CI/CD Integrations
Connect Claude Code
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 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.
Prerequisites
Before you begin, ensure that:
- 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.
There is nothing to build. The plugin installs directly from the Claude Code plugin marketplace.
Install the Plugin
-
In your terminal, run the following commands to add and install the Arcus plugin:
claude plugin marketplace add testsigmahq/arcus-claude-plugin claude plugin install arcus@testsigma
Log In and Connect Your Project
- In Claude Code, run /arcus:login.
- Complete the login flow in the browser. Return to Claude Code when prompted.
- 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.
- Start coding. The plugin begins capturing your context in the background.
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. Replace <ticket-key> with the Jira ticket ID for the work you are doing.
/arcus:map PROJ-123Running /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.
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.
Push your context
Test cases stay on your machine until you push them. Push is a guided flow, and Claude Code prompts you for each decision in order.
- Run /arcus:push, or ask Claude Code to push the test cases.
- Select the sprint to push into, or keep the test cases unmapped.
- Select the story the test cases map to. This step appears only if you selected a sprint.
- Select the module the test cases belong to. Arcus suggests a module based on the test case content.
- Set the priority for the test cases.
- Confirm the push. Arcus creates the test cases with the values you selected, and they appear in the sprint with both manual and automated steps.
Select unmapped when you do not yet know where the work belongs. The test cases wait in Unmapped Context until you resolve them. See Map developer context.
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 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.
Want to contribute or report missing content?