## TL;DR

Allure shows nothing when it cannot find the results directory. Point the report step at the right results path, ensure the test step actually wrote results, and persist history between runs for trends.

## Error

```text
Allure report: No test data found in allure-results
```

## Steps

1. Check the test step wrote to `allure-results`: list the directory after tests. Expected: JSON files present.
2. Fix the path in the report command: `allure generate allure-results -o allure-report`. Expected: paths match.
3. Ensure artifacts upload/download between jobs preserves the directory. Expected: the report job sees the files.
4. Persist `history/` from the previous report for trends. Expected: history carries over.
5. Re-run and open the report. Expected: tests listed.

## When to use

- Empty Allure report in CI, works locally.
- Multi-job pipelines.

## When not to use

- Results exist but render wrong (report version issue).
- You want a different reporter entirely.

## Tool compatibility

- Allure 2.x; any test framework with an Allure adapter.

## Variant phrasings

### Allure empty report CI

Path or artifact problem; check both.

### allure-results not found

The test step did not write them, or the path is wrong.

## Why it happens

Allure is two steps: tests write results, the reporter reads them. CI splits steps across jobs, and paths or artifacts break between them.

## Edge cases

- Adapters must match the framework version; mismatches write nothing silently.
- History needs write-back to storage; read-only artifact stores break trends.
- Parallel runs need merged results before generation.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_W_dzQZdxZDNHYNtnFACpTQ