e2e-test-runner

Execute Playwright and Cypress end-to-end tests with CI-optimized sharding and retries.

3|2|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/robotijn/ctoc --skill e2e-test-runner-robotijn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: e2e-test-runner
Source: https://github.com/robotijn/ctoc/tree/main/skills/testing/runners/e2e-test-runner
Command: npx skills add https://github.com/robotijn/ctoc --skill e2e-test-runner-robotijn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually running end-to-end tests is slow, error-prone, and often lacks the artifacts needed to debug failures. This skill automates E2E test execution with CI-optimized defaults, eliminating manual effort and ensuring test runs are reliable, debuggable, and aligned with 2026 best practices.

Core Features & Use Cases

  • CI-Optimized Execution: Runs Playwright/Cypress tests with built-in sharding, retry logic, and artifact capture (traces, screenshots, videos) for seamless CI integration.
  • Flaky Test Management: Enforces a 2-week SLA for quarantined flaky tests, automatically deleting unresolved flaky tests to prevent test suite degradation.
  • Zero-Tolerance Guardrails: Blocks silent failures, enforces a 30-minute suite budget, and requires containerized E2E runs before deployment to catch build and environment issues early. Use Case: A SaaS team can use this skill to run their full E2E suite across 4 CI shards, capture failure traces automatically, quarantine flaky tests, and generate a merged HTML report for quick debugging.

Quick Start

Use the e2e-test-runner skill to execute your project's end-to-end test suite and generate a merged report with failure traces and screenshots.

Frequently Asked Questions about e2e-test-runner

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

FAQPage Schema
How do I run Playwright and Cypress tests in CI with sharding and artifact capture?▼

You can run Playwright and Cypress tests in CI with sharding and artifact capture by using automated e2e-test-runner defaults. It handles test sharding, retry logic, and collects traces, screenshots, and videos for debuggable test runs.

What is the best way to quarantine flaky tests in a continuous integration pipeline?▼

The best way to quarantine flaky tests in a CI pipeline is to enforce a 2-week SLA for quarantined tests. This skill automatically quarantines flaky tests and deletes unresolved ones to prevent test suite degradation.

How do you enforce a time limit on an E2E browser testing suite?▼

You enforce a time limit on an E2E browser testing suite by applying a 30-minute suite budget. This skill enforces this budget and uses zero-tolerance guardrails to block silent or untriagable test failures.

Does this E2E test runner support containerized test runs before deployment?▼

Yes, this E2E test runner supports containerized test runs before deployment. It requires containerized execution to catch build and environment issues early, aligning with CI-optimized zero-tolerance guardrails.

Why do my end-to-end tests fail silently in CI without leaving debugging artifacts?▼

End-to-end tests fail silently in CI when artifact collection is not configured. This skill eliminates silent failures by automatically capturing failure traces, screenshots, and videos to generate a merged HTML report.

Can I split a large Cypress or Playwright suite across multiple CI shards?▼

Yes, you can split a large Cypress or Playwright suite across multiple CI shards. This skill applies test sharding to distribute the execution and generate a merged report for quick debugging across all shards.