agentic-browser-testing

Run goal-driven browser tests via accessibility tree assertions.

2|Updated Apr 18, 2021

Search Tags:#end-to-end #playwright #browser testing #accessibility tree #ci gating #deterministic automation

Ready to run

npx skills add https://github.com/rabbicse/go-projects --skill agentic-browser-testing

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: agentic-browser-testing
Source: https://github.com/rabbicse/go-projects/tree/main/projects/movie-ticket-booking/.claude/skills/agentic-browser-testing
Command: npx skills add https://github.com/rabbicse/go-projects --skill agentic-browser-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill replaces brittle, selector-heavy browser tests with a goal-driven agent that can explore changing UIs through the accessibility tree and prove the final outcome with an explicit oracle.

Core Features & Use Cases

Intent-driven E2E testing: Validate fast-changing workflows without maintaining hardcoded click paths.
Deterministic agent runs: Pin the model, set temperature to zero, seed state, and enforce a step budget so results are repeatable.
Snapshot-first interaction: Use accessibility snapshots, role-based refs, and structured assertions instead of screenshots or pixel coordinates.
CI gating and graduation: Block merges on machine-readable pass or fail results, then promote stable flows into scripted Playwright tests.
Use case: A QA team can smoke-test a churning checkout or dashboard flow, catch false passes, and later turn the stable path into a durable regression test.

Quick Start

Ask the agent to run a goal-driven browser test against a seeded entry URL and require a final snapshot-based pass or fail verdict.

Frequently Asked Questions about agentic-browser-testing

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

FAQPage Schema

How do I run goal-driven browser tests without maintaining brittle selectors?▼

Goal-driven browser testing uses the accessibility tree to explore changing UIs and verify outcomes with explicit assertions. You direct tests by intent rather than hardcoded click paths, eliminating selector maintenance.

How do I make agentic end-to-end tests deterministic for CI gating?▼

Make agentic end-to-end tests deterministic by pinning the model, setting temperature to zero, seeding application state, enforcing a bounded step budget, and using snapshot-based oracles for repeatable pass or fail verdicts.

What is the accessibility tree approach to browser testing?▼

The accessibility tree approach to browser testing interacts with applications via role-based references and structured snapshots instead of screenshots or pixel coordinates, providing a stable interaction model for fast-changing user flows.

Can I use goal-driven browser testing for exploratory smoke checks on churning UIs?▼

Yes, goal-driven browser testing suits exploratory smoke checks on churning UIs by validating workflows through intent rather than fixed selectors, allowing you to catch false passes in rapidly changing checkout or dashboard flows.

How do I graduate stable agent browser test paths into regression tests?▼

Graduate stable agent browser test paths into regression tests by promoting the proven goal-driven flow into a scripted Playwright test, blocking merges using machine-readable pass or fail results until the flow stabilizes.

What are the limitations of using accessibility snapshots for E2E testing?▼

Limitations of accessibility snapshots for E2E testing include the strict requirement for deterministic agent runs: pinned models, zero temperature, seeded state, and bounded steps are mandatory, making un-seeded or random-state applications unsuitable.