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

GitLab

The Arcus GitLab integration sends every merge request your team raises to QI Home, where Arcus generates test cases from its code changes.

Prerequisites

  • An active Arcus project.
  • The Owner role on the GitLab group. Only an Owner can create the group webhook Arcus needs.

Developers don’t change how they work. Once GitLab is connected, every merge request reaches Arcus on its own.

  1. In the left navigation, go to Settings > Integrations, and click Setup Integration next to GitLab.

  2. Sign in to GitLab if prompted, and authorize the Arcus application.

  3. If you own more than one GitLab group, the Select your GitLab group dialog opens. Select the group and click Connect.

Arcus registers a webhook on the group, so every project in it is covered. The GitLab card then shows Connected.

Merge requests raised in the group’s projects now arrive on the Unlinked Contexts tab of Context Management.

With a tracker such as Jira connected, a merge request whose title or description contains a ticket ID such as PROJ-123 goes straight to the sprint holding that story. It never reaches Unlinked Contexts, and nobody maps it manually.

  1. In the left navigation, go to Settings > Integrations.

  2. Confirm the GitLab card shows Connected. If it also shows Needs attention, hover the badge for the reason.

  3. Raise a test merge request in a project in the connected group.

  4. Open QI Home > Context Management. The merge request appears on the Unlinked Contexts tab within a few seconds.

On Unlinked Contexts, click Map to Module on the merge request, then pick a sprint and its stories, or an Adhoc session. Arcus generates test cases from the merge request’s changes, and the entry moves to Linked Contexts.

The full steps, including mapping several entries at once and discarding one that isn’t relevant, are in Context Management.

Was this page helpful?