e2e-test

Automate end-to-end web testing with browser interactions, screenshots, and database validation.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/nicholasmartin/peerpull --skill e2e-test-nicholasmartin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: e2e-test
Source: https://github.com/nicholasmartin/peerpull/tree/main/.claude/skills/e2e-test
Command: npx skills add https://github.com/nicholasmartin/peerpull --skill e2e-test-nicholasmartin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures web applications are validated across user journeys by combining automated codebase research, browser-driven interaction, and database verification so regressions and data integrity issues are caught before code review.

Core Features & Use Cases

  • Parallel research orchestration: launches sub-agents to map application structure, user journeys, and the database schema to build complete test plans.
  • Browser-driven interaction and visual checks: uses agent-browser to exercise every user flow, capture annotated screenshots, detect JS errors, and confirm UI/UX behavior across viewports.
  • Database validation and integrity checks: runs precise queries against the configured database to verify records created, updated, or deleted by UI interactions.
  • Use Case: run after feature implementation to automatically validate signup, profile creation, CRUD workflows, and responsive layouts while collecting reproducible evidence for reviewers.

Quick Start

Run the e2e-test skill to discover routes and journeys, start the dev server, execute agent-browser journeys with screenshots, and validate resulting database records.

Frequently Asked Questions about e2e-test

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

FAQPage Schema
How do I automate end-to-end testing with database validation and screenshots?▼

E2e testing with database validation and screenshots is automated by launching parallel research agents to map user journeys, driving browser interactions via agent-browser, capturing visual evidence, and running database queries to verify resulting data state.

How does agent-browser test orchestration map application routes for comprehensive test coverage?▼

Test orchestration maps application routes by launching sub-agents to research the codebase, identify user journeys, and extract the database schema, building a test plan that exercises every discovered flow through browser-driven interaction.

Do I need agent-browser installed on Linux or macOS to run browser-driven test interactions?▼

Yes, agent-browser must be installed on Linux, WSL, or macOS to run browser-driven test interactions, alongside access to dev server URLs and database connection details from .env.example for post-action validation.

What is the best way to validate database integrity after automated UI interactions?▼

Database integrity after automated UI interactions is validated by running precise queries against the configured database to verify records created, updated, or deleted by the browser-driven workflows, ensuring data state matches expected outcomes.

Can I use e2e testing to detect JavaScript errors across different viewport layouts?▼

Yes, e2e testing detects JavaScript errors and confirms UI/UX behavior across viewports by using agent-browser to exercise user flows, capture annotated screenshots, and collect reproducible visual evidence for reviewers.

When should I not use automated browser testing for web application validation?▼

Automated browser testing for web application validation is not suitable for applications without a browser-accessible frontend or when database connection details required for post-action state verification are unavailable.