dogfood

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

247|22|Updated Dec 11, 2024
One-click install
npx skills add https://github.com/graniet/kheish --skill dogfood-graniet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/graniet/kheish/tree/main/skills/dogfood
Command: npx skills add https://github.com/graniet/kheish --skill dogfood-graniet

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Manual web application QA testing is often inconsistent, misses hidden issues like silent JavaScript errors or edge case failures, and produces unstructured reports that are hard for engineering teams to act on quickly.

Core Features & Use Cases

  • 5-Phase Systematic Workflow: A structured plan-explore-collect-categorize-report process that ensures full coverage of pages, user flows, forms, and edge cases like empty states and error pages.
  • Automated Evidence Capture: Integrates browser automation tools to take annotated screenshots, log console errors, and record exact reproduction steps for every issue found.
  • Standardized Issue Classification: Uses a built-in taxonomy to categorize bugs by severity (Critical to Low) and type (Functional, Visual, Accessibility, etc.) for clear, prioritized reporting. Use case: A product team preparing for a feature launch can use this skill to run end-to-end exploratory testing on their web app, catch a broken checkout flow and uncaught console errors, and output a structured report with screenshots and reproduction steps for the engineering team to fix quickly.

Quick Start

Use the dogfood skill to perform exploratory QA testing on the web application at https://your-app.com, focusing on the user authentication and checkout flows, and save the final bug report to the ./qa-results directory.

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 web applications to catch functional and visual bugs?

Automating exploratory testing for web applications involves a structured plan-explore-collect-categorize-report workflow. This process uses browser automation to navigate user flows, forms, and edge cases, systematically identifying functional, visual, and accessibility bugs.

What is the best way to generate structured QA reports with screenshots and reproduction steps?

Structured QA reports are generated by capturing annotated screenshots, logging console errors, and recording exact reproduction steps during testing. Issues are then categorized using a standardized taxonomy by severity and type for clear prioritization.

Can I use browser automation for pre-launch and regression testing of web app checkout flows?

Yes, browser automation is effective for pre-launch and regression testing of web app checkout flows. It systematically explores user paths, validates form inputs, and captures evidence of silent JavaScript errors or broken navigation states.

How does systematic QA testing classify bug severity and type for engineering teams?

Systematic QA testing classifies bug severity and type using a built-in issue taxonomy, ranging from Critical to Low. It categorizes bugs as Functional, Visual, or Accessibility issues, providing engineering teams with prioritized, evidence-based reports.

What edge cases should web testing cover to find silent JavaScript errors and broken forms?

Web testing should cover edge cases like empty states, error pages, and form validation limits to find silent JavaScript errors and broken forms. Systematic exploration ensures these hidden issues are caught, logged, and documented with reproduction steps.