Connect
Map the automation you already operate
Connect GitHub Actions or Azure DevOps, then select discovered repositories, branches, workflows, and pipelines. Add the framework and result context that makes each Test Source understandable.
QaCockpit Cloud · How it works
Your automation stays put.
The understanding comes together.
QaCockpit adds a quality-intelligence layer above the repositories, frameworks, and CI/CD systems your teams already trust.
This page describes the hosted QaCockpit Cloud workflow. Using QaCockpit inside Azure DevOps? Explore QaCockpit for Azure DevOps.
One connected operating model
From distributed test runs to focused improvement.
Collect
Bring execution evidence into one record
Start existing CI/CD workflows from validated configurations or attach completed results to a campaign. JUnit reports, execution context, and protected artifacts remain connected to the exact attempt.
Understand
See more than a green or red pipeline
Compare expected scope with observed results, separate pipeline lifecycle from test outcome, and move from an organization signal to the exact project, source, test, failure, and artifact context.
Improve
Turn history into focused quality work
Use Test Catalog, Failure Inbox, trends, ownership, and source-health signals to find recurring problems, slow feedback, maintenance gaps, and weak release evidence.
One durable quality record
The execution story survives the pipeline.
Campaign scope, source runs, attempts, expected tests, observed results, environment, failures, and artifacts remain connected after CI/CD finishes.
Campaign Run Report
Clear responsibility boundaries
A quality control plane, not another execution cloud.
Your CI/CD keeps the code, secrets, dependencies, and execution environment.
Your repositories
Tests, workflows or pipelines, result configuration, and dependencies.
Projects, Test Sources, campaigns, permissions, scope, failures, and reports.
Your CI/CD provider
GitHub Actions or Azure DevOps runs in the security model you control.
Structured evidence
JUnit results, metadata, attempts, and authorized artifact evidence.
What changes for the team
Less reconstruction. More focused quality work.
See automation health, gaps, ownership, and cross-source campaign evidence.
Move from a failure signal to its exact run, stack, environment, history, and artifacts.
Read a clear quality summary without learning every repository and pipeline convention.
Frequently asked
Start with the stack you already have.
Does QaCockpit replace our test frameworks or CI/CD?
No. Your repositories remain the source of truth and your existing CI/CD executes the workflows. QaCockpit coordinates runs and turns returned evidence into a shared quality view.
Do all teams need to use the same technology?
No. A project can combine multiple repositories, workflows, frameworks, and result-producing Test Sources. QaCockpit normalizes the operational signal without forcing a framework migration.
What results can QaCockpit understand today?
JUnit XML is the primary normalized result format. QaCockpit also keeps execution metadata and protected artifact evidence such as screenshots, logs, traces, videos, and archives when supplied by the integration.
Can we use results that were not started from QaCockpit?
Yes. Campaigns are collection sessions and can include executions already recorded in QaCockpit. Provider-specific retained-result adoption is available where the integration supports it.
Your workflow, connected
See where quality work can become clearer and faster.
Describe your current automation landscape and we will map the first useful integration together.
Contact us