exploratory-web-qa

What problem does it solve?

Manual exploratory QA testing for web applications is often inconsistent, incomplete, and lacks standardized evidence tracking, making it hard to reproduce bugs and share clear, actionable findings with development teams.

Core Features & Use Cases

• Structured 5-phase workflow: Guides testers through planning, exploration, evidence collection, issue categorization, and report generation to ensure no critical testing gaps.
• Automated evidence capture: Integrates with browser tools to take annotated screenshots, log JavaScript console errors, and record step-by-step reproduction details for every issue found.
• Standardized bug reporting: Uses a pre-built report template and issue taxonomy to classify bugs by severity and category, producing clear, prioritized reports for stakeholders. Use case: Before launching a new e-commerce checkout flow, use this skill to run end-to-end exploratory tests, catch broken form validation, visual glitches, and console errors, and share a prioritized bug report with your engineering team.

Quick Start

Use the exploratory-web-qa skill to test the web app at https://your-store.com and save the final bug report to the ./qa-output folder.