e2e

Run full-stack end-to-end test flows against a live system with Connect RPC.

4|1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/reliant-labs/forge --skill e2e-reliant-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e
Source: https://github.com/reliant-labs/forge/tree/main/internal/templates/project/skills/forge/testing/e2e
Command: npx skills add https://github.com/reliant-labs/forge --skill e2e-reliant-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates uncertainty in complex releases by testing the complete running system end-to-end, ensuring that multi-service behavior works as users experience it.

Core Features & Use Cases

  • Full-stack end-to-end validation: Exercises real services, real database state, and real network calls across components.
  • Multi-service flow testing: Verifies cross-service propagation and workflow outcomes using actual Connect RPC calls.
  • Flake-resistant execution guidance: Enforces determinism rules like polling instead of sleeps, cleanup via t.Cleanup, and idempotent setup.

Use Case: When a workflow started in Service A must update and finalize state in Service B, use e2e to confirm the final state is correct across the running stack.

Quick Start

Run forge test e2e to execute the full end-to-end suite against a stack started by forge run.

Frequently Asked Questions about e2e

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

FAQPage Schema
How do I validate multi-service workflows with real Connect RPC calls?

You validate multi-service workflows by running full-stack end-to-end test flows against a live system, using real Connect RPC calls to verify that state propagation and workflow outcomes across services match expected results.

What is the best way to stop end-to-end test flakiness in a multi-service stack?

To stop end-to-end test flakiness, enforce deterministic execution rules: replace real-time sleeps with polling, use idempotent test setup, avoid ordering assumptions, and ensure proper resource cleanup via t.Cleanup to prevent state leakage between tests.

How do I run end-to-end tests against a live running stack?

You run end-to-end tests against a live stack by starting the system with forge run, then executing the full end-to-end test suite using forge test e2e to validate real database state and network calls across all services.

When do I need full-stack end-to-end testing instead of isolated unit tests?

You need full-stack end-to-end testing when a workflow started in one service must update and finalize state in another, requiring validation of the complete running system to ensure multi-service behavior works exactly as users experience it.

Why does my end-to-end test suite fail intermittently without code changes?

Intermittent end-to-end test failures usually stem from non-deterministic execution, such as relying on real-time sleeps, assuming test ordering, or lacking idempotent setup and proper cleanup via t.Cleanup, which causes state interference between test runs.