GitLab CI integration

End-to-end tests in every GitLab pipeline

The DoesQA catalog component brings end-to-end coverage into GitLab CI with a single include. The same .gitlab-ci.yml that builds and deploys your app now starts a DoesQA Run, waits for the outcome and keeps you shipping with confidence.

A pipeline that reflects real journeys

Turn on wait and the job holds until the Run finishes, so a broken login or checkout turns the pipeline red before it reaches users. Want speed instead? Fire the Run, move on, and let Notifications carry the result.

Choose what runs on each pipeline

  • Include and exclude tags, or a Run Recipe

  • Value overrides that point the Run at the environment you just deployed

  • Only the Test Cases with a chosen tag

  • Concurrency caps for shared pipelines

  • A label on every Run, such as Nightly Test Run

One setup across your tools

The component wraps the Universal Webhook, so the key, tags and Recipes you use in GitLab work the same way in GitHub, Bitbucket and Azure DevOps.

Find the component in the GitLab CI/CD Catalog.

DoesQA Flows dashboard

Get your next release tested end to end.

Hosted journeys with email, MFA, and branching. Shared Elements keep maintenance low. Pass and fail from real hosted browsers.

Get your next release tested end to end.

Hosted journeys with email, MFA, and branching. Shared Elements keep maintenance low. Pass and fail from real hosted browsers.

DoesQA Flows dashboard

Get your next release tested end to end.

Hosted journeys with email, MFA, and branching. Shared Elements keep maintenance low. Pass and fail from real hosted browsers.