HTML, PDF & Excel Reports - Step-Level Traceability on Every Test Run
Every agent response logged, timestamped, and linked to its test case. Export to HTML for sharing, PDF for audit, Excel for analysis - automatically after every run.
OVERVIEW
A test result without a trace is not evidence. Saying a test passed tells you the outcome. Knowing which agent sent which frame at what timestamp, what the device responded, and whether that response matched the expected value at the step level - that is the evidence that supports firmware release decisions, satisfies ISO 26262 Part 8 requirements, and gives the QA lead confidence to sign off.
TestBot generates three report formats automatically after every test run, with no configuration required. The HTML report is interactive - expand any test case to see its full step log. The PDF report is static and audit-ready, with a summary table, pass/fail status for every test case, and a complete step trace appendix. The Excel report is data-analyst friendly - filter by agent, by result, by timestamp, or by test ID in a tool you already use.
All three formats are written to a configurable output directory and published as CI/CD build artefacts automatically when TestBot runs in a pipeline.
Three Formats, One Run, Zero Extra Configuration
Every TestBot execution generates all three formats automatically.
HTML Report - Interactive
The default report format. Opens in any browser. Collapsible test case tree, step-level log for every agent action, timestamps, pass/fail badges, and screenshots where visual agents are used. Link-shareable across the team - no test tool installation needed to read it.
PDF Report - Audit Ready
Static, printable, and suitable for submission to quality management systems. Includes an executive summary page, test case pass/fail table, full step-level trace appendix, agent configuration snapshot, firmware version under test, and execution timestamp. Accepted by ISO 26262 and IEC 62304 auditors as test evidence.
Excel Report - Data Analyst Friendly
Structured tabular data - one row per test step. Filter by agent type, pass/fail status, timestamp range, or test case ID in Excel or Google Sheets. Pivot tables for defect distribution analysis. Import into your QMS or custom dashboard without parsing HTML.
Step-Level Trace - What Every Report Contains
Every agent action and device response is captured with full context.
| Parameters | Description |
|---|---|
| Timestamp | Exact time of every agent action and device response, to millisecond precision. |
| Agent Name | Which agent generated the step - CAN, UDS, BLE, Modbus, I/O Module, AI Vision, etc. |
| Action / Block | The test block that was executed - e.g. 'UDS ReadDataByIdentifier', 'CAN Send Frame', 'BLE Write Characteristic'. |
| Sent Data | Raw payload sent by the agent - CAN frame bytes, UDS request PDU, Modbus function code + register values, etc. |
| Received Data | Raw device response - CAN response frame, UDS positive/negative response, GATT notification value, etc. |
| Expected Value | The pass criterion defined in the test case - the value the response was compared against. |
| Result | PASS or FAIL for the step, with the delta between expected and actual values on failure. |
| Screenshots | For AI Vision and Web Browser agents - pixel-accurate screenshots of the display or browser state at the moment of assertion. |
Who Uses Each Report Format and Why
| Role | Report Used | Purpose |
|---|---|---|
| QA Engineer | HTML | Review overnight regression results in the browser, drill into failed test steps to identify root cause |
| Engineering Manager | HTML summary / PDF cover page | Pass/fail dashboard for the sprint; attach to release decision email |
| Compliance Engineer | Submit as ISO 26262 Part 8 / IEC 62304 test evidence to quality management system | |
| CI/CD Pipeline | All 3 formats | Archive as build artefacts; JUnit XML triggers pass/fail gate on merge request |
| Data Analyst / QA Lead | Excel | Pivot defect distribution by agent type, test ID, and firmware version across 30-day build history |
| Customer / Auditor | Receive evidence package showing all test cases executed, all results, and full step trace for critical items |
Frequently Asked Questions - TestBot Reporting
Reports are generated automatically after every test run with no configuration required. TestBot writes HTML, PDF, and Excel files to a configurable output directory. The directory path is set once in the project configuration and applies to all subsequent runs.
RELATED PAGES
See a Real TestBot Report
Book a demo and we will run a live test suite against hardware and show you the HTML, PDF, and Excel output.