testdrivertest-results-jsonlisted

<!-- Generated from test-results-json.mdx. DO NOT EDIT. --> ## Overview TestDriver automatically writes a JSON result file for each test case after it finishes. These files contain comprehensive metadata about the test run, including SDK and runner versions, infrastructure details, interaction statistics, and links to recordings. Result files are written to: ``` .testdriver/results/<testFile>/<testName>.json ``` For example, a test file `tests/login.test.mjs` with a test named `"should log in"` produces: ``` .testdriver/results/tests/login.test.mjs/should_log_in.json ``` <Note> Test names are sanitized for filesystem use — special characters are replaced with underscores and names are truncated to 200 characters. </Note> ## Enabling No configuration is required. The JSON files are written automatically by the TestDriver Vitest reporter plugin whenever tests run. ## JSON Schema Each result file is organized into logical groups: ### `versions` | Field | Type | Description | |---|---|---| | `versions.sdk` | `string \| null` | TestDriver SDK version (e.g. `"7.8.0"`) | | `versions.vitest` | `string \| null` | Vitest version used to run the test | | `versions.api` | `string \| null` | TestDriver API server version | | `versions.runnerBefore` | `string \| null` | Runner version at sandbox start | | `versions.runnerAfter` | `string \| null` | Runner version after auto-update | | `versions.runnerWasUpdated` | `boolean` | Whether the runner was auto-updated during provis