dogfood

Navigate web pages and interact with DOM elements for exploratory QA testing.

Updated May 4, 2026

Search Tags:#automation #testing #qa #browser #web #dogfood

Ready to run

npx skills add https://github.com/InverterNetwork/hermes-agent --skill dogfood-inverternetwork

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the challenge of performing consistent, repeatable exploratory QA testing on web applications, ensuring that visual, functional, and accessibility issues are identified and documented before they reach production.

Core Features & Use Cases

Automated Exploratory Testing: Systematically navigates web applications to test links, forms, and interactive elements.
Evidence Collection: Automatically captures annotated screenshots and console logs to provide clear evidence for every identified issue.
Structured Reporting: Generates comprehensive bug reports including severity, steps to reproduce, and expected vs. actual behavior.

Quick Start

Use the dogfood skill to perform a full exploratory test on the website at https://example.com and save the findings to the local dogfood-output directory.

Frequently Asked Questions about dogfood

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

FAQPage Schema

How do I automate exploratory QA testing for a web application?▼

Automated exploratory QA testing systematically navigates web pages and interacts with DOM elements to identify functional, visual, and accessibility issues before production. It captures browser snapshots and console logs to provide clear evidence for comprehensive bug reporting.

What is the best way to capture console errors and visual bugs during web testing?▼

The best way to capture console errors and visual bugs is through automated browser snapshots and console error monitoring during navigation. This approach collects annotated screenshots and logs as evidence, generating structured reports with severity, reproduction steps, and expected behavior.

How do I generate structured bug reports with steps to reproduce from browser testing?▼

Structured bug reports are generated by documenting discovered issues with severity, steps to reproduce, and expected versus actual behavior. Automated exploratory testing captures the necessary evidence, such as screenshots and console logs, to populate these comprehensive reports automatically.

Do I need a browser toolset to perform automated accessibility verification on web pages?▼

Yes, a browser toolset is required to perform automated accessibility verification. The testing process relies on browser navigation, DOM interaction, and visual analysis tasks to target accessibility issues and execute comprehensive functional testing across web applications.

Can I systematically test links and forms on my website before production deployment?▼

Yes, you can systematically test links and forms by running automated exploratory testing on your website. This process interacts with interactive elements, captures console errors, and documents visual or functional issues to ensure consistent, repeatable QA verification before deployment.

What are the limitations of using automated DOM interaction for web QA testing?▼

Automated DOM interaction for web QA testing requires a compatible browser toolset to execute navigation and visual analysis. Without this environment, it cannot perform accessibility verification or capture the necessary browser snapshots and console logs needed for evidence collection.