proof-e2e

Automate end-to-end UI testing with Playwright, Cypress, or Selenium.

69|8|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/tonone-ai/tonone --skill proof-e2e
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: proof-e2e
Source: https://github.com/tonone-ai/tonone/tree/main/team/proof/skills/proof-e2e
Command: npx skills add https://github.com/tonone-ai/tonone --skill proof-e2e

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-to-end UI testing is time-consuming and error-prone without a structured approach; this Skill provides a framework to build and maintain browser-based test suites using Playwright, Cypress, or Selenium.

Core Features & Use Cases

  • Detect frontend stack and existing E2E setup
  • Identify critical user journeys (authentication, core workflows, data mutations, error handling, navigation)
  • Set up test infrastructure (config, fixtures, page objects) and CI integration
  • Write robust tests with stable selectors, proper waits, and assertions
  • Integrate with CI to capture screenshots and artifacts on failures for debugging

Quick Start

Initialize an E2E test suite by detecting the frontend stack and creating a baseline configuration, then add a critical user-journey test

Frequently Asked Questions about proof-e2e

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

FAQPage Schema
How do I automate end-to-end UI tests for critical user journeys?

Automate end-to-end UI tests by orchestrating Playwright, Cypress, or Selenium suites to validate user journeys, cross-browser compatibility, and regression safeguards across authentication, core workflows, and error states.

What's the best way to set up E2E testing infrastructure with stable selectors?

Set up E2E testing infrastructure by detecting the frontend stack, generating baseline configurations and fixtures, and writing robust tests using stable data-test attribute selectors, proper waits, and assertions.

Does this test automation approach support CI integration with screenshots on failure?

Yes, test automation integrates with CI pipelines to enable parallel execution and automatically capture screenshots and artifacts on test failures for efficient debugging and regression tracking.

Can I use Playwright, Cypress, or Selenium for cross-browser compatibility testing?

You can use Playwright, Cypress, or Selenium for cross-browser compatibility testing, with the framework automatically detecting your existing E2E config and frontend stack to orchestrate the suites.

Why do my E2E tests fail during frontend stack detection and user-journey validation?

E2E tests fail when stable selector strategies like data-test attributes are missing, or when proper waits and assertions are not configured for core workflows, data mutations, and error handling states.

When do I need end-to-end UI testing for my web application?

You need end-to-end UI testing when your project requires user-journey validation across authentication, core workflows, data mutations, error handling, and navigation to prevent regressions.