QaCockpit Cloud documentation

Using the Azure DevOps Marketplace extension?

This Cloud documentation covers provider connections to the hosted QaCockpit platform.

Open QaCockpit for Azure DevOps documentation

Start with the evidence path

QaCockpit does not execute customer test code. Your CI/CD provider runs the tests, the framework writes JUnit XML, and the pipeline retains that file as an artifact. QaCockpit then imports the exact run evidence into a Test Source.

Test frameworkJUnit XMLCI/CD artifactQaCockpit

Make the test runner create one or more non-empty JUnit XML files.
Retain those files on every completed run, including runs with failed tests.
Connect GitHub Actions or Azure DevOps and create a Test Source.
Run the source or let QaCockpit observe the provider run and import its evidence.

Do not pass QaCockpit secrets or internal run IDs through workflow inputs. The default integration reads retained artifacts through the authorized provider connection.

Copy a provider or framework example

CI/CD provider

GitHub Actions

Add workflow_dispatch, create JUnit XML, and retain it with upload-artifact.

CI/CD provider

Azure DevOps

Publish the JUnit directory as a Pipeline artifact and keep result publishing separate.

Evidence contract

JUnit XML

Understand the portable result format, file discovery, failures, and multi-file reports.

Framework

Playwright

Configure the JUnit reporter and retain screenshots, videos, traces, and HTML evidence.

Framework

REST Assured

Retain Maven Surefire XML and API diagnostics from a JUnit 5 test suite.

Quality signal

Test Scope

Detect missing, added, and changed test identities instead of trusting counts alone.

From a Test Source to a release report

Connect CI/CD

Open Integrations in the authenticated application. Connect the QaCockpit GitHub App or the Azure DevOps organization, then refresh the provider inventory.

Configure a Test Source

A Test Source is one configured automation and result stream—not an entire repository. Select its repository, workflow or pipeline, default ref, framework, and result context.

Run and review evidence

A Test Execution keeps pipeline lifecycle, result intake, and test outcome separate. Combine several sources in a Campaign, compare expected and reported scope, review failures in the Failure Inbox, and share a versioned release report.