Add context
Context is everything the Test Authoring Agent reads before it writes a test case. You supply it 3 ways: sources you attach to a generation, artifacts a sprint’s stories link to, and developer activity that lands in Context Management waiting to be mapped. Arcus also gathers context on its own from run history and from live-app learning, listed in the Context drawer below.
Connect the sources first: install the coding-agent plugins from Context Management, connect GitHub, Bitbucket, or GitLab under Settings > Integrations (see Developers), and link trackers under Manage integrations, described at the end of this page.
Attach sources to a generation
Section titled “Attach sources to a generation”Attach as many sources as apply.
-
In the Add Context bar on QI Home or in the Arcus panel, click a source, or click the plus icon (+) for the full list.
-
Make your selections in the Add Context dialog. Each attached source shows a count beside its name.

-
Click Save. The source appears in the Add Context bar with a count beside its name.
| Source | Holds | You select |
|---|---|---|
| Jira | Requirements and user stories | Project, then the stories |
| Azure DevOps, Linear, ClickUp, OpenProject | Work items | Project, then the items |
| Confluence | PRDs and knowledge-base pages | Space, then pages |
| Figma | Designs: UI references, flows, and screens | Project, design file, page, then frames |
| GitHub | Pull requests and issues | Repository, then the pull requests or issues |
| Bitbucket | Pull requests | Repository, then the pull requests |
| GitLab | Merge requests | Project, then the merge requests |
| Files and Documents | .jpeg, .png, .docx, .pdf, .xls files | The files to upload |
| Video Recording | .mp4, .mov, .webm, .avi, .mkv recordings | The videos to upload |
Uploads are capped at 500 MB per file. A source whose integration isn’t connected yet shows an Integrate button in the dialog. Connect Confluence and Figma from there, and trackers under Settings > Integrations.

Read the Context drawer
Section titled “Read the Context drawer”Every sprint and Adhoc session page carries a Context button that opens the drawer, such as Session context for an Adhoc session: the external links Arcus gathered for that work, grouped by category. Each category shows a count of its items. Click Refresh context to re-read the sources.
- Business Context: what was supposed to be built (requirements and scope).
- Manual / Tribal Context: what humans know but never wrote down (uploads and notes).
- Technical Context: what got built (branches, PRs, code changes).
- Run History Context: what execution actually traversed (runs and flows).
- Live App Context: what Arcus learned from the live app during Agentic Learning sessions on these test cases.
Three more categories show under Coming soon: User Intent Context (what the developer meant to build, from AI coding sessions), User Journey Context (what end users actually do, from product analytics), and Production Failure Context (what breaks in production, from bugs and feedback).

Expand a category to see its items. A Jira story, for example, shows its source, its processing state, and its status. A run history item shows the run and its state, such as Active.

Open Context Management
Section titled “Open Context Management”-
Open QI Home.
-
Click Context Management. Its badge shows the pending count.
Until a source is connected, Unlinked Contexts offers Connect GitHub for pull requests, an Install plugin link for each coding tool (Claude Code, GitHub Copilot, Codex, and Cursor), and the Arcus CLI for pushing test cases you already wrote in code. Install the CLI with npm install -g @testsigma/arcus-cli.
Four tabs split the queue:
- Unlinked Contexts: pull requests and coding sessions not mapped yet
- Linked Contexts: everything already mapped, with the sprint and stories it went to
- Unlinked Test Cases: test cases pushed via CLI or gap exploration, not linked yet
- Linked Test Cases: test cases already linked

Map a context
Section titled “Map a context”Unlinked Contexts summarizes what’s waiting: where it came from (GitHub and Bitbucket pull requests, GitLab merge requests, or sessions from Claude Code, GitHub Copilot, Codex, and Cursor), the pending and mapped counts, and the age of the oldest pull request. Filter the list by source with All or a source tab: GitHub, Bitbucket, GitLab, Claude, Copilot, Cursor, Codex, or Collaborations (Slack and Microsoft Teams). A source tab appears only when that source has entries.
What an entry shows depends on its source. A coding session shows its title, taken from the prompt, with the author, the repository, when it was pushed, and an AI suggestion for the module and sprint. A pull request shows its title or branch, the repository, the author, and when it was opened or last updated.

When a pull request lands here and Arcus can’t tell which story it belongs to, a dialog explains why: Your PR landed here because it has nowhere to belong. Click Map this Manually to map it now, or Integrate Tool to connect a tracker, so that later pull requests carrying a ticket ID map on their own.
-
Click Map to Module on the entry.
-
Select the Project.
-
Under Map to, select Sprint or Adhoc.
-
For a sprint, select the Sprint and the Stories the work relates to. For Adhoc, select the session under Existing Adhoc Session, or click + Create New Adhoc Session.
-
Click Map.
When you map an entry, the Test Authoring Agent generates test cases from that context: new ones, or updates to existing ones covering the same modules. To map several entries at once, select their checkboxes and click Map to Module. For an entry that isn’t relevant to coverage, click Discard.
Linked Contexts then shows each mapped entry tagged with its sprint and story, plus totals for contexts mapped and sprints covered.
Map automatically
Section titled “Map automatically”Two kinds of entry are mapped without your input:
- A pull request whose title or description carries a ticket ID from your connected tracker is mapped straight to the sprint holding that story.
- A developer who runs
/arcus:map ticket <KEY>in their coding tool links the session before it arrives.
Link a pushed test case
Section titled “Link a pushed test case”Test cases authored with /arcus:test and pushed with /arcus:push, or saved by a gap exploration on the App knowledge graph, arrive on Unlinked Test Cases with their module, type, automation state, and local run result.
Test cases pushed with arcus push from the Arcus CLI go straight to the project’s folder in Test Cases, without a sprint, story, or module. They don’t appear on Unlinked Test Cases, so there’s nothing to link.
-
Click Link on the test case.
-
Select the Project.
-
Under Link to, select Sprint or Adhoc.
-
Select the sprint story, or the Adhoc session.
-
Click Link & accept.
The test case moves to the selected story, accepted and ready to run in a plan. Its local run results carry over. To drop one instead, click the delete icon.
Linked Test Cases lists everything already linked, each tagged with its module.
Manage the connections
Section titled “Manage the connections”Two dialogs behind the more options icon (⋮) on QI Home control what flows in:

- Manage integrations: toggles for the project management tools Arcus reads sprints from (Jira, Linear, ClickUp, Azure DevOps, OpenProject), and for Dev Tools and AI (GitHub, Bitbucket, and GitLab, plus setup links for the Claude Code, GitHub Copilot, Codex, and Cursor plugins). A connected plugin shows Active.
- Manage connected projects: use it to link 1 project per tool. Arcus then reads the active sprints in that project and drafts test cases for each story’s acceptance criteria. The steps are in Generate test cases.
Was this page helpful?
Thanks for the feedback.