skills.rest
zenbuapps
zenbuappsOFFICIAL
Explore all skills by this author →
GitHub

browser-tester

Analyze git diffs and run Playwright CLI tests with video and screenshot reports.

1|Updated Mar 6, 2026
Search Tags:#screenshots#playwright#ui-testing#browser-testing#test-automation#git-diff#video-recording
One-click install
npx skills add https://github.com/zenbuapps/zenbu-powers --skill browser-tester
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browser-tester
Source: https://github.com/zenbuapps/zenbu-powers/tree/main/skills/browser-tester
Command: npx skills add https://github.com/zenbuapps/zenbu-powers --skill browser-tester

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Git diff driven browser-based testing workflow: analyze code changes, map impact scope across pages and components, and automatically run browser tests with Playwright CLI, capturing videos and screenshots and generating a comprehensive test report.

Core Features & Use Cases

  • Analyze git diffs to identify affected pages, components, and user flows.
  • Execute deterministic browser tests using Playwright CLI, recording videos, taking screenshots, and producing a test report.
  • Facilitate CI/local validation by generating a shareable report that communicates test results to developers and QA.

Quick Start

Run the browser-tester skill to analyze the diff, map affected pages, and execute Playwright tests to produce videos, screenshots, and a final report.

Frequently Asked Questions about browser-tester

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

FAQPage Schema
How do I automate browser tests based on git diff changes?▼

Automating browser tests from git diffs involves analyzing code changes to map impacted pages and components, then executing Playwright CLI tests to capture videos and screenshots before generating a final test report.

Can I run Playwright CLI tests locally and capture screenshots and video recordings?▼

Playwright CLI tests can run in both CI and local environments to capture screenshots, record videos, and produce a test report. Test outputs are saved directly to the output/playwright/browser-test directory.

Do I need a Playwright CLI setup to run automated UI testing from code changes?▼

A Playwright CLI setup is required to execute automated UI testing. The testing workflow applies to frontend projects where code changes touch UI elements, components, or routes.

What is the best way to map impact scope across pages and components after a git commit?▼

Mapping impact scope after a git commit requires analyzing the diff to identify affected frontend pages, components, and user flows, which then determines which browser tests to execute.

Why use git diff driven browser testing instead of running the full test suite?▼

Git diff driven browser testing targets only the pages and components affected by recent code changes, reducing test execution time while still capturing videos, screenshots, and generating a comprehensive report.

Does automated browser testing work for frontend projects with route changes?▼

Automated browser testing works for frontend projects where changes touch UI, components, or routes. The workflow analyzes the diff, maps the impact scope, and runs Playwright tests accordingly.

Related Skills

Explore More Software Engineering Skills→
SantiagoisperSantiagoisper

ce-test-browser

Automate end-to-end browser tests for web pages affected by code changes.

Community
Advanced
ai-ecoverseai-ecoverse
28

playwright-cli-e2e

Execute a 12-group end-to-end regression suite for playwright-cli and diff results against a baseline.

Official
Intermediate
tedtv1007-ctrltedtv1007-ctrl

playwright-testing

Automate browser-based end-to-end testing with Playwright.

Community
Advanced
htooayelwinicthtooayelwinict

testing

Automate TDD workflows across Pest, Vitest, and Playwright test layers.

Community
Advanced