How it works

Your automation stays put.
The signal comes together.

QaCockpit adds an operational layer above the repositories, frameworks, and workflows your teams already use.

Model your automation sources

A Test Source describes a repository, provider, workflow, framework, result format, and artifact rules. Your tests stay where they are.

Define safe, named inputs for a workflow and reuse them across focused runs and regression campaigns. No arbitrary shell commands enter the portal.

Group profiles into sequential stages with parallel execution inside each stage. QaCockpit dispatches your existing GitHub Actions workflows.

JUnit results, logs, and protected artifacts return to one run report. Expected scope, missing results, history, and failure clusters stay visible.

One campaign record

Campaign stages, attempts, expected tests, observed results, branch, commit, environment, logs, and artifacts remain connected.

Campaign Run Report

Clear responsibility boundaries

Your CI keeps the code, secrets, dependencies, and execution environment.

01 · Define

Tests, workflow YAML, upload configuration, and framework dependencies.

02 · Coordinate

Sources, profiles, campaigns, permissions, expected scope, and reports.

03 · Execute

Workflow jobs run in the environment and security model you control.

04 · Return

JUnit XML, metadata, attempts, logs, and authorized artifacts.

Your workflow, connected

Describe your current automation landscape and we will map the first integration together.