GitLab CI

Run DevTools YAML flows in GitLab CI and emit JUnit reports. Useful for merge request checks and scheduled pipelines across environments.

For the full setup (PR checks, artifacts, caching, smoke vs regression), see the API regression testing guide.

Required env vars

Depends on your flows. Common examples:

LOGIN_EMAIL, LOGIN_PASSWORD
API keys or base URLs via GitLab CI variables

How to run it

Add a job in .gitlab-ci.yml:

stages: [test]

api_tests:
  stage: test

Commit and push to run in GitLab pipelines.

TODO:

Add a screenshot of pipeline summary with test results.
Clip of job log showing devtools output.

stages: [test]

api_tests:
  stage: test
  image: ubuntu:latest
  script:
    - apt-get update && apt-get install -y curl
    - curl -fsSL https://sh.dev.tools/install.sh | bash
    - devtools flow run --report junit:test-results.xml tests.yaml

What to change

Path to your YAML flows file (tests.yaml).
Stages/jobs structure and caching strategy.
Reports and artifacts for visibility.

Common variations

Parallel jobs per service or environment.
Manual gates for production deploys.
Scheduled nightly runs with only: [schedules].

Links