Reporters¶
Tryke supports multiple output formats via the --reporter flag.
text (default)¶
The default reporter. Shows each test result with pass/fail status, discovered expectation lines, assertion diagnostics on failure, and a summary at the end.
dot¶
Compact single-character output — one character per test. Useful for large suites where you only want to see failures:
.passFfailEerrorsskipTtodoxxfailXxpassed (anxfailtest that passed unexpectedly)
json¶
Machine-readable JSON output. Each test result is a JSON object, one per line (JSONL format). Useful for integrating with other tools or custom dashboards.
junit¶
JUnit XML output for CI systems that consume JUnit reports (Jenkins, GitHub Actions, etc.):
llm¶
A format optimized for consumption by large language models. Concise, structured output designed to fit in LLM context windows.
next¶
A cargo-nextest-style reporter. One line per completed test with a status badge, duration, and file_stem :: test_name identifier; a live status bar at the bottom of the terminal tracks progress through the run.
The live status bar is drawn at the bottom of the terminal and only appears when both stdout and stderr are TTYs, so redirecting output to a file or piping into another command produces clean per-test lines with no escape codes.
sugar¶
A pytest-sugar-style reporter. One line per test file showing inline check/cross marks for each test in the file, plus a count, percentage, and a small bar on the right. Failures are deferred to a recap at the end of the run, so the per-file output isn't interrupted.
Like next, the live status bar is only drawn when both stdout and stderr are TTYs; redirecting either falls back to plain per-file lines with no escape codes.
Using reporters with other modes¶
The --reporter flag works with watch mode too: