dogfood

Name: dogfood
Availability: InStock
Author: garrettroi

Navigates web applications, captures console errors, and generates structured bug reports.

Updated Mar 12, 2026

Search Tags:#testing #qa #browser automation #web application #bug reporting #exploratory testing

Ready to run

npx skills add https://github.com/GarrettRoi/open-manus --skill dogfood-garrettroi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/GarrettRoi/open-manus/tree/main/skills/dogfood
Command: npx skills add https://github.com/GarrettRoi/open-manus --skill dogfood-garrettroi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates systematic exploratory QA testing of web applications, helping to identify bugs, capture evidence, and generate structured reports.

Core Features & Use Cases

Systematic Exploration: Guides through a 5-phase workflow (Plan, Explore, Collect Evidence, Categorize, Report) for comprehensive testing.
Automated Evidence Capture: Uses browser tools to take screenshots, record console errors, and visually assess pages.
Structured Reporting: Generates detailed bug reports with severity, category, steps to reproduce, and screenshots.
Use Case: A QA engineer can use this skill to thoroughly test a new web application feature, ensuring all potential bugs are identified and documented before release.

Quick Start

Use the dogfood skill to test the website at https://example.com, focusing on the user signup flow.

Frequently Asked Questions about dogfood

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

FAQPage Schema

How do I automate exploratory testing for a web application?▼

Automated exploratory testing for a web application is performed by navigating pages, interacting with elements, capturing console errors, and taking annotated screenshots to identify bugs. This approach uses a 5-phase workflow to systematically plan, explore, collect evidence, categorize, and report issues.

Can I automatically generate structured bug reports with severity and categories?▼

Structured bug reports with severity and categories are generated automatically after systematic web app testing. The reports include steps to reproduce, identified categories, severity levels, and captured screenshot evidence to document discovered bugs thoroughly.

What is the best way to capture console errors and screenshots during web app QA testing?▼

Capturing console errors and screenshots during web app QA testing is best achieved using browser automation tools. These tools automatically record page states, visually assess elements, and compile the captured evidence into a structured bug report.

Does browser automation work for systematic exploratory testing of user signup flows?▼

Browser automation works effectively for systematic exploratory testing of user signup flows by navigating the interface and interacting with elements. It captures console errors and annotated screenshots to document any bugs encountered during the process.

What are the limitations of automated exploratory QA testing for web applications?▼

Limitations of automated exploratory QA testing involve its reliance on browser automation tools to navigate and interact with web applications. It focuses on capturing console errors and visual screenshots, meaning complex logical validations might still require manual verification.