skills.rest
Throokie
ThrookieCOMMUNITY
Explore all skills by this author →
GitHub

e2e-optimizer

Run only changed E2E paths with mocked external dependencies in Playwright.

2|Updated Mar 21, 2026
Search Tags:#automation#testing#e2e#playwright#quality-assurance#mock
One-click install
npx skills add https://github.com/Throokie/claude-code-skills --skill e2e-optimizer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: e2e-optimizer
Source: https://github.com/Throokie/claude-code-skills/tree/main/skills/e2e-optimizer
Command: npx skills add https://github.com/Throokie/claude-code-skills --skill e2e-optimizer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Addresses the slow feedback loop of traditional E2E testing by executing only the changed end-to-end paths and by enforcing mocks for external dependencies, reducing runtime and flakiness.

Core Features & Use Cases

  • Selective E2E execution: runs only impacted flows to significantly shorten feedback time.
  • External dependency mocking: ensures deterministic results by stubbing API calls and network requests.
  • Testing strategy guidance: promotes a focused, MVU-style core-path validation and shift-left testing.

Quick Start

Run a focused E2E test for the core user path with mocked external dependencies.

Frequently Asked Questions about e2e-optimizer

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

FAQPage Schema
How do I speed up Playwright E2E tests by running only changed paths?▼

Speed up Playwright E2E tests by selectively executing only impacted end-to-end paths. This targeted approach significantly shortens feedback time by skipping unchanged flows during your test runs.

Why are my E2E tests flaky and how does mocking external dependencies help?▼

Flaky E2E tests are often caused by live network requests; mocking external dependencies ensures deterministic results by stubbing API calls. This strict isolation guarantees fast, consistent test runs without external interference.

What is the testing pyramid approach for validating core user paths?▼

The testing pyramid approach validates core paths with E2E tests while relying on unit and component tests for non-core logic. This focused MVU-style validation shifts testing left to optimize coverage and speed.

Can I run focused E2E tests for core user paths with mocked API calls?▼

Yes, you can run focused E2E tests for core user paths with strictly mocked API calls. This configuration validates critical application flows while maintaining deterministic outcomes through external dependency stubbing.

What's the best way to reduce E2E test runtime for web applications?▼

The best way to reduce E2E test runtime is executing only the changed end-to-end paths combined with strict external dependency mocking. This eliminates unnecessary test execution and network latency.

Related Skills

Explore More Software Engineering Skills→
jon23djon23d
3

playwright-e2e

Create and run Playwright end-to-end tests with configuration and API mocking.

Community
Intermediate
haidonglethqbhaidonglethqb

ck:test

Automate unit, integration, e2e, and UI tests with coverage analysis.

Community
Advanced
verivendverivend

vitest-testing

Generate Vitest unit test templates for Vue 3 TypeScript Vite projects.

Official
Intermediate
TheSoftwareHouseTheSoftwareHouse
282

e2e-testing

Automate Playwright end-to-end tests with page objects and network mocking.

Official
Intermediate