TableTest Reporter — Specification

Report rendering
- Cell rendering
  - A cell is published in the notation it was written in
  - A pipe inside a value is escaped so it cannot end the cell
- Page footer
  - Every page records when the report was generated
  - Falls back to plain attribution without a timestamp
Available output formats
- Available formats are the three built-ins plus any custom templates, sorted
Output format discovery
- A custom format is discovered only when both its table and index templates are present
Pass/fail rollup
- A feature's status is summed bottom-up from its children
- A table's status is derived from its executed row results
Relative links
Report timestamp
- States the run timestamp in utc
Significant whitespace
- Whitespace is significant at line edges, in runs, and in tabs
The indexDepth option
Whitespace markers
- Significant whitespace runs are wrapped in marker spans
Whole-report search
- Search finds pages whose title or text contains the query

TableTest Reporter — Specification
Relative links

Relative links

All 13 scenarios passing

Every link in a report is relative — never root-absolute — so a generated report works from any directory: a local folder, a web server root, or a subpath like GitHub project Pages. The example pages are a feature "boolean-logic" holding tables "and-op" and "or-op".

Every page has a single root-relative path
Links are relative to the linking page's own directory
Shared assets are reached by climbing to the output root

Generated by tabletest-reporter · 20 Aug 2026 07:15 UTC