skills.rest
sora32127
sora32127COMMUNITY
Explore all skills by this author →
Website𝕏@contradiction29GitHub

e2e-tester

Automate headless browser testing for UI changes and regressions.

41|8|Updated Mar 20, 2024
Search Tags:#testing#e2e#regression#ui-testing#headless-browser#agent-browser#qa-automation
One-click install
npx skills add https://github.com/sora32127/healthy-person-emulator-dotorg --skill e2e-tester-sora32127
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: e2e-tester
Source: https://github.com/sora32127/healthy-person-emulator-dotorg/tree/main/.agent/skills/e2e-tester
Command: npx skills add https://github.com/sora32127/healthy-person-emulator-dotorg --skill e2e-tester-sora32127

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automates end-to-end browser testing to verify that UI changes are reflected correctly by using a headless browser, reducing manual verification effort and catching regressions early.

Core Features & Use Cases

  • Headless browser validation: Use agent-browser CLI to open pages, take accessibility snapshots, and interact with elements to confirm behavior.
  • Regression-oriented tests: Validate navigation flows, forms, error handling, and responsive layouts across key pages (top, post, readme, search, support).
  • Quick feedback loop: Provide quick, deterministic test results that can be integrated into CI for rapid release validation.

Quick Start

Run the e2e-tester against the target web application to verify the latest UI changes.

Frequently Asked Questions about e2e-tester

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

FAQPage Schema
How do I automate E2E browser testing for UI changes?▼

Automate E2E browser testing for UI changes by using a headless browser to execute scripted interactions, snapshot the DOM, interact with elements, and report deterministic outcomes for regression validation.

Can I use a headless browser to validate navigation flows and forms?▼

Yes, you can use a headless browser to validate navigation flows, forms, error handling, and responsive layouts by executing predefined scenarios and verifying behavioral outcomes across key pages.

What is the best way to verify UI regressions across responsive layouts?▼

Verify UI regressions across responsive layouts by running deterministic headless browser tests that open pages, take accessibility snapshots, interact with elements, and report any unexpected behavioral deviations.

Do I need the agent-browser CLI to run headless E2E tests?▼

Yes, you need the agent-browser CLI to open pages, take accessibility snapshots, and interact with elements to confirm behavior when running headless E2E tests for UI changes.

How do I integrate regression-oriented tests into a CI pipeline?▼

Integrate regression-oriented tests into a CI pipeline by executing predefined scenarios via the agent-browser CLI to provide quick, deterministic test results for rapid release validation.

Are there limitations when using a headless browser for UI testing?▼

Headless browser UI testing requires predefined scenarios in references and a deterministic workflow to open pages and snapshot the DOM, meaning tests are limited to scripted interactions rather than visual verification.

Related Skills

Explore More Software Engineering Skills→
AmitabhainArunachalaAmitabhainArunachala
1

Agent Browser

Automate web browser interactions for AI agents via CLI.

Community
Advanced
yalehyaleh
21

Testing Strategy

Transform ad-hoc Go testing into a pattern-driven strategy with coverage analysis.

Community
Advanced
joneqianjoneqian

agent-browser

Control a headless browser using accessibility-tree snapshots and ref-based element targeting.

Community
Advanced
robertzengcnrobertzengcn

browse

Automate headless browser navigation, interaction, and visual verification with Playwright-based Chromium.

Community
Advanced