dogfood

Guide exploratory QA testing of web applications through a structured workflow.

Updated Jun 26, 2026
One-click install
npx skills add https://github.com/NITISH-gitbit/hermes-custom --skill dogfood-nitish-gitbit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/NITISH-gitbit/hermes-custom/tree/main/skills/dogfood
Command: npx skills add https://github.com/NITISH-gitbit/hermes-custom --skill dogfood-nitish-gitbit

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?

This Skill automates the process of systematic QA testing of web applications, enabling users to find bugs, evidence, and reports efficiently.

Core Features & Use Cases

  • Exploratory QA Testing: Guides through a structured 5-phase workflow for QA testing of web apps.
  • Browser Automation: Integrates with browser tools for navigation, snapshotting, console error checking, and interactive element testing.
  • Evidence Collection: Takes screenshots, captures console output, and records detailed issue reports.
  • Issue Categorization: Classifies issues based on severity and category using the provided taxonomy.
  • Reporting: Generates a comprehensive report with an executive summary, issue details, and testing coverage.
  • Use Case: Ideal for QA professionals or automated testing engineers looking to streamline the QA process for web applications.

Quick Start

Execute the 'dogfood' skill with the target URL and testing scope to start systematic web application testing.

Frequently Asked Questions about dogfood

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

FAQPage Schema
How do I automate exploratory web testing for a web application?

QA automation for web applications works by integrating browser navigation, snapshotting, and console error checking into a structured testing workflow. It captures screenshots, records console output, and classifies discovered issues based on severity and category taxonomy.

Can I capture console errors and screenshots during web testing?

Yes, you can capture console errors and screenshots during web testing. The workflow integrates browser console checking and vision snapshotting to collect visual evidence and output logs, recording detailed issue reports for comprehensive bug tracking.

What do I need to start QA automation for web applications?

To start QA automation for web applications, you need a target URL and browser automation tools for navigation, snapshotting, clicking, typing, and console checking. Providing the target URL and testing scope initializes the systematic 5-phase testing workflow.

How do I categorize and report bugs found during browser automation?

You categorize and report bugs using a provided taxonomy that classifies issues by severity and category. The workflow generates a comprehensive report featuring an executive summary, detailed issue information, and overall testing coverage metrics.

Does this automated web testing workflow handle interactive elements like clicking and typing?

Yes, the automated web testing workflow handles interactive elements by integrating browser click, type, scroll, back, and press commands. These browser automation tools allow systematic testing of all interactive elements within the target web application.

What is the best way to generate a QA report from exploratory testing?

The best way to generate a QA report from exploratory testing is using a structured workflow that compiles collected screenshots and console errors into a comprehensive document. It produces an executive summary, detailed issue categorizations, and overall testing coverage metrics.