Install any skill in seconds. Free to start, no credit card required.
Get Started Free →testdriverai/testdriver:debugging-with-screenshots
Diagnose failing tests with screenshots, replays, and logs
Passed 11 of 16 test cases with the skill, and 2 of 16 without it.
and 14 more in the full report
13 fixed3 passed either way7 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
When `list_local_screenshots()` is executed without specifying a `sortBy` option, in what order are the screenshots returned by default?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies modification timestamp with newest first as the default sort order. | Missed | Passed |
The instructions your model reads when the skill loads.
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.
List and filter screenshots saved in the .testdriver/screenshots/ directory:
list_local_screenshots()
Filter Parameters:
test cases passed, vs 2 / 16 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.