dogfood

Name: dogfood
Availability: InStock
Author: unclehowell

Perform systematic exploratory QA testing of web applications with browser tools.

Updated Sep 1, 2021

Search Tags:#automation #testing #qa #reporting #browser #bug

Ready to run

npx skills add https://github.com/unclehowell/unclehowell --skill dogfood-unclehowell

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Exploratory QA testing of web applications often lacks systematic evidence collection and structured reporting, leading to missed bugs and inefficient triage.

Core Features & Use Cases

Systematic Workflow: Guides agents through planning, exploring, evidence collection, categorization, and reporting phases.
Browser Toolset Integration: Utilizes navigation, snapshot, vision, console, and interaction tools to detect functional, visual, and accessibility issues.
Automated Reporting: Generates a markdown report with screenshots, severity classification, and executive summary.

Quick Start

Ask the agent to run the dogfood skill on the target URL and receive a complete bug report with screenshots.

Frequently Asked Questions about dogfood

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

FAQPage Schema

What is automated exploratory QA testing for web applications?▼

Automated exploratory QA testing for web applications systematically navigates target URLs to detect functional, visual, and accessibility issues. It guides agents through planning, exploring, evidence collection, categorization, and reporting phases.

How do I generate automated QA reports with screenshots for my website?▼

To generate automated QA reports with screenshots, apply the testing workflow to your target website. It produces a markdown report containing screenshots, severity classification, and an executive summary.

Does web QA testing require specific browser tools for console monitoring?▼

Web QA testing requires a browser toolset with navigation, snapshot, click, type, vision, console, scroll, back, press, and close capabilities to properly monitor console errors and interact with the page.

Can I use automated testing to check form interactions and visual layouts?▼

Automated testing can check form interactions and visual layouts by utilizing browser snapshot and vision tools. This detects functional defects and visual discrepancies during the exploratory testing workflow.

What is the best way to systematically categorize bugs found during web testing?▼

The best way to systematically categorize bugs found during web testing is using an evidence collection and categorization phase. This workflow classifies issues by severity and generates a structured markdown report.

Why does exploratory testing often miss bugs and create inefficient triage?▼

Exploratory testing misses bugs and creates inefficient triage when it lacks systematic evidence collection and structured reporting. Applying an automated workflow with screenshots and severity classification solves this problem.