test-web

Run smoke tests on a web UI using agent-browser to identify regressions.

38|13|Updated Jun 30, 2025

Search Tags:#automation #commit #qa #test #web #agent-browser

Ready to run

npx skills add https://github.com/jhb-software/payload-astro-website-template --skill test-web

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test-web
Source: https://github.com/jhb-software/payload-astro-website-template/tree/main/.claude/skills/test-web
Command: npx skills add https://github.com/jhb-software/payload-astro-website-template --skill test-web

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates quick verification of web features by running a lightweight smoke test against a running web app to catch obvious regressions before commits.

Core Features & Use Cases

Open the app at a known URL (e.g., http://localhost:4321) and load the UI to perform quick checks.
Generate an interactive element snapshot to identify UI references and verify key selectors.
Execute simple clicks or interactions to validate navigation and behavior in a controlled local/dev environment.

Quick Start

Start the web dev server in the background and verify the feature using agent-browser against http://localhost:4321.

Frequently Asked Questions about test-web

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

FAQPage Schema

How do I run a smoke test on my web app before a commit?▼

To run a smoke test before a commit, use agent-browser to open your local dev server, generate an interactive element snapshot to verify selectors, and perform clicks to validate navigation and behavior.

What is web UI smoke testing for local development?▼

Web UI smoke testing for local development is running lightweight automated checks against a running web app to catch obvious regressions and verify page interactions before committing code.

Do I need a specific port running to test web UI features with agent-browser?▼

Yes, web UI testing with agent-browser requires your dev server running on port 4321 to open the app, take snapshots, and perform interactions to verify behavior.

Can I validate page interactions and element references in a CI workflow?▼

Yes, you can validate page interactions and element references in a CI workflow by running agent-browser against the accessible web app to execute clicks and verify navigation behavior.

What's the best way to identify regressions in a web UI before committing?▼

The best way to identify web UI regressions before committing is to automate quick verification using agent-browser to load the UI, verify key selectors via snapshots, and validate controlled local interactions.