What happens if a test passes in dev but fails in production?

The skill provides a specific 'pnpm dev:prod' workflow to debug bundling issues and package export problems that only appear in production builds.

Does this skill work with Playwright and Vitest?

Yes, it includes specific commands for running both Playwright E2E suites and Vitest integration tests.

How does it handle port conflicts?

The workflow automatically identifies and kills processes on port 3000 before starting new test servers to ensure a clean environment.

What is the 'Iron Law' of this skill?

The Iron Law dictates that you must never propose a fix without reproducing the failure locally first. Analyzing logs is not a substitute for execution.

How do I verify a fix is no longer flaky?

The skill includes a verification step that runs the specific failing test multiple times in a loop to ensure the race condition is truly resolved.

CI Test Triager

Name: CI Test Triager
Author: payloadcms

bypayloadcms

•

39,933

Seguridad y Pruebas

Systematically reproduces and debugs flaky CI test failures in Next.js and Playwright environments.

Acerca de

This skill provides a rigorous, mandatory workflow for triaging failed tests on the main branch, specifically targeting 'flaky' tests that pass locally but fail in CI environments. It enforces a strict 'reproduce before fixing' policy, guiding users through automated port management, dev server instantiation, specific test execution, and production build verification to isolate root causes like race conditions, bundling issues, or environment disparities.

Características Principales

Detection of race conditions and test pollution patterns
Automated port management and background server control
Mandatory reproduction-first workflow enforcement
39,933 GitHub stars
Dual-track testing for both development and production builds
Multi-run stability verification to ensure permanent fixes

Casos de Uso

Resolving race conditions in complex fullstack Next.js applications
Investigating intermittent Playwright E2E failures on GitHub Actions
Debugging tests that pass in development but fail when bundled for production

Acerca de

Características Principales

Detection of race conditions and test pollution patterns
Automated port management and background server control
Mandatory reproduction-first workflow enforcement
39,933 GitHub stars
Dual-track testing for both development and production builds
Multi-run stability verification to ensure permanent fixes

Casos de Uso

Resolving race conditions in complex fullstack Next.js applications
Investigating intermittent Playwright E2E failures on GitHub Actions
Debugging tests that pass in development but fail when bundled for production