Dogfood — Exploratory QA of web apps: find bugs, evidence, reports
Dogfood — Exploratory QA of web apps: find bugs, evidence, reports
Start with meaning, then move to detail.
This lesson explains Dogfood — Exploratory QA of web apps: find bugs, evidence, reports as part of extending Hermes and connecting external tools. You will learn what it does, when it matters, and the smallest safe test that proves it works.
If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?
For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.
For advanced readers, inspect Skill metadata, Reference: full SKILL.md, Overview, then verify failure modes and version compatibility.
Complete installation and one successful task before adding new capabilities.
A clear outcome before you read.
- Understand Dogfood — Exploratory QA of web apps: find bugs, evidence, reports without assumed prior knowledge.
- Separate the source description from what still needs testing in your environment.
- Read the first command and identify its inputs and outputs before copying it.
Short definitions before the details.
- Skill
- An instruction bundle that teaches Hermes a repeatable workflow without necessarily adding an external service.
Exploratory QA of web apps: find bugs, evidence, reports
What does the source say, and in what order?
- 01Skill metadata
Start here to understand the core idea or structure.
- 02Reference: full SKILL.md
Read this after the foundation, then connect it to the previous step.
- 03Overview
Read this after the foundation, then connect it to the previous step.
- 04Prerequisites
Read this after the foundation, then connect it to the previous step.
- 05Inputs
Read this after the foundation, then connect it to the previous step.
- 06Workflow
Read this after the foundation, then connect it to the previous step.
- 07Phase 1: Plan
Read this after the foundation, then connect it to the previous step.
- 08Phase 2: Explore
Read this after the foundation, then connect it to the previous step.
- 09Phase 3: Collect Evidence
Read this after the foundation, then connect it to the previous step.
- 10Phase 4: Categorize
Finish here to verify the result and special cases.
Copy only after you understand the effect.
{output_dir}/
├── screenshots/ # Evidence screenshots
└── report.md # Final report (generated in Phase 5)browser_navigate(url="https://example.com/page")browser_snapshot()Read the first command and identify its inputs and outputs before copying it.
Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.