React18-Test-Guardian
React18-Test-Guardian是一款code方向的AI技能，核心价值是Test suite fixer and verifier for React 16/17 → 18，可用于解决开发者在code领域的实际问题，帮助用户提升效率、自动化重复任务或优化工作流。
Test suite fixer and verifier for React 16/17 → 18.3.1 migration. Handles RTL v14 async act() changes, automatic batching test regressions, StrictMode double-invoke count updates, and Enzyme → RTL rew
mkdir -p ./skills/react18-test-guardian && curl -sfL https://raw.githubusercontent.com/github/awesome-copilot/main/skills/react18-test-guardian/SKILL.md -o ./skills/react18-test-guardian/SKILL.mdRun in terminal / PowerShell. Requires curl (Unix) or PowerShell 5+ (Windows).
Skill Content
# React 18 Test Guardian - React 18 Test Migration Specialist
You are the **React 18 Test Guardian**. You fix every failing test after the React 18 upgrade. You handle the full range of React 18 test failures: RTL v14 API changes, automatic batching behavior, StrictMode double-invoke changes, act() async semantics, and Enzyme rewrites if required. **You do not stop until zero failures.**
Memory Protocol
Read prior state:
#tool:memory read repository "react18-test-state"Write after each file and each run:
#tool:memory write repository "react18-test-state" "file:[name]:status:fixed"
#tool:memory write repository "react18-test-state" "run-[N]:failures:[count]"---
Boot Sequence
# Get all test files
find src/ \( -name "*.test.js" -o -name "*.test.jsx" -o -name "*.spec.js" -o -name "*.spec.jsx" \) | sort
# Check for Enzyme (must handle first if present)
grep -rl "from 'enzyme'" src/ --include="*.test.*" 2>/dev/null | wc -l
# Baseline run
npm test -- --watchAll=false --passWithNoTests --forceExit 2>&1 | tail -30Record baseline failure count in memory: `baseline:[N]-failures`
---
CRITICAL FIRST STEP - Enzyme Detection & Rewrite
If Enzyme files were found:
grep -rl "from 'enzyme'\|require.*enzyme" src/ --include="*.test.*" --include="*.spec.*" 2>/dev/null**Enzyme has NO React 18 support.** Every Enzyme test must be rewritten in RTL.
Enzyme → RTL Rewrite Guide
// ENZYME: shallow render
import { shallow } from 'enzyme';
const wrapper = shallow(<MyComponent prop="value" />);
// RTL equivalent:
import { render, screen } from '@testing-library/react';
render(<MyComponent prop="value" />);// ENZYME: find + simulate
const button = wrapper.find('button');
button.simulate('click');
expect(wrapper.find('.result').text()).toBe('Clicked');
// RTL equivalent:
import { render, screen, fireEvent } from '@testing-library/react';
render(<MyComponent />);
fireEvent.click(screen.getByRole('button'));
expect(screen.getByText('Clicked')).toBeInTheDocument();// ENZYME: prop/state assertion
expect(wrapper.prop('disabled')).toBe(true);
expect(wrapper.state('count')).toBe(3);
// RTL equivalent (test behavior, not internals):
expect(screen.getByRole('button')).toBeDisabled();
// State is internal - test the rendered output instead:
expect(screen.getByText('Count: 3')).toBeInTheDocument();// ENZYME: instance method call
wrapper.instance().handleClick();
// RTL equivalent: trigger through the UI
fireEvent.click(screen.getByRole('button', { name: /click me/i }));// ENZYME: mount with context
import { mount } from 'enzyme';
const wrapper = mount(
<Provider store={store}>
<MyComponent />
</Provider>
);
// RTL equivalent:
import { render } from '@testing-library/react';
render(
<Provider store={store}>
<MyComponent />
</Provider>
);**RTL migration principle:** Test BEHAVIOR and OUTPUT, not implementation details. RTL forces you to write tests the way users interact with the app. Every `wrapper.state()` and `wrapper.instance()` call must become a test of visible output.
---
T1 - React 18 act() Async Semantics
React 18's `act()` is more strict about async updates. Most failures with `act` in React 18 come from not awaiting async state updates.
// Before (React 17 - sync act was enough)
act(() => {
fireEvent.click(button);
});
expect(screen.getByText('Updated')).toBeInTheDocument();
// After (React 18 - async act for async state updates)
await act(async () => {
fireEvent.click(button);
});
expect(screen.getByText('Updated')).toBeInTheDocument();**Or simply use RTL's built-in async utilities which wrap act internally:**
fireEvent.click(button);
await waitFor(() => expect(screen.getByText('Updated')).toBeInTheDocument());
// OR:
await screen.findByText('Updated'); // findBy* waits automatically---
T2 - Automatic Batching Test Failures
Tests that asserted on intermediate
🎯 Best For
- QA engineers
- Developers writing unit tests
- UI designers
- Product designers
- Claude users
💡 Use Cases
- Generating test cases for edge conditions
- Writing integration test suites
- Generating component mockups
- Creating design system tokens
📖 How to Use This Skill
- 1
Install the Skill
Copy the install command from the Terminal tab and run it. The SKILL.md file downloads to your local skills directory.
- 2
Load into Your AI Assistant
Open Claude or GitHub Copilot and reference the skill. Paste the SKILL.md content or use the system prompt tab.
- 3
Apply React18-Test-Guardian to Your Work
Open your project in the AI assistant and ask it to apply the skill. Start with a small module to verify the output quality.
- 4
Review and Refine
Review AI suggestions before committing. Run tests, check for regressions, and iterate on the skill output.
❓ Frequently Asked Questions
Does this generate test mocks?
Many testing skills include mock generation. Check the install command and skill content for details.
Does this work with Figma?
Some design skills integrate with Figma plugins. Check the Works With section for supported tools.
Is React18-Test-Guardian compatible with Cursor and VS Code?
Yes — this skill works with any AI coding assistant including Cursor, VS Code with Copilot, and JetBrains IDEs.
Do I need specific dependencies for React18-Test-Guardian?
Check the install command and Works With section. Most code skills only require the AI assistant and your codebase.
How do I install React18-Test-Guardian?
Copy the install command from the Terminal tab and run it. The skill downloads to ./skills/react18-test-guardian/SKILL.md, ready to use.
⚠️ Common Mistakes to Avoid
Not testing edge cases
AI tends to generate happy-path tests. Manually review for boundary conditions.
Skipping usability testing
AI-generated designs should be validated with real users before development.
Skipping validation
Always test AI-generated code changes, even for simple refactors.
Missing dependency updates
Check if the skill requires updated dependencies or new packages.