Test Artifacts¶
What are these files?
Outputs from test run (kept under artifacts/test/
to avoid polluting the repo root).
- junit.xml — produced by
pytest --junit-xml
- htmlcov/ — produced by
coverage.py
via--cov-report=html
- benchmarks/ — created when
pytest-benchmark
is available andENABLE_BENCH=1
- hypothesis/ — Hypothesis DB via
HYPOTHESIS_DATABASE_DIRECTORY
Files & what they’re for
-
junit.xml — JUnit-style test report (pytest).
- Good: 0 failures / 0 errors; all tests passed. — 0 tests; 0 failures; 0 errors; 0 skipped
- How to use: Feed to CI/badges; inspect failing tests and timings.
-
htmlcov — HTML coverage report (coverage.py).
- Good: Meets coverage threshold; no critical files missing. — coverage % unavailable
- How to use: Open the HTML report; set/validate a coverage threshold in CI.
junit.xml¶
About this artifact
What it is: JUnit-style test report (pytest). What good looks like: 0 failures / 0 errors; all tests passed. Summary: total 0, failures 0, errors 0, skipped 0, time ~0.00s
htmlcov¶
About this artifact
What it is: HTML coverage report (coverage.py). What good looks like: Meets coverage threshold; no critical files missing. Open HTML coverage report