integration-e2e-testing

Standardize integration and E2E test design, review, and execution.

2|1|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/tundraray/overture --skill integration-e2e-testing-tundraray
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: integration-e2e-testing
Source: https://github.com/tundraray/overture/tree/main/skills/integration-e2e-testing
Command: npx skills add https://github.com/tundraray/overture --skill integration-e2e-testing-tundraray

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams standardize and refine integration and E2E testing practices to improve reliability and reduce leakage into production.

Core Features & Use Cases

  • Behavior-First Principle: verify observable outcomes and user-visible behavior.
  • ROI Calculation: quantify test value, scope, and maintenance to prioritize coverage.
  • Test Skeleton Specification: define required test skeleton patterns, acceptance criteria, and review criteria for deterministic CI execution.
  • Review & Quality Standards: provide guidance for skeleton-implementation consistency, independence, and reproducibility.

Quick Start

Plan an integration test strategy for a new feature by applying ROI scoring, skeleton specification, and verification criteria.

Frequently Asked Questions about integration-e2e-testing

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

FAQPage Schema
How do I design an integration test strategy for a new feature?▼

To design an integration test strategy, apply ROI scoring to quantify test value and scope, define test skeleton patterns, and establish verification criteria for deterministic CI execution.

What is the behavior-first principle in E2E testing?▼

The behavior-first principle in E2E testing targets observable outcomes and user-visible behavior rather than internal implementation details to ensure reliable end-to-end journeys.

How do I calculate ROI for integration and E2E tests?▼

Calculate ROI for integration and E2E tests by quantifying test value, scope, and maintenance costs to prioritize coverage across features and end-to-end journeys.

What are test skeleton patterns and why are they needed for CI execution?▼

Test skeleton patterns define required structures, acceptance criteria, and review standards to ensure consistency, independence, and reproducibility for deterministic CI-ready quality checks.

When should I use E2E tests versus integration tests?▼

Use E2E tests for end-to-end user journeys and integration tests for feature interactions, prioritizing coverage by calculating ROI to balance test value and maintenance scope.

What quality standards should I apply when reviewing integration test skeletons?▼

Review integration test skeletons for implementation consistency, independence, and reproducibility to meet verification criteria and maintain deterministic CI-ready quality checks.