testdriver:screenshot

Capture screenshots during test execution and store them by test file.

238|34|Updated Aug 25, 2024
One-click install
npx skills add https://github.com/testdriverai/testdriverai --skill testdriver-screenshot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testdriver:screenshot
Source: https://github.com/testdriverai/testdriverai/tree/main/ai/skills/testdriver%3Ascreenshot
Command: npx skills add https://github.com/testdriverai/testdriverai --skill testdriver-screenshot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture screenshots during automated test execution to provide visual context for debugging UI failures and regressions.

Core Features & Use Cases

  • Automated screenshot capture at key moments during test runs to document UI state.
  • Screenshots organized by test file under .testdriver/screenshots for easy navigation and review.
  • Automatic cleanup of per-test-file screenshots at the start of each run to keep outputs clean.
  • Useful for sharing evidence with teammates and for troubleshooting flaky tests in CI environments.

Quick Start

Run your tests with TestDriver to automatically generate and save screenshots for each test file.

Frequently Asked Questions about testdriver:screenshot

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I capture screenshots automatically during automated test execution?

You can capture screenshots automatically during automated test execution by running your tests with TestDriver. It saves images under .testdriver/screenshots organized by test file name to document UI state.

How are screenshots organized when saving visual evidence for debugging UI failures?

Screenshots for debugging UI failures are organized by test file name under the .testdriver/screenshots directory. This structure keeps visual evidence grouped for easy navigation and review.

Does TestDriver clean up old screenshots at the start of each test run?

Yes, TestDriver automatically cleans up per-test-file screenshots at the start of each run. This automatic cleanup keeps your screenshot outputs clean and prevents stale images from accumulating.

Can I use automated screenshot capture to troubleshoot flaky tests in CI environments?

Yes, automated screenshot capture is useful for troubleshooting flaky tests in CI environments. It provides visual context of the UI state during execution, which helps identify intermittent failures.

What pages and scenarios are supported for capturing UI state during test runs?

Screenshot capture supports UI-driven test suites for pages such as login, checkout, and error scenarios. It documents the UI state at key moments during these test runs to provide visual context.

Do I need a specific project structure to save test screenshots locally?

Yes, you need a local project structure to store images under .testdriver/screenshots/<test-file-name>/. This requires TestDriver's screenshot API to save the visual evidence correctly.