qa-browser

Performs runtime testing of live web apps via Chrome DevTools Protocol.

1|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/dev-gios/agent-teams-qa --skill qa-browser
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-browser
Source: https://github.com/dev-gios/agent-teams-qa/tree/main/skills/qa-browser
Command: npx skills add https://github.com/dev-gios/agent-teams-qa --skill qa-browser

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill identifies runtime issues in live web applications that are invisible to static code analysis, ensuring a robust and user-friendly experience.

Core Features & Use Cases

  • Dynamic Testing: Connects to a live URL to simulate user interactions and uncover errors.
  • Comprehensive Audits: Checks for console errors, network failures, accessibility violations, unresponsive elements, layout issues, and performance bottlenecks.
  • Use Case: Before deploying a new feature, use this Skill to test the live staging environment, catching critical JavaScript errors or broken API calls that could impact users.

Quick Start

Use the qa-browser skill to test the live application at https://example.com.

Frequently Asked Questions about qa-browser

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

FAQPage Schema
How do I find runtime JavaScript errors and network failures in a live web application?

Dynamic runtime testing connects to a live web application via Chrome DevTools Protocol to identify JavaScript errors and network request failures. It performs console audits and network health checks to uncover hidden runtime issues.

Can I check my web application for WCAG accessibility violations automatically?

Yes, you can check web application accessibility using axe-core WCAG compliance audits. Dynamic runtime testing connects to live URLs to identify accessibility violations and validate interactive elements automatically.

How do I measure Core Web Vitals and performance bottlenecks in a staging environment?

Runtime analysis measures Core Web Vitals and identifies performance bottlenecks by connecting to live staging environments. It simulates user interactions to catch performance issues and unresponsive elements before deployment.

Does runtime testing detect responsive layout issues across different viewport sizes?

Yes, runtime testing includes responsive layout validation to detect layout issues. By connecting via Chrome DevTools Protocol, it scopes live web applications to ensure responsive design integrity across viewports.

What is the difference between dynamic runtime testing and static code analysis for web apps?

Dynamic runtime testing identifies live web application issues invisible to static code analysis. It connects to active URLs via Chrome DevTools Protocol to find real-time JavaScript errors, network failures, and accessibility violations.

Do I need Chrome DevTools Protocol to perform network health checks and console audits?

Yes, Chrome DevTools Protocol is required to perform network health checks and console audits. It enables the connection to live web applications needed to identify runtime errors and measure Core Web Vitals.