Home/Docs/Team trends

Team trends

Point hotato team at a directory of run envelopes and get one honest trend: pass rate over time, pooled talk-over and time-to-yield, and the failure class your team hits most.

bash

# every run you keep is one JSON envelope
hotato run --suite barge-in --format json > runs/001.json
# ... more runs over days, branches, releases ...

# aggregate the directory into a trend + a self-contained HTML page
hotato team runs/ --html team.html --out agg.json

What it reports

Pass rate per run over time, plus a trend line in the HTML page. Rates are fractions: 1.00 means 8 of 8.
Mean, median, and p90 talk-over and time-to-yield, pooled across all events in all runs.
The most common failure class, so a recurring config knob surfaces by name.
Run order you control: --order mtime (default) uses file time; --order name makes a numeric filename prefix the explicit index.

What a run looks like

Real output, the bundled self-test battery scored twice:

terminal

$ hotato team runs/ --html team.html
hotato team: 2 runs from runs/ (ordered by mtime)
  events: 16 total
  pass rate: latest 8 of 8 (1.00), mean 1.00
  trend: 1.00 to 1.00 (flat) across 2 runs
  talk-over: mean 1.02s median 0.53s p90 2.29s (n=16)
  time to yield: mean 0.62s median 0.50s p90 1.01s (n=12)
  most common failure class: no failures

A trend of one point is a fabrication

Fewer than two runs is stated plainly and exits 0. Every aggregate pools real measurements from the envelopes; empty input returns null, never a padded number. p90 is linear interpolation (METHODOLOGY.md).

Where the envelopes come from

Anywhere you already run hotato: a nightly CI job appending to a directory, a per-branch artifact, or teammates scoring their own calls (capture guides). The suite gate (pytest plugin) and the PR check both emit the same envelope.