Test

What This Skill Does

This skill executes tests for a React codebase, allowing users to specify the channel (source, experimental, stable, classic, or www) and a test pattern. It's designed for developers who need to validate their code changes against different React environments and configurations.

When to Use

• Validate a bug fix in the stable release channel.
• Test a new feature with experimental flags enabled.
• Verify code changes against the www-modern channel.
• Run tests in watch mode during development (TDD).
• Confirm compatibility with legacy www-classic.
• Check for regressions after refactoring code.

Key Features

• Supports multiple release channels (source, experimental, stable, classic, www).
• Allows specifying a test pattern to run specific tests.
• Uses --silent flag to limit output to failures.
• Uses --no-watchman to avoid sandboxing issues.
• Provides examples for common usage scenarios.
• Offers guidance on common mistakes to avoid.

Arguments: $ARGUMENTS: Channel, flags, and test pattern Usage Examples: /test React Fiber Hooks - Run with source channel (default) /test experimental React Fiber Hooks - Run with experimental channel /test www React Fiber Hooks - Run with www-modern channel /test www variant false React Fiber Hooks - Test VARIANT=false /test stable React Fiber Hooks - Run with stable channel /test classic React Fiber Hooks - Run with www-classic channel /test watch React Fiber Hooks - Run in watch mode (TDD) Release Channels: (default) - Source/canary channel, uses React Feature Flags.js defaults experimental - Source/experimental channel with EXPERIMENTAL flags = true www - www-modern channel with VARIANT flags = true www variant false - www channel with VARIANT flags = false stable - What ships to npm classic - Legacy www-classic (rarely needed) Instructions: Parse channel from arguments (default: source) Map to yarn command:

• (default) → yarn test --silent --no-watchman
• experimental → yarn test -r=experimental --silent --no-watchman
• stable → yarn test-stable --silent --no-watchman
• classic → yarn test-classic --silent --no-watchman
• www → yarn test-www --silent --no-watchman
• www variant false → yarn test-www --variant=false --silent --no-watchman Report test results and any failures Hard Rules: Use --silent to see failures - This limits the test output to only failures. Use --no-watchman - This is a common failure in sandboxing. Common Mistakes: Running without a pattern - Runs ALL tests, very slow. Always specify a pattern. Forgetting both www variants - Test www AND www variant false for VARIANT flags. Test skipped unexpectedly - Check for @gate pragma; see feature-flags skill.Run tests for the React codebase. Arguments: $ARGUMENTS: Channel, flags, and test pattern Usage Examples: /test React Fiber Hooks - Run with source channel (default) /test experimental React Fiber Hooks - Run with experimental channel /test www React Fiber Hooks - Run with www-modern channel /test www variant false React Fiber Hooks - Test VARIANT=false /test stable React Fiber Hooks - Run with stable channel /test classic React Fiber Hooks - Run with www-classic channel /test watch React Fiber Hooks - Run in watch mode (TDD) Release Channels: (default) - Source/canary channel, uses React Feature Flags.js defaults experimental - Source/experimental channel with EXPERIMENTAL flags = true www - www-modern channel with VARIANT flags = true www variant false - www channel with VARIANT flags = false stable - What ships to npm classic - Legacy www-classic (rarely needed) Instructions: Parse channel from arguments (default: source) Map to yarn command:
• (default) → yarn test --silent --no-watchman
• experimental → yarn test -r=experimental --silent --no-watchman
• stable → yarn test-stable --silent --no-watchman
• classic → yarn test-classic --silent --no-watchman
• www → yarn test-www --silent --no-watchman
• www variant false → yarn test-www --variant=false --silent --no-watchman Report test results and any failures Hard Rules: Use --silent to see failures - This limits the test output to only failures. Use --no-watchman - This is a common failure in sandboxing. Common Mistakes: Running without a pattern - Runs ALL tests, very slow. Always specify a pattern. Forgetting both www variants - Test www AND www variant false for VARIANT flags. Test skipped unexpectedly - Check for @gate pragma; see feature-flags skill.