dogfood

Automate exploratory QA testing of web applications with browser automation.

Updated Apr 29, 2026
One-click install
npx skills add https://github.com/DifanaDAP/hermes-backup --skill dogfood-difanadap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/DifanaDAP/hermes-backup/tree/main/workspace/skills/dogfood
Command: npx skills add https://github.com/DifanaDAP/hermes-backup --skill dogfood-difanadap

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires browser_navigate, browser_snapshot, browser_click, browser_type, browser_vision, browser_console, browser_scroll, browser_back, browser_press, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Dogfood addresses the time-consuming and error-prone nature of web application QA testing by providing a systematic, exploratory approach to identify bugs and issues.

Core Features & Use Cases

  • Systematic Workflow: A 5-phase process for comprehensive testing.
  • Interactive Element Testing: Ensures all interactive elements are functioning correctly.
  • Evidence Collection: Captures screenshots and logs for detailed issue reports.
  • Issue Categorization: Classifies issues by severity and category.
  • Automated Reporting: Generates structured reports for easy review and action.

Quick Start

Run the dogfood skill on your web app at 'https://example.com' with a focus on 'full site'.

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?

Automate exploratory QA testing for a web application by executing systematic browser interactions, capturing visual evidence, and categorizing identified issues. This structured approach uses a 5-phase workflow to perform comprehensive navigation and interactive element testing.

What is the best way to collect evidence during web app bug detection?

Collect evidence during web app bug detection by automating screenshot capture and console log retrieval during navigation. This process systematically records visual states and errors, generating detailed reports with categorized findings and recommendations.

Can I run automated reporting on web application issues by severity?

Yes, you can run automated reporting on web application issues by severity. The testing process classifies identified bugs by severity and category, outputting structured reports that contain detailed findings and actionable recommendations for easy review.

Do I need browser automation libraries to perform systematic exploratory testing?

Yes, browser automation libraries are required to perform systematic exploratory testing. The process depends on browser interaction tools to navigate URLs, snapshot states, click elements, type inputs, and scroll through web pages to identify bugs.

What limitations exist when using automated browser interactions for QA testing?

Limitations of using automated browser interactions for QA testing include dependency on supported browser actions like navigate, click, type, and scroll. Complex non-browser interactions or native system dialogs fall outside the scope of this web application testing approach.