dogfood

Automate exploratory QA testing of web applications with browser navigation and evidence capture.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Exploratory QA of web applications to identify bugs, capture evidence, and deliver structured reports for faster fixes and improved quality.

Core Features & Use Cases

  • Systematic browser-based exploration: navigate pages, interact with elements, and document issues.
  • Evidence collection and reporting: generate bug reports with screenshots, console logs, and reproducible steps.
  • Reproducible QA workflow: provide a clear, actionable path for developers to reproduce and fix issues.

Quick Start

Initiate a dogfood exploratory QA session for a target URL with a defined testing scope.

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 web applications?

Automated exploratory QA testing is executed by guiding a browser-based agent to navigate pages, interact with elements, and capture evidence. This systematic approach targets end-to-end evaluation across pages and user flows.

Can I generate reproducible bug reports from browser-based web testing?

Generating reproducible bug reports from web testing involves capturing screenshots, console logs, and structured interaction steps. This creates a clear, actionable path for developers to reproduce and fix the identified issues.

What do I need to run an automated browser agent for end-to-end evaluation?

Running an automated browser agent for end-to-end evaluation requires a target URL, testing scope, a browser toolset with navigate, snapshot, click, type, vision, and console capabilities, and an output directory for artifacts.

How does a browser agent collect evidence during web UI exploration?

During web UI exploration, a browser agent collects evidence by navigating pages, interacting with elements, and capturing screenshots and console logs. This evidence is compiled into structured reports for faster fixes.

What is the best way to structure testing scope for systematic web QA?

Structuring testing scope for systematic web QA involves defining specific pages and user flows for end-to-end evaluation. This targets the browser-based exploration to uncover bugs fast and generate structured reports.