skills.rest
paveg
pavegCOMMUNITY
Explore all skills by this author →
GitHub

browser-e2e-test

Automate browser end-to-end tests and create GitHub issues from failures.

2|Updated Dec 19, 2025
Search Tags:#automation#testing#e2e#claude#browser#github-issues
One-click install
npx skills add https://github.com/paveg/dots --skill browser-e2e-test
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browser-e2e-test
Source: https://github.com/paveg/dots/tree/main/dot_claude/skills/browser-e2e-test
Command: npx skills add https://github.com/paveg/dots --skill browser-e2e-test

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Web applications require reliable end-to-end browser testing and prompt bug reporting. This Skill automates browser-based E2E tests and creates GitHub issues for discovered problems, reducing manual QA time and speeding feedback.

Core Features & Use Cases

  • Automated navigation & interaction: Execute test flows by navigating pages, interacting with elements, and waiting for page loads.
  • UI capture & validation: Take screenshots and verify UI states and element visibility during test runs.
  • Bug detection & issue creation: Record failures (API, console, or UI) and auto-create GitHub issues using the provided templates.
  • Use Case: QA teams validate critical user journeys on staging with automated test runs and automatic issue generation.

Quick Start

Run the browser E2E test workflow in Claude to automatically validate a web app and create GitHub issues for any bugs.

Frequently Asked Questions about browser-e2e-test

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

FAQPage Schema
How do I automate browser end-to-end testing for web applications?▼

Capture browser bug failures by recording API errors, console messages, and UI visibility issues during test runs. This Skill detects these failures and automatically creates GitHub issues using templates to document the discovered problems for QA teams.

Can I capture network requests and console messages during E2E test runs?▼

Run browser E2E test workflows by applying steps like navigate, wait, screenshot, read_page, read_network_requests, and read_console_messages. These steps execute within Claude to validate web apps and generate GitHub issues for any detected bugs automatically.

Do I need additional dependencies to automate GitHub issue creation from browser tests?▼

No additional dependencies are required to automate GitHub issue creation from browser tests. This Skill operates independently to create GitHub issues using provided templates when API, console, or UI failures are detected during web application testing.

What's the best way to verify UI behavior and take screenshots during staging tests?▼

Verify UI behavior and take screenshots during staging tests by applying screenshot and read_page steps within automated E2E workflows. This captures UI states and validates element visibility to ensure critical user journeys function correctly before production deployment.

Related Skills

Explore More Software Engineering Skills→
freeCodeCamp-UniversefreeCodeCamp-Universe
8

sync-issue-templates

Syncs issue templates from an organization's GitHub repository to the current one.

Official
Intermediate
mindroom-aimindroom-ai
232

address-pr-review-comments

Analyze and categorize GitHub PR review comments for triage and remediation.

Official
Intermediate
linskybinglinskybing

cicd-pipeline-optimization

Optimizes ProjectName Gradle builds with automated dependency updates and PRs.

Community
Advanced
ivegamsftivegamsft

e2e-testing

Execute end-to-end tests for web applications using Playwright and Cypress.

Community
Advanced