e2e-test

Orchestrate parallel sub-agents to validate user journeys, UI, and PostgreSQL data.

Updated Feb 28, 2026
One-click install
npx skills add https://github.com/Xandon/haversack-broker-os2 --skill e2e-test-xandon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-test
Source: https://github.com/Xandon/haversack-broker-os2/tree/main/.claude/skills/e2e-test
Command: npx skills add https://github.com/Xandon/haversack-broker-os2 --skill e2e-test-xandon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-to-end testing helps validate that completed features work as intended across frontend, backend, and data layers, reducing post-release defects by coordinating research, UI checks, and data validation.

Core Features & Use Cases

  • Parallel research agents that study user journeys, database changes, and potential bugs for a feature.
  • Browser-based UI validation using agent-browser to navigate and verify flows across the app.
  • Automated screenshots & visual validation to ensure UI consistency and layout integrity.
  • Data verification by querying PostgreSQL to confirm records and audit trails align with expected changes.
  • Post-implementation gating to validate everything before marking a feature complete.

Quick Start

Run the end-to-end test after implementing a feature to validate journeys, data changes, and UI consistency.

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 across frontend, backend, and database layers?

End-to-end testing is automated by orchestrating parallel sub-agents that research user journeys, verify browser-based UI flows, and validate PostgreSQL data mutations to confirm completed features meet acceptance criteria.

How does parallel agent research work for feature validation?

Parallel agent research works by deploying multiple sub-agents simultaneously to investigate user journeys, analyze database changes, and identify potential bugs across frontend, backend, and data layers after feature implementation.

What is the best way to verify PostgreSQL data changes during e2e testing?

Verifying PostgreSQL data changes during e2e testing is best handled by querying the database directly to confirm that records and audit trails align with expected mutations from the completed feature.

Can I use agent-browser for automated UI validation and screenshots?

Yes, you can use agent-browser for automated UI validation to navigate application flows, verify UI consistency, and capture automated screenshots for visual layout integrity checks.

When do I need to run end-to-end validation after implementing a feature?

You need to run end-to-end validation immediately after feature implementation to act as a post-implementation gating mechanism, ensuring all journeys, data changes, and UI elements function correctly before release.

Does e2e-test work without external dependencies for QA automation?

Yes, e2e-test works without external dependencies, using internal parallel agents and built-in agent-browser capabilities to perform comprehensive QA automation and structured results reporting.