Skip to content
Docs
Arcus
Popular questions
↑↓ to navigate↵ to selectesc to close
Book a demo

AI in Arcus

AI in Arcus is a set of agents, each owning one part of the testing cycle. Together they plan what to test, write test cases, automate and heal them, and report what fails. Copilot, which automates test cases, isn’t GitHub Copilot. GitHub Copilot connects to Arcus as a coding agent plugin.

The agents work inside your projects, and what they generate lands in the same library as the test cases you write yourself.

Most agents don’t have a screen of their own.

AgentWhat it doesWhere you see it
Sprint Planner AgentPlans which test cases to write for a sprint, from its stories and their linked contextThe Generation Plan in a QI Home session
Test Authoring AgentWrites scenarios, then detailed test cases, from your prompt and the context you attachA QI Home session: “I’m the Test Authoring Agent”
Explorer AgentCrawls your app in a browser and maps its screens, so test cases follow paths that existExplore the app, then write test cases in QI Home, when your prompt includes a URL; the App knowledge graph
Coverage AgentTracks coverage as test cases are reviewed and run, and scores release readiness“Sprint Coverage Agent connected” in a sprint session; the Coverage, Pass Rate, Confidence, and Readiness cards; Release readiness
Test Plan AgentComposes a test plan from a session’s test casesThe Plans & Execution card in a QI Home session
CopilotDrives the app through a test case’s manual steps and writes the automated steps, records steps you perform, and runs themLearn with Copilot on a test case; Copilot
Healer AgentFinds an element another way when its locator stops matching, and saves the healed locator for reviewThe Healer card in a Copilot session, and the heal cards on a run result. See Healer
Analyzer AgentExplains why a step failed (verdict, root cause, and fix), and reads run results for recurring failures and risk signalsThe Analyzer card in a Copilot session, ANALYZER VERDICT on a failed step in a run result, and the Insights and activity panel in a QI Home session. See Analyzer
Bug Reporter AgentRaises a failed run as a defect in your issue trackerRaise it as a defect in a run result’s more options menu. Coming soon. See Bug Reporter

A QI Home session. Callouts mark where each agent appears: (1) the Test Authoring Agent in the chat, (2) the Coverage, Pass Rate, Confidence, and Readiness cards for the Coverage Agent, (3) the Plans & Execution card for the Test Plan Agent, (4) the App knowledge graph card for the Explorer Agent, and (5) the Insights and activity panel for the Analyzer Agent.

Arcus also uses AI to scan your library for duplicates. Deduplication flags exact and semantic duplicates, parameterization candidates, and shared step sequences, and recommends a fix for each.

The Test Cases toolbar with the Deduplication button outlined.

Generation reads the context you give it. That can be stories from Jira, Azure DevOps, Linear, ClickUp, or OpenProject, Confluence pages, and Figma designs. It can also be pull requests from GitHub, GitLab, or Bitbucket, files such as PDFs and Word documents, and video recordings. Trackers, design tools, and repositories need their integration connected. You upload files and videos directly. See Add context.

The QI Home prompt box. Callouts mark (1) the Add Context options, and (2) Context Management and (3) App knowledge graph.

Two other inputs shape what the agents write:

  • The App knowledge graph: the screens the Explorer Agent has visited.
  • Your existing library: the Test Authoring Agent searches your existing test cases and looks for what isn’t covered yet.

Developers can send more context without leaving their tools. Coding agent plugins send each session, and Git plugins send each pull request. See Developers.

  • Plans before cases: the Generation Plan comes first. Approve it, Modify it, or Cancel.
  • Review before the library: generated test cases arrive as Pending. Accept them, or use Save to Library to choose the folder. Rejected cases stay listed in the review but don’t count toward coverage. To add your team’s approval on top, turn on Review Management in Project Settings > Overview.
  • Steer Copilot: in the Copilot configuration, Pause on ambiguity makes Copilot stop and ask when a step matches more than one element. Instructions to Copilot tells it what to do or avoid, such as stopping before payment.
  • Review self-healing: every locator the Healer Agent repairs is recorded for review.
  • Choose the fixes: Deduplication recommends a merge or a step group for each finding, and you choose which to apply.

The Copilot Behaviour section of the Copilot configuration, with Pause on ambiguity and Instructions to Copilot outlined.

The MCP server lets an AI client such as Claude Code read your projects and test cases, and draft new ones into Arcus. The CLI lets a coding agent validate and run test cases on your machine.

Was this page helpful?