Recorded evidence
The task is one story. The reports should agree.
Review control-panel, service and device reports together. Check the intended asset, completion window and assets that must stay unchanged.
Start with recorded evidence
Follow one task across the reports.
Import supported JSON or MCAP task reports. Compare control-panel, service and device states for the same task, and inspect the source events behind each finding.
Open recorded evidence Recording formats and setup docsSimulated task reports
Robot A must finish within 10 seconds.
Robot B must stay unchanged.
- Control panel
- Completed6.5 s
- Task service
- Accepted1.2 s
- Robot A report
- No completion recorded
Robot B changed to the requested task.
Reports do not meet the requirement
Times are from the recording start. This example uses the app’s evaluator.
Files stay in your browser. A device report does not prove what physically happened. Live device connections are not available.
The comparison
Define the requirement. Inspect the evidence.
Captured intervals matter as much as recorded states. A missing report can leave the result inconclusive.
01 / Define the requirement
- Intended asset
- Robot A
- Task
- task-104
- Completion window
- 10 seconds
- Keep unchanged
- Robot B
02 / Bring the captured reports
- Control panelRequested and displayed state
- Task serviceAccepted and reported state
- Device reportRecorded device state
03 / Compare against the requirement
Same task. Intended asset. Declared coverage.Check source events on a shared timestamp basis, within the captured intervals.
What the beta reviews
Look past a successful status.
Conflicting reports
Find when the control panel reports completion while captured device evidence does not support it.
The wrong asset
Compare the requested task and intended asset, including assets whose recorded state must remain unchanged.
Missing evidence
Keep absent reports and uncovered intervals visible. An unobserved period cannot establish success.