React Testing
React component testing patterns: React Testing Library, Vitest/Jest, MSW network mocking, axe accessibility, and the RTL vs E2E decision boundary.
- What
- React component testing patterns: React Testing Library, Vitest/Jest, MSW network mocking, axe accessibility, and the RTL vs E2E decision boundary.
- Cost
- Free
- Needs
- Use "React Testing" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: a testing skill for writing React component tests that check behavior, not implementation details. It covers the core principle (test what the user sees and does), component tests with React Testing Library, custom hook tests, accessibility assertions with axe, network-level mocking with MSW, and the decision boundary between RTL component tests, Playwright component testing, and full Cypress/Playwright end-to-end runs. It also guides migration from Enzyme and class-component-era patterns, and setting up Vitest or Jest for a new React project. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: pure guidance, nothing to install; assumes a React project with a test runner; examples follow modern RTL idioms, legacy Enzyme suites need translation. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseThe install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Use "React Testing" with your Muse. Prerequisites: a React codebase with a test runner (Vitest or Jest). Pure guidance skill, nothing to install. 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/react-testing/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Write behavior-focused tests for this component following these patterns: user-visible behavior, MSW for network, axe for accessibility." 3. For test strategy questions, ask: "Should this be an RTL component test or a full E2E run? Apply the decision boundary." Tip: paste one component (plus its current test file, if any) at a time. Safety: a skill is plain-text instructions; it runs nothing by itself. Review generated tests before trusting them, especially assertions around async behavior.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.