browser-qa

Automate browser-based QA with Playwright for end-to-end verification.

2|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/DojoCodingLabs/GTM-Engineering-Command-Center --skill browser-qa-dojocodinglabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser-qa
Source: https://github.com/DojoCodingLabs/GTM-Engineering-Command-Center/tree/main/skills/browser-qa
Command: npx skills add https://github.com/DojoCodingLabs/GTM-Engineering-Command-Center --skill browser-qa-dojocodinglabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The GTM agent can see, interact with, and verify real browser experiences, enabling QA of tracking, signup flows, and blockers that have no API path.

Core Features & Use Cases

  • Verify Meta Pixel fires, PostHog events, and network requests across browser interactions.
  • Visual verification through screenshots, DOM inspection, and performance checks.
  • Test full signup/checkout flows end-to-end and handle UI blockers that block automation.
  • Verify mobile responsiveness and performance metrics across viewport sizes.
  • Inspect live DOM, console errors, and performance data to detect issues.

Quick Start

Run an automated browser QA workflow on the target page to verify pixel events, analytics, and a signup flow using Playwright.

Frequently Asked Questions about browser-qa

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

FAQPage Schema
How do I verify Meta Pixel and PostHog events during an automated signup flow?

Verify Meta Pixel and PostHog events during automated signup flows by using Playwright-driven browser automation to interact with pages and inspect network requests. This confirms tracking fires correctly across full end-to-end browser interactions without requiring API paths.

What is the best way to automate visual testing and DOM inspection for web experiences?

Automate visual testing and DOM inspection through autonomous browser QA that captures screenshots, inspects live DOM elements, and checks console errors. This detects visual discrepancies and frontend issues across targeted viewport sizes.

Can I use Playwright to test mobile responsiveness and performance metrics?

Playwright automates browser QA to test mobile responsiveness and performance metrics by simulating various viewport sizes. It inspects live performance data to detect rendering issues and ensure web experiences adapt correctly across screen dimensions.

How do I handle UI blockers that interrupt automated end-to-end browser testing?

Handle UI blockers during automated end-to-end testing by applying Chrome DevTools MCP integration and Computer Use as a fallback. These structured patterns resolve blockers that prevent automation when standard browser interactions are insufficient.

Does autonomous browser QA work for checkout flows where APIs are insufficient?

Autonomous browser QA works for checkout flows by driving real browser experiences to validate end-to-end processes. It verifies complete flows and tracking where APIs are insufficient, using visual checks and error detection to ensure functionality.