How to integrate with CI/CD

Add Aucert testing to your continuous integration pipeline.

Prerequisites

• Aucert CLI installed
• An AUCERT_API_KEY (generate from the Aucert dashboard)
• An aucert.config.yaml in your repository

GitHub Actions

.github/workflows/aucert.yml

name: Aucert Tests
on: [pull_request]
jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - run: npm install -g @aucert/cli
      - run: aucert run --output junit
        env:
          AUCERT_API_KEY: ${{ secrets.AUCERT_API_KEY }}

Store AUCERT_API_KEY in Settings → Secrets → Actions.

GitLab CI

.gitlab-ci.yml

aucert:
  image: node:20
  script:
    - npm install -g @aucert/cli
    - aucert run --output junit
  variables:
    AUCERT_API_KEY: $AUCERT_API_KEY
  artifacts:
    reports:
      junit: aucert-results/*.xml

Store AUCERT_API_KEY in Settings → CI/CD → Variables.

Jenkins

Jenkinsfile

pipeline {
    agent any
    environment {
        AUCERT_API_KEY = credentials('aucert-api-key')
    }
    stages {
        stage('Test') {
            steps {
                sh 'npm install -g @aucert/cli'
                sh 'aucert run --output junit'
            }
            post {
                always {
                    junit 'aucert-results/*.xml'
                }
            }
        }
    }
}

Store AUCERT_API_KEY in Jenkins Credentials.

tip

Use --output junit for CI/CD so test results appear in your CI provider's test summary view. For comprehensive nightly reports, use --output html instead.

What's next

• GitHub Actions (detailed) — Advanced workflows, matrix builds, caching
• Configure project — Customize test parameters
• Interpret results — Understand test output