Test Observability
Test artifact
Also known as: build artifact, test report artifact
A test artifact is a file a CI run produces and stores — a results file, an HTML report, a screenshot, a trace — retained under a policy rather than kept indefinitely.
Artifacts are the default way CI systems preserve test output, and their weakness is friction plus expiry. Looking at one typically means opening a run page, downloading a zip, extracting it and opening a file, which is enough steps that most failures go uninvestigated. GitHub retains artifacts for 90 days by default, configurable between 1 and 90 days on public repositories and up to 400 on private ones.
The retention window quietly bounds how far back a team can reason. A question that requires a run from four months ago cannot be answered from artifacts under the default policy — not because anyone decided history was unimportant, but because nobody changed a default.
- The standard mechanism for preserving CI output, and the standard reason nobody reads it.
- Retention defaults bound how far back your team can investigate.
- Upload on failure explicitly — many pipelines skip the step exactly when it matters.
Related terms
See it in your own test results
Qualflare detects flaky tests, clusters failures by root cause, and scores release risk from the test results you already produce in CI. Start free.
Start free with Qualflare← Back to the testing & observability glossary.
Last reviewed September 9, 2026