Reporting
Generate, consume, and enrich Ginkgo reports, console verbosity...
Install
npx skills add onsi/ginkgo --skill reporting -g -a claude-code -y- Repository
- onsi/ginkgo9.1k
- Category
- Engineering
- Updated
- 26d ago
- License
- MIT
- Context cost
- Lightabout 1,416 tokens
- Runs scripts
- No, instructions only
What it does
Generate, consume, and enrich Ginkgo reports, console verbosity (-v/-vv/--trace/--no-color/--succinct), machine-readable reports (--json-report/--junit-report with --output-dir/--keep-separate-reports), programmatic reporting nodes (ReportAfterEach, ReportAfterSuite, CurrentSpecReport), AddReportEntry with ReportEntryVisibility, and profiling (--cover/--race/--cpuprofile/--memprofile). Use when you need a report file, custom suite-level reporting, attaching data to a spec, controlling console output, or profiling a suite.
Reporting and profiling
How to produce reports and feed data into them. To read a failing report as an agent (the jq failure-diagnosis workflow), see ginkgo:debugging-failures. Docs: https://onsi.github.io/ginkgo/#generating-machine-readable-reports and https://onsi.github.io/ginkgo/#attaching-data-to-reports.
Console output
| Flag | Effect |
|---|---|
--succinct | Minimal (default when running multiple suites). |
| (none) | Normal, detail only for failed specs (default, single suite). |
-v | Full timeline for every spec; streams live in series. |
-vv | -v plus node > Enter/< Exit events and every failure (not just the primary). |
--trace | Full stack trace on every failure, not just panics. |
--no-color / GINKGO_NO_COLOR=TRUE | Disable color. |
--github-output | Format console output for GitHub Actions. |
In parallel (-p), -v/-vv timelines can't stream, the streams would interleave, so Ginkgo emits each spec's full timeline after that spec completes. → CI flags in ginkgo:ci.
Machine-readable reports
ginkgo -r --json-report=report.json --output-dir=./.reports
