e2e-strategy

Design end-to-end testing strategies for user journeys across frontend, backend, and infrastructure.

3|Updated May 28, 2026
One-click install
npx skills add https://github.com/mahg-es/araya --skill e2e-strategy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: e2e-strategy
Source: https://github.com/mahg-es/araya/tree/main/skills/e2e-strategy
Command: npx skills add https://github.com/mahg-es/araya --skill e2e-strategy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-to-end testing strategy design ensures complete user journeys across frontend, backend, and infrastructure are validated, reducing deployment risks.

Core Features & Use Cases

  • Test Pyramid design: establish a balanced mix of unit, integration, and end-to-end tests.
  • Critical journey coverage: identify and automate the most important user paths.
  • Reliability and CI integration: specify deterministic environments, workflows, and metrics to prevent flaky tests.

Quick Start

Define an end-to-end testing plan that captures critical journeys, test pyramid balance, and automation architecture.

Frequently Asked Questions about e2e-strategy

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

FAQPage Schema
How do I design an end-to-end testing strategy that covers critical user journeys?▼

Design an end-to-end testing strategy by identifying critical user paths across frontend, backend, and infrastructure, then automating them to ensure complete journey validation and reduce deployment risks.

What is the best way to balance a test pyramid for web apps and services?▼

Balance a test pyramid by establishing a proportional mix of unit, integration, and end-to-end tests, ensuring broad coverage at base layers and targeted execution for critical paths.

How do I prevent flaky tests in my CI/CD test automation workflows?▼

Prevent flaky tests in test automation by specifying deterministic environments, reliable architecture, and structured metrics within your CI integration workflows.

When do I need end-to-end testing for pre-release readiness and risk-prone features?▼

You need end-to-end testing for pre-release readiness when validating complete user journeys across frontend, backend, and infrastructure, specifically targeting risk-prone features and critical paths.

How can I verify error states and critical paths in my test automation architecture?▼

Verify error states and critical paths by designing a test architecture that automates important user journeys and explicitly includes error state validations across infrastructure and application layers.