qa_survey

Automate browser-based QA surveys across Runbook user roles and generate recommendations.

Updated Feb 19, 2026
One-click install
npx skills add https://github.com/wesuuu/runbook --skill qa-survey
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa_survey
Source: https://github.com/wesuuu/runbook/tree/main/.agent/skills/qa_survey
Command: npx skills add https://github.com/wesuuu/runbook --skill qa-survey

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Surveying the app across multiple user roles in a reproducible, browser-based QA workflow to identify issues and produce a recommendations document.

Core Features & Use Cases

  • Cross-user testing: Validate authentication, navigation, and permissions for admins, editors, and viewers.
  • UI flow verification: Exercise key pages (projects, protocol editor, runs, settings) to surface defects and gather improvement notes.
  • QA report generation: Compile findings into a structured QA recommendations document.

Quick Start

Run the QA survey across the running app to generate a QA recommendations document for multiple user roles.

Frequently Asked Questions about qa_survey

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

FAQPage Schema
How do I automate browser QA surveys across different user roles?

Browser UI testing for web apps verifies key pages like projects, protocol editors, runs, settings, and exports. This Skill exercises these UI flows across multiple user roles to surface defects and gather improvement notes for a final report.

How do I generate a structured QA report for a web app?

To generate a QA report, you must run this Skill against a running local frontend and backend environment. It requires Chrome browser automation tools to execute end-to-end tests and automatically compile the findings into a structured document.

Do I need a running local frontend and backend to run end-to-end tests?

This Skill is designed for comprehensive end-to-end testing of web apps, specifically targeting authentication, navigation, and permission validation across admin, editor, and viewer roles rather than isolated unit testing.

What is the best way to test protocol editing and runs across user permissions?

Browser automation for QA surveys validates permissions by exercising UI flows for admin, editor, and viewer roles. It specifically tests access to projects, protocol editing, runs, settings, and exports to identify permission defects.

Can I use this for testing web app exports and settings pages?

Yes, you can test web app exports and settings pages. This Skill automates browser QA workflows that explicitly exercise these pages across different user roles to identify issues and compile the results into a QA report.