dogfood

Detect bugs and usability issues in web applications through exploratory QA testing.

Updated May 9, 2026

Search Tags:#qa #browser automation #web testing #bug reporting #console errors #exploratory testing

Ready to run

npx skills add https://github.com/pmcdowall/hermes-skills --skill dogfood-pmcdowall

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/pmcdowall/hermes-skills/tree/main/dogfood
Command: npx skills add https://github.com/pmcdowall/hermes-skills --skill dogfood-pmcdowall

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams discover hidden defects in web applications by performing structured exploratory testing and collecting actionable evidence instead of relying on manual ad hoc checks.

Core Features & Use Cases

Exploratory Web Testing: Navigate applications, inspect pages, interact with controls, and validate user flows across different scenarios.
Bug Evidence Collection: Capture screenshots, console errors, reproduction steps, and expected versus actual behavior for clear defect reporting.
Use Case: QA teams can use this Skill to test a new web product release, identify broken workflows, and generate a prioritized bug report for engineering teams.

Quick Start

Use the dogfood skill to test the provided web application URL, find usability and functional issues, and create a structured QA report.

Frequently Asked Questions about dogfood

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

FAQPage Schema

How do I find bugs in web apps through exploratory testing?▼

Exploratory testing for web apps navigates pages, interacts with controls, and validates user flows to systematically uncover usability issues and broken workflows. It captures screenshots, console errors, and reproduction steps for structured defect reporting.

What's the best way to automate QA testing for web application releases?▼

Systematic QA testing for web application releases uses browser automation to inspect pages and validate navigation checks. It generates a prioritized bug report containing expected versus actual behavior and actionable evidence for engineering teams.

Can I capture console errors and screenshots during browser automation testing?▼

Yes, browser automation testing can capture console errors and screenshots during web app validation. It collects reproduction steps and documents expected versus actual behavior to create clear, reproducible defect reports for engineering.

Does exploratory web testing work for validating user flows and form submissions?▼

Exploratory web testing applies to validating user flows, navigation checks, and form testing in browser-based scenarios. It systematically interacts with application controls to identify functional defects and document usability issues.

Do I need browser automation tools for structured bug reporting?▼

Yes, structured bug reporting requires browser automation tools and evidence capture capabilities. These tools navigate web applications, collect defect documentation like reproduction steps, and output structured QA findings for engineering teams.

Why does systematic QA testing find hidden defects better than ad hoc checks?▼

Systematic QA testing finds hidden defects by performing structured exploratory testing and collecting actionable evidence, instead of relying on manual ad hoc checks. It validates complex user workflows and generates prioritized bug reports.