SpecTracer takes your Gherkin feature files as the source of truth and collates Unit, Integration, and E2E test results into a single, self-contained HTML report. Tech-stack agnostic.
Modern teams test across multiple layers — but visibility is fragmented. SpecTracer brings everything together.
Unit, integration, and E2E tests live in different directories (or repos). There is no single view of overall coverage — until now.
Teams unknowingly accumulate slow E2E tests instead of fast unit tests. The pyramid dashboard makes it obvious at a glance.
Hard to know if a specific business scenario is tested across all necessary layers. SpecTracer flags missing coverage per scenario.
Most reporting tools are tied to one framework (Allure for Java, Cypress Dashboard for Cypress). SpecTracer works with any stack.
Three steps from feature files to a rich HTML report.
Define your scenarios in standard .feature files with tags like @FC-42 that link to test results. Declare required layers with @require-unit.
Use any test framework — pytest, Jest, Cypress, Behave, anything that produces JUnit XML or Cucumber JSON. SpecTracer doesn't care what language you use.
Run uv run python build_pyramid.py. SpecTracer links tests to scenarios via shared tags and produces a single self-contained HTML report with five interactive sections.
Get a report generated in under a minute.
# Clone and install
git clone https://github.com/ampyard/spec-tracer.git
cd spec-tracer
uv sync
# Run your tests with JUnit/Cucumber output
uv run pytest tests/unit --junitxml=reports/unit.xml
uv run pytest tests/integration --junitxml=reports/int.xml
uv run behave features/ --format json -o reports/e2e.json
# Generate the report
uv run python build_pyramid.py
# Open report.html in your browserspectracer.config.json at your project root and just run the tool — no flags needed.
The generated report is a single self-contained HTML file with five sections.
The headline metric: Tested: X / Y (Z%). Per-feature breakdowns with green/amber/red thresholds. Designed for daily standups.
3-tier visualization of E2E / Integration / Unit with test counts, duration, and pass rates. Spot inverted pyramids instantly.
Searchable tree: Feature → Scenario → Layer results. Full Gherkin text, required layer status, and per-test pass/fail/skip.
Every failed test across all layers with feature/scenario context and expandable stack traces. One place to triage everything.
Progress, pyramid ratio, and E2E runtime checks with configurable thresholds. Visual indicators that make team health obvious.
Test results whose tags don't match any scenario. Catch orphaned or mis-tagged tests that would otherwise go unnoticed.
SpecTracer dogfoods its own reports — it processes its own test outputs to generate a self-report. Every feature is validated with real Gherkin scenarios and E2E tests before it ships.
Free to use, modify, and distribute. No restrictions.
Just a CLI run in CI producing a static HTML file. No databases, no servers, no setup.
Works with Python, Java, JavaScript, Go, — anything that outputs JUnit XML or Cucumber JSON.