dogfood

Identify web application defects during guided exploratory QA sessions with browser toolsets.

2|Updated Apr 25, 2026

Search Tags:#qa #end-to-end #web-testing #bug-reporting #exploratory-testing #browser-tool

Ready to run

npx skills add https://github.com/AlexiosBluffMara/mercury --skill dogfood-alexiosbluffmara

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/AlexiosBluffMara/mercury/tree/main/skills/dogfood
Command: npx skills add https://github.com/AlexiosBluffMara/mercury --skill dogfood-alexiosbluffmara

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic browser-based QA testing helps teams identify defects efficiently, capture evidence, and generate structured reports to speed up triage and fixes.

Core Features & Use Cases

Phase-driven testing workflow (Plan, Explore, Collect Evidence, Categorize, Report)
Automated evidence capture (screenshots, console logs, DOM state)
Structured bug reporting with taxonomy and executive summary
Use case: validate a new web feature across multiple pages and produce a comprehensive bug report with evidence.

Quick Start

Start a browser-assisted QA session against the target site and generate a dogfood report in the output directory.

Frequently Asked Questions about dogfood

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

FAQPage Schema

How do I run exploratory QA testing with automated evidence capture?▼

Exploratory QA testing with automated evidence capture is done by applying a guided session to a target URL, capturing screenshots and console logs, and generating a structured bug report. You need a browser toolset and a defined testing scope.

What is the best way to generate structured bug reports during web testing?▼

Generating structured bug reports during web testing is achieved by driving a phase-driven workflow that categorizes defects and compiles an executive summary. The session captures DOM state, screenshots, and console logs to produce a comprehensive report.

Can I use a browser toolset to identify web application defects across multiple pages?▼

You can use a browser toolset to identify web application defects by defining a target URL and testing scope. The session validates features across multiple pages, capturing deterministic evidence to speed up triage and fixes.

How does phase-driven testing workflow help with end-to-end web testing?▼

Phase-driven testing workflow helps with end-to-end web testing by structuring the process into Plan, Explore, Collect Evidence, Categorize, and Report phases. This ensures systematic defect identification and comprehensive evidence capture.

Do I need a defined testing scope to perform browser-assisted QA sessions?▼

A defined testing scope is required to perform browser-assisted QA sessions and drive deterministic, reportable results. Without a target URL and scope, the session cannot systematically capture evidence or generate a valid dogfood report.