dogfood

Name: dogfood
Availability: InStock
Author: aissenliu

Automate exploratory QA testing of web applications and generate markdown bug reports.

Updated Apr 27, 2026

Search Tags:#automation #workflow #qa #evidence #browser #bug-report #exploratory-testing

Ready to run

npx skills add https://github.com/AissenLiu/EasyHermes --skill dogfood-aissenliu

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Systematic exploratory QA testing of web applications to uncover bugs early, capture evidence, and generate structured reports.

Core Features & Use Cases

Phase-based workflow including Plan, Explore, Collect Evidence, Categorize, and Report.
Prerequisites: browser toolset (e.g., browser_navigate, browser_snapshot, browser_click, browser_type, browser_vision, browser_console, browser_scroll, browser_back, browser_press), a target URL, and a defined testing scope.
Typical Use Cases: perform end-to-end exploratory testing on internal or public web apps, log issues with steps, screenshots, and a final report.

Quick Start

Initiate a dogfood QA run on your target web application to produce a structured bug-report with evidence.

Frequently Asked Questions about dogfood

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

FAQPage Schema

How do I automate exploratory testing to find bugs in my web application?▼

Automated exploratory testing uses a browser toolset to systematically navigate web applications, test interactions, and capture bug evidence. It follows a structured workflow to plan, explore, collect evidence, categorize, and generate a markdown report.

What is the best way to capture bug evidence during browser QA?▼

Capturing bug evidence during browser QA involves using browser tools to take screenshots, log console errors, and record interaction steps. This evidence is categorized and compiled into a structured markdown report for developer review.

Do I need a specific browser toolset for automated web app QA?▼

Automated web app QA requires a browser toolset with navigation, snapshot, click, type, and console access capabilities. You also need a target URL and a defined testing scope to execute the exploratory workflow successfully.

Can I use systematic exploratory testing for edge cases and forms?▼

Systematic exploratory testing applies to edge cases, forms, and interactions across any web app pages. The browser toolset executes predefined test actions to uncover unexpected behaviors and logs them with structured evidence.

What limitations exist when automating bug reports with a browser toolset?▼

Automating bug reports with a browser toolset requires a predefined testing scope and target URL. It relies on browser actions like clicking and typing, meaning it cannot test backend logic or API endpoints directly without additional integration.