Feature request
Description the feature
The HTML report should render times (run start time, per-request timing, durations) in a human-readable format such as 2026-04-22 14:35:10 UTC and durations like 1.2s / 350ms, instead of raw ISO strings, epoch seconds, or unformatted floats.
Is your feature request related to a problem?
Yes. The current report is harder to skim — especially when sharing it with non-engineers or reviewing a run after the fact. Readers have to mentally parse timestamps/durations, and small differences (ms vs s) are easy to misread.
Do you have any suggestions on how to add this feature in scanapi ?
- Format timestamps in the Jinja/HTML template using a helper/filter (e.g.
strftime('%Y-%m-%d %H:%M:%S %Z')) and include the timezone.
- Format durations with a small helper that picks units (
ms under 1s, s otherwise, m Ns past 60s).
- Keep the raw ISO timestamp as a
title/tooltip attribute so the precise value is still available on hover.
Feature request
Description the feature
The HTML report should render times (run start time, per-request timing, durations) in a human-readable format such as
2026-04-22 14:35:10 UTCand durations like1.2s/350ms, instead of raw ISO strings, epoch seconds, or unformatted floats.Is your feature request related to a problem?
Yes. The current report is harder to skim — especially when sharing it with non-engineers or reviewing a run after the fact. Readers have to mentally parse timestamps/durations, and small differences (ms vs s) are easy to misread.
Do you have any suggestions on how to add this feature in scanapi ?
strftime('%Y-%m-%d %H:%M:%S %Z')) and include the timezone.msunder 1s,sotherwise,m Nspast 60s).title/tooltip attribute so the precise value is still available on hover.