Generate Test Recording Report
test-record-reportTurn recorded test steps into a formatted markdown report with screenshots, assertions, and summary totals. Use it to document and share test results.
Instructions
test-record-report
Generate a markdown report from a recorded test session created by test-record-step.
What it does
Reads the session's steps.json and produces a structured report.md file:
Header with test name, date, step count, and duration
Per-step sections with screenshot image links, assertions, metadata, and element counts
Summary section with totals
The report is written to <recordingsRoot>/<sessionName>/report.md and also returned
in the response for immediate consumption.
Parameters
sessionName (string, required): Session name matching prior test-record-step calls
testName (string, optional): Title for the report (defaults to sessionName)
Returns
JSON with { sessionName, testName, reportPath, stepCount, markdown }
plus guidance. Throws McpError InvalidRequest if session or steps are missing.
Examples
Basic report
await testRecordReportTool({ sessionName: "login-flow" })Named report
await testRecordReportTool({
sessionName: "login-flow",
testName: "Login Flow — Happy Path"
})Typical Workflow
test-record-step({ sessionName: "my-test", label: "App launched" })test-record-step({ sessionName: "my-test", label: "Login tapped", assertion: "Login form visible" })test-record-step({ sessionName: "my-test", label: "Logged in", metadata: { user: "test@example.com" } })test-record-report({ sessionName: "my-test", testName: "Login Flow" })
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| testName | No | Report title (defaults to sessionName) | |
| sessionName | Yes | Recording session name |