qa-tester

Test website functionality, rendering, forms, and integrations across browsers.

10|2|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/mrhinkle/VibeCoding-a-Website --skill qa-tester-mrhinkle
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-tester
Source: https://github.com/mrhinkle/VibeCoding-a-Website/tree/main/.claude/skills/qa-tester
Command: npx skills add https://github.com/mrhinkle/VibeCoding-a-Website --skill qa-tester-mrhinkle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

A single, systematic quality gate that verifies whether a website is actually usable and ready for launch by uncovering functional, rendering, integration, accessibility, and performance failures that isolated audits miss.

Core Features & Use Cases

  • Comprehensive page rendering checks across viewport sizes and device types to detect blank pages, broken images, layout shifts, and console errors.
  • Cross-browser and mobile responsiveness testing for Chrome, Edge, Safari, and Firefox, including device-emulation steps and touch-target validation.
  • End-to-end form validation and delivery checks, third-party integration verification (analytics, embeds, email, payments), SSL/mixed-content inspection, and categorized severity reporting for blockers, critical, and minor issues.
  • Regression and post-update workflows to re-test changed features and confirm fixes without re-running full audits.

Quick Start

Run a full QA pass on https://staging.example.com and produce a categorized QA test report with reproduction steps and severity for each issue.

Frequently Asked Questions about qa-tester

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

FAQPage Schema
How do I run cross-browser QA testing on a staging website before launch?▼

Run a comprehensive QA testing pass on your staging URL to verify functionality, cross-browser rendering, and form validation across Chrome, Safari, Firefox, Edge, and mobile viewports. It generates a severity-classified report with reproduction steps for any uncovered issues.

What is included in a pre-launch website quality assurance check?▼

A pre-launch quality assurance check includes page rendering verification, console and network health inspection, SSL and mixed-content status validation, end-to-end form submission testing, and third-party integration verification for analytics or payment embeds.

Can I test form validation and third-party integrations without running a full website audit?▼

Yes, you can apply regression and post-update workflows to re-test changed features like form validation and third-party integrations. This confirms recent fixes without requiring you to re-run a full comprehensive website audit.

Does accessibility and performance testing work across different mobile viewports and device types?▼

Accessibility and performance testing works across mobile viewports and device types by applying device emulation steps and touch-target validation. This detects blank pages, broken images, layout shifts, and responsiveness failures across browsers.

What is the best way to categorize and report website testing failures found during a QA pass?▼

The best way to report website testing failures is through a categorized severity report that classifies issues as blockers, critical, or minor, while providing detailed reproduction steps for each detected functional or rendering failure.

Why do I need to verify SSL and mixed-content status during website QA testing?▼

You need to verify SSL and mixed-content status during QA testing to uncover integration and security failures that isolated audits miss, ensuring your website is actually usable and ready for launch without browser security warnings.