playwright-evidence

Generate Playwright test reports and upload evidence to Google Drive.

1|Updated Apr 21, 2026
One-click install
npx skills add https://github.com/devbasex/ai-plugins --skill playwright-evidence-devbasex
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: playwright-evidence
Source: https://github.com/devbasex/ai-plugins/tree/main/plugins/playwright-kit/skills/playwright-evidence
Command: npx skills add https://github.com/devbasex/ai-plugins --skill playwright-evidence-devbasex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After running Playwright E2E tests, teams need a shareable report and a safe place to store bulky evidence like videos, traces, and HAR files. This Skill automates report generation and Google Drive archival so results can be shared with the team without manual file handling. ## Core Features & Use Cases - Automatic report generation: A pytest hook produces reports/<run-id>/report.md with a summary table, failure details, body_check violations, and evidence links after every test run. - Drive upload workflows: Upload evidence automatically at session end via --pwk-drive-folder, or manually with scripts for single files, recursive directory mirroring, and Markdown-to-Google-Docs conversion with embedded Drive links. - Trace Viewer integration: Publicly uploaded trace.zip files get a trace.playwright.dev URL so anyone can replay traces in a browser without installing Playwright. - Use Case: After running ./scenario-test/run.sh, mirror the whole reports/<run-id>/ folder to a private Drive folder, convert report.md into a Google Doc with clickable evidence links, and share the Doc URL on Slack. ## Quick Start Run the Playwright scenario tests with a Drive folder specified, then ask the AI to convert the generated report into a Google Doc with embedded evidence links and share it with the team.

Frequently Asked Questions about playwright-evidence

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

FAQPage Schema
How do I upload Playwright test evidence to Google Drive?▼

Pass --pwk-drive-folder=<FOLDER_ID> to the test run script for automatic upload at session end, or run the gdrive_upload_dir.py script manually to mirror a local reports directory to Drive while preserving its folder structure.

How to convert a Markdown test report to Google Docs?▼

Use the upload_md_as_gdoc.py script with the report path, parent folder ID, and document name. For reports with evidence links, build_gdoc_with_drive_links.py rewrites trace and file references to Drive URLs before converting.

Can I view a Playwright trace without installing Playwright?▼

Yes. Upload trace.zip with the --public flag to get a trace.playwright.dev URL that replays the trace in any browser. Note this grants anyone-read access, so avoid it when traces contain cookies or credentials.

Why does Drive upload fail with a 403 insufficient permissions error?▼

The OAuth2 token lacks the drive.file scope. Re-authenticate through the google-auth skill specifying the drive.file scope, or set the GOOGLE_AUTH_SCRIPTS environment variable if the skill is not installed.

What security risks exist when uploading Playwright traces and HAR files?▼

trace.zip and HAR files can contain cookies, localStorage, Basic Auth credentials, and request bodies. Upload only to private Drive folders shared with trusted parties, and avoid the --public flag for sensitive runs.