Report format

The report format tells the agent how to write test reports: the Markdown structure, the status vocabulary, and the artifact naming. It is one file, utils/format.md, global for every run of the project.

1. Open Extending → Report Format.
2. Edit the Markdown; changes save automatically.
3. If the project has no utils/format.md yet, click Create utils/format.md, it starts from the proven default.

Two parts are load-bearing, keep them:

• The **Status:** line of each report is parsed by the runner to set the run's result. Remove it and a passing test is recorded as BROKEN.
• The status definitions (PASSED, FAILED, SKIPPED, WARN, BROKEN) are the status vocabulary your reports and the Dashboard count from.
• The artifact naming ({test_name}/{test_name}_report.md, step_{n}.png) is how the app finds each test's report and screenshots.

Everything else, the sections, the wording, the level of evidence, is yours to tailor: the report contract.