Setting Up CI

Setting Up CI

A published report with no launches just shows "No runs yet." This page is the fastest path from there to a report that actually reflects your test history — full detail lives in the CLI Tool docs; this is the short version for an open-source project on GitHub Actions.

Option 1: qualflare-action (recommended for GitHub Actions)

A GitHub Action that wraps the CLI — one uses: step instead of a manual binary install:

- name: Run tests
  run: pytest --junitxml=results.xml
  continue-on-error: true   # let the upload step run even when tests fail

- name: Upload results to Qualflare
  uses: Qualflare/qualflare-action@v1
  with:
    token: ${{ secrets.QF_TOKEN }}
    project: myapp
    results: results.xml

continue-on-error: true on the test step matters: GitHub Actions aborts a job on a failing step by default, which would skip the upload exactly when you most want the failure analysis. Full reference — every input, the runner support matrix, version pinning — is in the qualflare-action reference.

Option 2: the CLI directly

Works on any CI platform, not just GitHub Actions, and exposes every qf collect flag the Action doesn't (--environment, --milestone, --branch, --dry-run, and more):

qf login ci "$QF_TOKEN" --force
qf ci collect results.xml

See CI/CD Integration for the full multi-platform guide (GitHub Actions, GitLab CI, Jenkins, Azure DevOps) and Collect Command for the full flag reference.

Getting a token

Both options need a Qualflare access token. Mint one at Project Settings → Access Tokens, then store it as a CI secret — the examples above name it QF_TOKEN, but the name is yours to choose as long as it matches what you reference in your workflow.

Related

• qualflare-action Reference — full inputs, outputs, and caveats
• CI/CD Integration — the CLI-based guide, covering four CI platforms
• Publishing a Report — where these results end up