e2e-test

Execute end-to-end QA with parallel sub-agents and browser automation.

12|5|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/ahostbr/kuroryuu-public --skill e2e-test-ahostbr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-test
Source: https://github.com/ahostbr/kuroryuu-public/tree/main/.claude/skills/e2e-test
Command: npx skills add https://github.com/ahostbr/kuroryuu-public --skill e2e-test-ahostbr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables automated, end-to-end quality assurance by orchestrating multiple agents to examine codebases, map out database schemas, detect potential bugs, and validate user journeys through a browser-based UI testing tool, ensuring comprehensive coverage before code reviews.

Core Features & Use Cases

  • Parallel sub-agents to research code structure, database schema, and potential issues
  • Browser-based UI journey validation using a CLI tool to capture screenshots and verify end-to-end flows
  • Post-implementation validation to confirm that all critical paths still function as expected prior to review

Quick Start

Run the e2e-test skill to execute the end-to-end testing workflow across code, database, and UI.

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 QA testing for web applications with a database backend?

Automated end-to-end QA testing orchestrates parallel agents to inspect codebases and database schemas, then uses browser automation to validate UI journeys and query records before code review.

Can I run browser automation to capture screenshots and verify UI flows in a CI pipeline?

Browser automation CLI captures screenshots and tests user journeys during end-to-end QA, validating UI/UX flows across development and staging environments to ensure robust software delivery.

What is multi-agent QA orchestration and how does it validate database records?

Multi-agent QA orchestration launches parallel sub-agents to inspect code structure and database schema, then queries the database to verify persistent records after testing user journeys.

Does end-to-end testing work for modern web apps with separate frontend and backend APIs?

End-to-end testing applies to modern web applications with frontend UI, backend APIs, and persistent data stores, validating critical paths across both development and staging environments.

When should I use automated e2e testing instead of manual code review?

Automated e2e testing should run before code review to detect potential bugs, validate database records, and confirm all critical UI journeys still function as expected post-implementation.

Why does e2e testing require parallel sub-agents for codebase and schema inspection?

Parallel sub-agents research codebase structure and database schema concurrently to map potential bugs efficiently, enabling comprehensive browser automation and data validation before review.