Allure in CI Pipelines and Dashboards

Local reports are useful, but the real value appears when Allure is wired into CI pipelines and made available as a shared dashboard. This way, everyone can see the state of tests for each branch, build or release.

Publishing Allure Reports from CI #

The typical flow is: run tests with Allure results enabled, archive the allure-results directory as an artifact and then generate and host the HTML report. Depending on your setup, you can publish the report to static hosting, an Allure server or keep it as a downloadable artifact.

# Example: GitHub Actions steps to archive Allure results
jobs:
  tests:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: Install deps
        run: npm ci
      - name: Run tests with Allure
        run: npm test -- --reporter=allure
      - name: Upload Allure results
        if: always()
        uses: actions/upload-artifact@v4
        with:
          name: allure-results
          path: allure-results

Historical reports allow you to spot trends, such as the same test failing repeatedly or growing suite duration.

Common Mistakes #

Mistake 1 — Keeping Allure reports only on local machines #

This limits collaboration.

❌ Wrong: Expecting others to reproduce runs locally to see reports.

✅ Correct: Publish reports from CI so they are available to the whole team.

Mistake 2 — Not integrating reports into daily workflows #

This reduces impact.

❌ Wrong: Generating reports but never linking them in PRs or dashboards.

✅ Correct: Make reports part of code review and release readiness checks.