ce-dogfood-beta

Diff active branch against main and run browser QA tests.

10|Updated Dec 13, 2016
One-click install
npx skills add https://github.com/vitallium/dotfiles --skill ce-dogfood-beta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-dogfood-beta
Source: https://github.com/vitallium/dotfiles/tree/main/dot_agents/skills/ce-dogfood-beta
Command: npx skills add https://github.com/vitallium/dotfiles --skill ce-dogfood-beta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diffs the active branch against main, builds an exhaustive browser test matrix of every change, drives the app with agent-browser, auto-fixes issues, adds regression tests, and commits each fix until the matrix is green, enabling a hands-off QA pass before shipping.

Core Features & Use Cases

  • Surface diffs between branches to identify what to test.
  • Map full user journeys and generate a deterministic test matrix executed via agent-browser.
  • Auto-fix issues, append regression tests, and commit changes until the matrix is green.
  • Produce a durable dogfood report summarizing diffs, findings, and decisions.

Quick Start

Pass a PR number or branch name to ce-dogfood-beta to start an autonomous end-to-end QA pass on that branch.

Frequently Asked Questions about ce-dogfood-beta

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

FAQPage Schema
How do I automate end-to-end browser QA for a feature branch before merging?

Automated end-to-end browser QA diffs your active branch against main, maps changes to user journeys, builds a test matrix, and executes it through agent-browser with autonomous fixes. It appends regression tests and commits changes until the matrix passes.

What is dogfooding in the context of continuous integration test automation?

Dogfooding in test automation means autonomously driving your application through agent-browser to exercise every diff from the active branch. It builds a comprehensive test matrix, auto-fixes issues, and produces a durable report of outcomes and learnings.

Can I generate a test matrix from git diffs and run browser automation automatically?

Yes, you can generate a test matrix from git diffs by mapping branch changes to complete user journeys. The matrix is then executed through agent-browser, which auto-fixes issues and appends regression tests until all matrix scenarios are green.

Does autonomous QA work with git worktrees and local dev servers?

Autonomous QA coordinates with git worktrees and local dev servers to execute the end-to-end test matrix. It diffs the active branch, drives the application, and manages fixes across the necessary development environments.

What's the best way to ensure new branch changes are test-covered before shipping?

The best way to ensure test coverage is diffing the active branch against main to build an exhaustive browser test matrix. Agent-browser executes every user journey, auto-fixes failures, and commits regression tests until all scenarios pass.

How does an agent-browser handle regression testing during an automated QA pass?

Agent-browser handles regression testing by autonomously executing the test matrix, identifying failures, applying fixes, and appending regression tests. It commits each fix iteratively until the entire browser test matrix is green.