---
type: atlas-artifact
artifact_type: test-report
project: "{{project}}"
status: draft
owner: "{{owner}}"
created: {{date}}
updated: {{date}}
source: "{{source}}"
reviewer: "{{reviewer|TBD}}"
tags: [atlas, artifact, test-report]
---
# Test Report: {{title}}

Parent project: [[{{project}}]]
Source: {{source}}

## Scope

What was tested and what was excluded.

## Environment

- Host/platform:
- Branch/commit/version:
- Relevant config, with secrets redacted:

## Commands run

```bash
exact command
```

## Results summary

- Total:
- Passed:
- Failed:
- Skipped:
- Duration:

## Failures / flakes

| Test/check | Result | Notes | Follow-up |
|---|---|---|---|
|  |  |  |  |

## Evidence paths or logs

- `path/to/log-or-artifact`

## Interpretation

What the results mean for the release/project.

## Follow-up tasks

- [ ] Owner: ... Action: ...

## Test-report-specific review checklist

- [ ] Scope and exclusions are explicit.
- [ ] Commands and environment are reproducible.
- [ ] Failures/flakes have owners or rationale.
- [ ] Logs/evidence do not include secrets.

## Universal reviewer checklist

Before accepting this artifact, verify:

- [ ] Clear owner, status, date, source, and next action.
- [ ] Saved in the correct durable destination and named using the convention.
- [ ] Links back to the relevant project note and source task/issue/PR/session/incident.
- [ ] Claims are backed by evidence links, command output, or labeled assumptions.
- [ ] Risks, rollback, recovery, or revisit triggers are documented where relevant.
- [ ] No secrets, tokens, raw PII, private keys, or unredacted credentials are included.
- [ ] A new specialist can understand the artifact without rereading the whole chat.
