test-browser

Run agent-browser tests on git-changed web routes before merging.

Updated Nov 11, 2023
One-click install
npx skills add https://github.com/michaelvolz/redmuffin.Blazor.StaticWeb --skill test-browser-michaelvolz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-browser
Source: https://github.com/michaelvolz/redmuffin.Blazor.StaticWeb/tree/main/.opencode/skills/ce/test-browser
Command: npx skills add https://github.com/michaelvolz/redmuffin.Blazor.StaticWeb --skill test-browser-michaelvolz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures browser regressions introduced by PRs or branches are caught by running targeted end-to-end tests on the affected routes before merging.

Core Features & Use Cases

  • Scope detection: Maps git diffs or PR file listings to the URL routes that need testing while prompting for headed or headless mode.
  • agent-browser automation: Runs navigation, snapshots, interactions, and screenshot commands after validating the dev server port and availability.
  • Human oversight: Requests verification for flows requiring OAuth, payments, or external APIs, and outlines failure handling with optional todo creation.
  • Use Case: When a feature branch updates several controllers, let the skill step through each impacted page, capture snapshots, and surface errors for follow up.

Quick Start

Invoke the test-browser skill with the relevant PR number, branch name, or the word current so it runs agent-browser checks on your changed pages.

Frequently Asked Questions about test-browser

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

FAQPage Schema
How do I run browser tests only on changed routes to catch regressions before merging?

Run browser tests on changed routes by mapping git diffs or PR file listings to affected URLs and executing agent-browser commands against them. This ensures regressions introduced by feature branches are caught before merging.

How do I map git diffs to URLs for targeted end-to-end testing?

Mapping git diffs to URLs for end-to-end testing is handled by prompting for user input to guide scope detection. The skill analyzes modified files in a PR or branch and translates them into the specific web routes requiring agent-browser coverage.

Does agent-browser test automation require a running dev server?

Yes, agent-browser test automation requires a running dev server on a discoverable port. The skill validates server port availability before running navigation, snapshots, interactions, and screenshot commands on the affected pages.

Can I run headless browser tests on a specific branch or PR?

Yes, you can run headless browser tests on a specific branch or PR by invoking the skill with a PR number, branch name, or the word current. It prompts for headed or headless mode and applies agent-browser coverage to the changed pages.

How does browser test automation handle flows requiring OAuth or external APIs?

Browser test automation handles flows requiring OAuth or external APIs by requesting human verification before proceeding. The skill pauses automated navigation to outline failure handling and offers optional todo creation for follow-up.

Why should I use git diff based browser testing instead of testing every route?

Git diff based browser testing targets only the affected routes from your changes, saving time compared to testing every route. It steps through each impacted page to capture snapshots and surface errors directly related to the branch modifications.