Skip to content
You're viewing the v2 docs. Looking for v1?Go to v1 docs
Docs
Arcus
Popular questions
↑↓ to navigate↵ to selectesc to close
Book a demo

Cursor

The Arcus extension for Cursor captures your coding sessions and sends them to QI Home, where Arcus generates test cases from them.

Prerequisites

  • Cursor, or VS Code 1.85 or later.
  • node on the integrated terminal’s PATH.
  • An active Arcus project.

Install the extension

Section titled “Install the extension”

The extension captures file saves and the editor’s hook events, and also works in VS Code. Its project and map commands run a bundled Node script, which is why it needs node.

Install Arcus from the VS Code Marketplace. Cursor reads the same marketplace.

Cursor commands use a hyphen where the other Arcus plugins use a colon: /arcus-login, not /arcus:login.

Sign in and pick a project

Section titled “Sign in and pick a project”

  1. Press Cmd+Shift+P, select Arcus: Sign In, and complete the sign-in in the browser.

  2. Run /arcus-project list to see your projects, then /arcus-project use <project_id> to pin the one your sessions go to.

Capture starts after you sign in. To sign out, select Arcus: Sign Out from the command palette, which clears your local credentials.

Section titled “Link your work to a ticket”

Run /arcus-map ticket <KEY> with the ticket for the work you’re doing:

Terminal window
/arcus-map ticket PROJ-123

Your session then arrives in QI Home already mapped to the sprint holding that ticket, so nobody maps it manually.

Write and push test cases

Section titled “Write and push test cases”

  1. Run /arcus-test, optionally followed by the feature you want covered. Cursor writes end-to-end test cases for the current repository, validates them, and offers to run them.

  2. Run /arcus-push to send the test cases from this session to Arcus.

For every command, see Plugins. Swap the colon for a hyphen in each one.

Where your work lands

Section titled “Where your work lands”
  • Sessions arrive on the Unlinked Contexts tab of Context Management, unless you linked a ticket. Mapping a session to a sprint or an Adhoc session triggers test generation from it.
  • Pushed test cases arrive on the Unlinked Test Cases tab, unless you picked a sprint when you pushed.

The mapping and linking steps are in Context Management.

Pull requests for the same work

Section titled “Pull requests for the same work”

With the Arcus GitHub App installed, a pull request for work you captured here joins your session automatically:

  • Session not mapped yet: the session and the pull request become a single entry in Unlinked Contexts.
  • Session already mapped: the pull request is mapped to the same sprint or Adhoc session, and there’s nothing more to do.

Was this page helpful?