test▌
facebook/react · updated Apr 8, 2026
Run tests for React codebase across multiple release channels and configurations.
- ›Supports six release channels: source (default), experimental, www, www with variant false, stable, and classic, each with distinct feature flag configurations
- ›Accepts test patterns, watch mode for TDD, and variant flags to test different code paths
- ›Requires explicit test pattern argument to avoid running the entire test suite; uses --silent flag to surface failures and --no-watchman for sandboxing comp
Run tests for the React codebase.
Arguments:
- $ARGUMENTS: Channel, flags, and test pattern
Usage Examples:
/test ReactFiberHooks- Run with source channel (default)/test experimental ReactFiberHooks- Run with experimental channel/test www ReactFiberHooks- Run with www-modern channel/test www variant false ReactFiberHooks- Test VARIANT=false/test stable ReactFiberHooks- Run with stable channel/test classic ReactFiberHooks- Run with www-classic channel/test watch ReactFiberHooks- Run in watch mode (TDD)
Release Channels:
(default)- Source/canary channel, uses ReactFeatureFlags.js defaultsexperimental- Source/experimental channel with EXPERIMENTAL flags = truewww- www-modern channel with VARIANT flags = truewww variant false- www channel with VARIANT flags = falsestable- What ships to npmclassic- Legacy www-classic (rarely needed)
Instructions:
- Parse channel from arguments (default: source)
- Map to yarn command:
- (default) →
yarn test --silent --no-watchman <pattern> - experimental →
yarn test -r=experimental --silent --no-watchman <pattern> - stable →
yarn test-stable --silent --no-watchman <pattern> - classic →
yarn test-classic --silent --no-watchman <pattern> - www →
yarn test-www --silent --no-watchman <pattern> - www variant false →
yarn test-www --variant=false --silent --no-watchman <pattern>
- (default) →
- 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
wwwANDwww variant falsefor__VARIANT__flags. - Test skipped unexpectedly - Check for
@gatepragma; seefeature-flagsskill.
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.4★★★★★33 reviews- ★★★★★Hana Park· Dec 20, 2024
test has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Pratham Ware· Dec 8, 2024
Registry listing for test matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Omar Mehta· Dec 4, 2024
Keeps context tight: test is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Yash Thakker· Nov 27, 2024
test reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Emma Rahman· Nov 23, 2024
test is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Aditi Bhatia· Nov 7, 2024
Useful defaults in test — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Mia Jackson· Nov 7, 2024
Solid pick for teams standardizing on skills: test is focused, and the summary matches what you get after install.
- ★★★★★Aanya Rahman· Oct 26, 2024
test is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Sophia Shah· Oct 26, 2024
We added test from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Dhruvi Jain· Oct 18, 2024
I recommend test for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 33