Skip to main content

Reading results: Allure & CI

Where test results live and how to read them — locally and on CI.

Local​

  • Run output: screenshots on failure in results/screenshots/; videos + traces in test-results/; per-test logs in results/logs/.
  • Allure report: make allure-serve builds and serves the report from results/allure-results/.

CI​

  • Allure dashboard: https://allure.int.octostar.com (Tailscale). The live history of every scheduled/triggered run. Trace-viewer deep links are baked into each test's attachments.
  • Reading a run: open the run → failing tests are categorised (see allure-categories.json). Each test carries its screenshot, video, log, and a trace-viewer link — start with the trace.

Applying a PR to CI​

Use this workflow to apply different docker images to CI environment https://github.com/Octostarco/Octostarco.github.io/actions/workflows/push_octostar_changes_on_server.yaml

App versioning is done by editing and deploying different versions in the app editor manifest

Telling failure types apart​

Use the trace + log to classify the failure:

  • Test bug — wrong/brittle selector, missing wait, bad assumption about seed data.
  • Product regression — the test is right; the app changed. File it.
  • Infra — Tailscale, health check, environment. Reproduce locally to confirm.
  • Github Actions -