e2e-tester

Name: e2e-tester
Availability: InStock
Author: ylxmf

Execute browser-based end-to-end test flows and record verdicts with evidence.

11|1|Updated Mar 3, 2026

Search Tags:#verification #evidence #e2e-testing #browser #reproducibility #test-plans #live-system

Ready to run

npx skills add https://github.com/ylxmf2005/AgentCorp --skill e2e-tester-ylxmf2005

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: e2e-tester
Source: https://github.com/ylxmf2005/AgentCorp/tree/main/agentcorp/e2e-tester
Command: npx skills add https://github.com/ylxmf2005/AgentCorp --skill e2e-tester-ylxmf2005

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The e2e-tester skill validates that end-to-end user journeys can be completed on the live AgentCorp system and provides verifiable evidence of the outcome.

Core Features & Use Cases

Drive real user flows in a live environment using a browser-based session and capture evidence such as screenshots, page state, and logs.
Record verbatim steps, observed results, and per-flow verdicts (passed, failed, or blocked) with explicit failure details and required follow-ups.
Use the provided references and test plans to guide execution, ensure reproducibility, and document gaps and mitigations for future fixes.

Quick Start

Run assigned end-to-end test flows against the live system and report observed outcomes with supporting evidence.

Frequently Asked Questions about e2e-tester

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

FAQPage Schema

How do I validate end-to-end user journeys on a live system?▼

End-to-end user journey validation on a live system is performed by driving real user flows through a browser-based session, capturing evidence like screenshots and logs to verify outcomes.

What's the best way to capture browser evidence during live system testing?▼

Capturing browser evidence during live system testing involves running deterministic test plans that record verbatim steps, page state, and logs to document observed outcomes for each flow.

How does e2e testing handle blocked or failed test flows?▼

E2e testing handles failed or blocked flows by recording per-flow verdicts with explicit failure details and required follow-ups, documenting gaps and mitigations for future fixes.

Can I use test plans to ensure reproducibility in browser-based testing?▼

Test plans guide deterministic execution in browser-based testing by providing structured references that ensure reproducibility and document observed results for each user flow.

Does e2e testing work for live flows or only API-only checks?▼

E2e testing applies specifically to live flows requiring browser-based interaction and observed outcomes rather than API-only checks, validating complete user journeys on the live system.

When should I not use browser-based end-to-end validation?▼

Browser-based end-to-end validation should be avoided when your verification task only requires API-only checks, as this approach focuses on live user flows with observed browser evidence.