---
title: CI/CD integration
description: >-
  Run Kapptivate tests automatically in CI/CD pipelines like GitHub Actions,
  with pass/fail status, summaries, and deep-linked results.
sidebarTitle: CI/CD
lastUpdated: "2026-09-23"
---

> **For AI agents:** the complete documentation index is at [llms.txt](/llms.txt). Append `.md` to any page URL for its markdown version.

Tests that only run when someone remembers to click Run don't protect a release. Driving Kapptivate from your CI/CD pipeline puts the same tests in front of every push, schedule, or deploy, with the results readable directly in the pipeline.

![A GitHub Actions run with the Kapptivate Test Results summary table and its View deep links](/images/cicd-github-summary.webp)

## How it works

Your workflow runs the [Kapptivate CLI](/cli/overview), authenticated with an [API key](/administration/api-keys), to execute a test or campaign. The pipeline then reflects the outcome:

- The job **succeeds or fails** with the run, so a red pipeline means a red test.
- A **Kapptivate Test Results** summary lands in the run's summary page, one row per test with its **Status**, name, **Duration**, and a **View** link.
- Each **View** link deep-links to that execution's [results](/executions/results) in the Kapptivate app, screenshots, video, and steps included.
- The run's report is attached as an **artifact**.

## GitHub Actions

In GitHub Actions, the summary table renders on the workflow run's Summary page. A typical setup runs a campaign on a schedule (for example `run-kapptivate-suite.yml` with `on: schedule`) or on push, and fails the job when tests fail.

See [ktm ci build](/cli/commands/ci/build) and [ktm ci run](/cli/commands/ci/run) for the commands to use in your workflow, and the [CI/CD guide](/cli/ci-cd) for complete pipeline examples.

<Tip>
Prefer driving tests from an AI assistant instead of a pipeline? The [MCP server](/mcp/overview) lets agents build and run campaigns in natural language.
</Tip>