dogfood

Automate exploratory QA testing of web applications with structured bug reports.

1.2k|116|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/math-inc/OpenGauss --skill dogfood-math-inc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/math-inc/OpenGauss/tree/main/skills/dogfood
Command: npx skills add https://github.com/math-inc/OpenGauss --skill dogfood-math-inc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic QA testing helps teams find bugs early by guiding exploratory testing across web applications, capturing evidence, and organizing findings into a structured report.

Core Features & Use Cases

  • Structured 5-phase QA workflow (Plan, Explore, Collect Evidence, Categorize, Report)
  • Browser-tool based navigation, interaction, and evidence capture
  • Generates a Dogfood QA Report with issue taxonomy

Quick Start

Run a dogfood session against your target URL to start automated exploratory QA.

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 for web applications is executed through a structured 5-phase workflow that navigates pages, interacts with elements, and generates a formal bug report. You simply provide a target URL and testing scope to begin.

What is systematic dogfood testing and how does it capture bug evidence?

Systematic dogfood testing is an exploratory QA process that uses a browser toolset to navigate web pages and capture evidence. It organizes artifacts and applies a formal issue taxonomy to ensure findings are reproducible in the final structured report.

Can I run a targeted QA session against a specific URL without prior setup?

Yes, you can run a targeted QA session against a specific URL without prior setup. The system guides you through planning, exploration, evidence collection, issue categorization, and reporting without requiring external dependencies.

What's the best way to structure bug reports found during web testing?

The best way to structure bug reports from web testing is by applying a formal issue taxonomy and organizing captured evidence into a publishable Dogfood QA Report. This ensures reproducibility and clear classification of findings.

Does automated exploratory testing work for complex browser interactions?

Yes, automated exploratory testing works for complex browser interactions by using a dedicated browser toolset to navigate pages and interact with elements. It systematically captures evidence during these actions for the final report.