What is the Behavior-First principle in this skill?

The Behavior-First principle focuses testing on user-observable outcomes and business logic correctness, intentionally excluding implementation details and UI layout specifics to maximize test stability and ROI.

What is the recommended limit for E2E tests?

To maintain a fast and reliable CI/CD pipeline, the skill recommends a maximum of 1-2 E2E tests per feature, focusing strictly on critical user journeys.

What are the required annotations for a test skeleton?

Every test must include comments for the original Acceptance Criteria (AC), a Behavior string (Trigger → Process → Result), category, dependency, complexity, and the calculated ROI score.

How does the skill help calculate Test ROI?

It provides a specific formula: (Business Value × User Frequency + Legal Requirement × 10 + Defect Detection) divided by the total cost of creation, execution, and maintenance.

Integration & E2E Testing Architect

Name: Integration & E2E Testing Architect
Author: Tahir-yamin

byTahir-yamin

•

Security & Testing

Standardizes integration and end-to-end test design using behavior-first principles and ROI-driven selection criteria.

About

The Integration & E2E Testing Architect skill provides a rigorous framework for designing and auditing high-value test suites within the Claude Code environment. It helps developers move beyond fragile, low-value tests by prioritizing user-observable behavior, enforcing standardized test skeleton specifications, and calculating ROI to ensure testing efforts focus on critical business paths. By incorporating EARS (Easy Approach to Requirements Syntax) mapping and strict review criteria, this skill ensures that integration and E2E layers are maintainable, deterministic, and effective at catching defects without bloating CI/CD pipelines.

Key Features

Calculates test ROI scores based on business value, frequency, and maintenance costs.
Maps EARS requirements syntax directly to event-driven or state-based test generation.
Enforces standardized test skeletons with mandatory annotations for AC, behavior, and complexity.
Provides automated review criteria to detect anti-patterns like state sharing or mocked internal components.
3 GitHub stars
Applies behavior-first principles to focus on user-observable results rather than implementation details.

Use Cases

Designing a high-confidence integration test suite for complex component interactions.
Auditing existing E2E tests to identify and remove low-ROI or non-deterministic test cases.
Generating standardized test skeletons that align developer implementation with business acceptance criteria.

About

Key Features

Calculates test ROI scores based on business value, frequency, and maintenance costs.
Maps EARS requirements syntax directly to event-driven or state-based test generation.
Enforces standardized test skeletons with mandatory annotations for AC, behavior, and complexity.
Provides automated review criteria to detect anti-patterns like state sharing or mocked internal components.
3 GitHub stars
Applies behavior-first principles to focus on user-observable results rather than implementation details.

Use Cases

Designing a high-confidence integration test suite for complex component interactions.
Auditing existing E2E tests to identify and remove low-ROI or non-deterministic test cases.
Generating standardized test skeletons that align developer implementation with business acceptance criteria.