rdc-react-testing
Provides testing utilities for mocking and validating components and hooks built with @data-client/react.
Install
mkdir -p .claude/skills/rdc-react-testing && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/4197" && unzip -o skill.zip -d .claude/skills/rdc-react-testing && rm skill.zipInstalls to .claude/skills/rdc-react-testing
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Test @data-client/react with renderDataHook and mountDataClient - jest unit tests, fixtures, interceptors, MockResolver, mock responses, nock HTTP mocking, fake timers for polling/subscription tests, DataProvider test setup, hook and component testing. Use when writing or debugging tests for hooks, components, or resources built on @data-client/react.Key capabilities
- →Render hooks for testing
- →Mock API responses
- →Test mutations and side effects
- →Simulate error states
- →Test manager middleware
How it works
It provides utilities like renderDataHook and MockResolver to simulate the Data Client store and intercept network requests during tests.
Inputs & outputs
When to use rdc-react-testing
- →Write unit tests for custom hooks
- →Mock API responses for component tests
- →Verify cache behavior in tests
- →Test loading and error states
About rdc-react-testing
Configures test environments with fixtures and interceptors to simulate API behavior. It allows for reliable testing of data-fetching logic without actual network calls.
Test @data-client/react with renderDataHook - jest unit tests, fixtures, interceptors, mock responses, nock HTTP mocking, hook testing, component testing
When not to use it
- →Non-React testing environments
- →Testing logic unrelated to @data-client
Prerequisites
Limitations
- →Requires @data-client/react
- →Automatic cleanup is registered at module load
How it compares
It offers specialized testing utilities for Data Client hooks and components, avoiding the need for manual store mocking.
Compared to similar skills
rdc-react-testing side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| rdc-react-testing (this skill) | 1 | 4mo | Review | Advanced |
| ui-ux-expert-skill | 91 | 11mo | Review | Advanced |
| react-best-practices | 22 | 4mo | No flags | Intermediate |
| frontend-testing | 11 | 4mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by reactive
View all by reactive →You might also like
ui-ux-expert-skill
fercracix33
Technical workflow for implementing accessible React user interfaces with shadcn/ui, Tailwind CSS, and TanStack Query. Includes 6-phase process with mandatory Style Guide compliance, Context7 best practices consultation, Chrome DevTools validation, and WCAG 2.1 AA accessibility standards. Use after Test Agent, Implementer, and Supabase agents complete their work.
react-best-practices
redpanda-data
Client-side React performance optimization patterns.
frontend-testing
langgenius
Generate Vitest + React Testing Library tests for Dify frontend components, hooks, and utilities. Triggers on testing, spec files, coverage, Vitest, RTL, unit tests, integration tests, or write/review test requests.
ai-sdk
vercel
Answer questions about the AI SDK and help build AI-powered features. Use when developers: (1) Ask about AI SDK functions like generateText, streamText, ToolLoopAgent, embed, or tools, (2) Want to build AI agents, chatbots, RAG systems, or text generation features, (3) Have questions about AI providers (OpenAI, Anthropic, Google, etc.), streaming, tool calling, structured output, or embeddings, (4) Use React hooks like useChat or useCompletion. Triggers on: "AI SDK", "Vercel AI SDK", "generateText", "streamText", "add AI to my app", "build an agent", "tool calling", "structured output", "useChat".
feature-flags
Use when feature flag tests fail, flags need updating, understanding @gate pragmas, debugging channel-specific test failures, or adding new flags to React.
playwright-validation
open-metadata
Use when validating UI changes in a branch require Playwright E2E testing. Reviews branch changes, validates UI with Playwright MCP, and adds missing test cases.