testdriverdebugging-with-screenshotslisted

<!-- Generated from debugging-with-screenshots.mdx. DO NOT EDIT. --> ## Overview When a test fails, debug it by seeing exactly what happened — don't guess. TestDriver captures screenshots, video replays, and logs as your test runs, so you can replay the moment of failure instead of squinting at a stack trace. TestDriver MCP provides powerful commands to view and analyze the screenshots saved during test execution, enabling rapid debugging, test development, and comparison workflows without manually opening image files. <Note> **Automatic Screenshots (Default: Enabled)**: TestDriver automatically captures screenshots before and after every command. Screenshots are named with the line number and action, making it easy to trace exactly which line of code produced each screenshot. For example: `001-click-before-L42-submit-button.png` </Note> ## MCP Commands ### list_local_screenshots List and filter screenshots saved in the `.testdriver/screenshots/` directory: ``` list_local_screenshots() ``` **Filter Parameters:** <ParamField path="directory" type="string" optional> Filter screenshots by test file or subdirectory (e.g., "login.test", "mcp-screenshots"). If omitted, lists all screenshots. </ParamField> <ParamField path="line" type="number" optional> Filter by exact line number from test file (e.g., 42 matches L42 in filename). </ParamField> <ParamField path="lineRange" type="object" optional> Filter by line number range. Example: `{ start: 10, end: 20 }` match