testdriverdebugging-with-screenshotslisted

<!-- Generated from debugging-with-screenshots.mdx. DO NOT EDIT. --> ## Overview When a test fails, debug it. Look at what happened. Do not guess. TestDriver captures screenshots, video replays, and logs while your test runs. Thus you can replay the moment of the failure. You do not need to look at a stack trace. TestDriver MCP gives commands to view and examine the screenshots that TestDriver saved during the test. This lets you debug quickly, develop tests, and compare, without a manual open of image files. <Note> **Automatic Screenshots (Default: Enabled)**: TestDriver captures screenshots automatically before and after each command. The screenshot name has the line number and the action. Thus it is easy to see which line of code made 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 the screenshots by test file or subdirectory (for example, "login.test", "mcp-screenshots"). If you do not give this, the tool lists all screenshots. </ParamField> <ParamField path="line" type="number" optional> Filter by the exact line number from the test file (for example, 42 matches L42 in the filename). </ParamField> <ParamField path="lineRange" type="object" optional> Filter by a line number range. Example: