Connect Codex

Introduction

Projects

Test Cases

Data Sets

Imports and Exports

Step Groups

Test Runs

Test Plans

test capture

Integrations

Testsigma Two-way Integration

Settings

Manage Users

QI Home

Reports & Analytics

API Reference

CI/CD Integrations

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

Install the Arcus plugin from the Codex marketplace.

Log In and Connect Your Project

In Codex, run /arcus:login.
Complete the login flow in the browser. Return to Codex 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.
Start coding. The plugin begins capturing your context in the background.

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.

NOTE:

You can push without mapping. The context lands in Unmapped Context and QA maps it from there. See Map Developer Context.

Push Your Context

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.

Did you find it helpful?