e2e-test

Name: e2e-test
Availability: InStock
Author: Terrazul

Automate end-to-end validation of user journeys across frontend, backend, and integrations.

Updated Nov 22, 2025

Search Tags:#workflow #e2e #qa-automation #test-management #end-to-end-testing #journey-testing

Ready to run

npx skills add https://github.com/terrazul-ai/tz-packages --skill e2e-test-terrazul-ai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: e2e-test
Source: https://github.com/terrazul-ai/tz-packages/tree/main/web-qa-engineer/templates/claude/skills/e2e-test
Command: npx skills add https://github.com/terrazul-ai/tz-packages --skill e2e-test-terrazul-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-to-end testing of complete user journeys across frontend, backend, and integrations is automated to reduce release risk and manual QA effort.

Core Features & Use Cases

Journey mapping: Define end-to-end user paths from starting point to goal across frontend, API, and integrations.
Multi-step execution: Run complex flows sequentially with traceable steps.
State validation: Verify data consistency across UI, API responses, and the database.
Error flow testing: Validate how the system handles failures and recovery.
Reporting & metrics: Capture results, timings, and evidence for audit and improvement.

Use Cases: Pre-release verification, cross-component testing, acceptance testing, and regression checks for critical user journeys.

Quick Start

Run the e2e-test skill to execute a full signup-to-dashboard journey in a staging environment.

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 user journey tests across frontend and backend?▼

End-to-end user journey tests are automated by mapping complete user paths from start to goal across frontend, API, and integrations, then executing multi-step flows sequentially with traceable steps to validate full system reliability.

What is the best way to validate data consistency across UI, API responses, and the database during testing?▼

State validation verifies data consistency across UI, API responses, and the database during end-to-end testing, ensuring that frontend interactions and backend data updates remain synchronized throughout complex multi-step user journeys.

How do I test error flows and system recovery in end-to-end testing?▼

Error flow testing in end-to-end validation checks how the system handles failures and recovery, ensuring that unexpected errors during user journeys are caught, managed, and traced without breaking the entire flow.

When do I need end-to-end testing for pre-release verification?▼

End-to-end testing is needed for pre-release verification, cross-component testing, and acceptance testing when the reliability of full user journeys matters, reducing release risk and manual QA effort before deployment.

Can I use end-to-end testing for cross-component acceptance testing in a staging environment?▼

End-to-end testing supports cross-component acceptance testing in staging environments by running deterministic steps, validating state, and capturing detailed reporting and metrics for critical user journeys like signup-to-dashboard flows.

Does end-to-end testing work for regression checks on critical user journeys?▼

End-to-end testing works for regression checks by re-running critical user journeys sequentially, validating state consistency, and capturing evidence and timings to ensure new changes do not break existing cross-component flows.