browse

Automate QA browser testing with Playwright and headless Chromium.

Updated Aug 23, 2026

Search Tags:#debugging #qa #playwright #e2e-testing #browser-automation #visual-verification

Ready to run

npx skills add https://github.com/mariasebarespersona/Tum-AI --skill browse-mariasebarespersona

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/mariasebarespersona/Tum-AI/tree/main/.claude/skills/browse
Command: npx skills add https://github.com/mariasebarespersona/Tum-AI --skill browse-mariasebarespersona

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA teams often struggle to validate UI behavior across real browsers and catch visual regressions during development and deployment. This skill provides real-browser automation to observe user interactions, capture screenshots, and report issues automatically.

Core Features & Use Cases

Real browser sessions with Playwright headless Chromium for accurate UI testing.
End-to-end test patterns: start browser, navigate, interact, verify, and report with screenshots.
Visual QA and post-deploy verification to ensure UI integrity after releases.
Example Use Case: validate login flow and ensure layout stability across pages after a new build.

Quick Start

Start a Playwright browser session and run the provided E2E tests against the target web application.

Frequently Asked Questions about browse

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

FAQPage Schema

How do I automate E2E testing with Playwright and real Chromium?▼

Automate E2E testing by controlling a real Chromium browser via Playwright to execute deterministic interactions, verify UI behavior, and capture screenshots. It requires Node.js and a target URL configuration to run post-deployment checks.

Can I use this for visual QA and post-deployment verification of web apps?▼

Yes, visual QA and post-deployment verification are core use cases. The skill validates UI integrity after releases by observing real user interactions and automatically capturing screenshots to report visual regressions.

What do I need to start running headless Chromium browser automation for QA?▼

You need Playwright, Node.js, and a target URL configuration. These dependencies allow the skill to start a real browser session, navigate web applications, and perform deterministic interactions for testing.

Does this skill support screenshot reporting for UI testing?▼

Yes, screenshot reporting is supported. The skill captures screenshots during browser automation to report visual issues and layout instability, ensuring UI behavior is validated accurately across pages after a new build.

What's the best way to validate a login flow and ensure layout stability?▼

Validate a login flow by starting a Playwright browser session to navigate, interact, and verify the UI. The skill automatically captures screenshots to check layout stability and ensure the authentication process behaves deterministically.