testing-library▌
jezweb/claude-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Status: Production Ready
- ›Last Updated: 2026-02-06
- ›Version: 16.x
- ›User Event: 14.x
React Testing Library
Status: Production Ready Last Updated: 2026-02-06 Version: 16.x User Event: 14.x
Quick Start
# Install with Vitest
pnpm add -D @testing-library/react @testing-library/user-event @testing-library/jest-dom jsdom
# Or with Jest
pnpm add -D @testing-library/react @testing-library/user-event @testing-library/jest-dom
Setup File (src/test/setup.ts)
import '@testing-library/jest-dom/vitest';
import { cleanup } from '@testing-library/react';
import { afterEach } from 'vitest';
// Cleanup after each test
afterEach(() => {
cleanup();
});
Vitest Config
// vitest.config.ts
export default defineConfig({
test: {
globals: true,
environment: 'jsdom',
setupFiles: ['./src/test/setup.ts'],
},
});
Query Priority (Accessibility First)
Use queries in this order for accessible, resilient tests:
| Priority | Query | Use For |
|---|---|---|
| 1 | getByRole |
Buttons, links, headings, inputs |
| 2 | getByLabelText |
Form inputs with labels |
| 3 | getByPlaceholderText |
Inputs without visible labels |
| 4 | getByText |
Non-interactive text content |
| 5 | getByTestId |
Last resort only |
Examples
import { render, screen } from '@testing-library/react';
// ✅ GOOD - semantic role queries
screen.getByRole('button', { name: /submit/i });
screen.getByRole('heading', { level: 1 });
screen.getByRole('textbox', { name: /email/i });
screen.getByRole('link', { name: /learn more/i });
// ✅ GOOD - label-based queries for forms
screen.getByLabelText(/email address/i);
// ⚠️ OK - when no better option
screen.getByText(/welcome to our app/i);
// ❌ AVOID - not accessible, brittle
screen.getByTestId('submit-button');
Query Variants
| Variant | Returns | Throws | Use For |
|---|---|---|---|
getBy |
Element | Yes | Element exists now |
queryBy |
Element or null | No | Element might not exist |
findBy |
Promise | Yes | Async, appears later |
getAllBy |
Element[] | Yes | Multiple elements |
queryAllBy |
Element[] | No | Multiple or none |
findAllBy |
Promise<Element[]> | Yes | Multiple, async |
When to Use Each
// Element exists immediately
const button = screen.getByRole('button');
// Check element doesn't exist
expect(screen.queryByRole('dialog')).not.toBeInTheDocument();
// Wait for async element to appear
const modal = await screen.findByRole('dialog');
// Multiple elements
const items = screen.getAllByRole('listitem');
User Event (Realistic Interactions)
Always use userEvent over fireEvent - it simulates real user behavior.
import { render, screen } from '@testing-library/react';
import userEvent from '@testing-library/user-event';
describe('Form', () => {
it('submits form data', async () => {
const user = userEvent.setup();
const onSubmit = vi.fn();
render(<LoginForm onSubmit={onSubmit} />);
// Type in inputs
await user.type(screen.getByLabelText(/email/i), '[email protected]');
await user.type(screen.getByLabelText(/password/i), 'secret123');
// Click submit
await user.click(screen.getByRole('button', { name: /sign in/i }));
expect(onSubmit).toHaveBeenCalledWith({
email: '[email protected]',
password: 'secret123',
});
});
});
Common User Events
const user = userEvent.setup();
// Clicking
await user.click(element);
await user.dblClick(element);
await user.tripleClick(element); // Select all text
// Typing
await user.type(input, 'hello world');
await user.clear(input);
await user.type(input, '{Enter}'); // Special keys
// Keyboard
await user.keyboard('{Shift>}A{/Shift}'); // Shift+A
await user.tab(); // Tab navigation
// Selection
await user.selectOptions(select, ['option1', 'option2']);
// Hover
await user.hover(element);
await user.unhover(elementHow to use testing-library on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add testing-library
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches testing-library from GitHub repository jezweb/claude-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate testing-library. Access the skill through slash commands (e.g., /testing-library) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
Task Automation & Efficiency
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Knowledge Enhancement
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Quality Improvement
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Installation Steps
- 1.Install skill using provided installation command
- 2.Test with simple use case relevant to your work
- 3.Evaluate output quality and relevance
- 4.Iterate on prompts to improve results
- 5.Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices▌
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This▌
✓ Use When
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid When
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path▌
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★65 reviews- ★★★★★Ganesh Mohane· Dec 28, 2024
testing-library reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Shikha Mishra· Dec 24, 2024
Keeps context tight: testing-library is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Alexander Ndlovu· Dec 24, 2024
Registry listing for testing-library matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Aanya Desai· Dec 24, 2024
I recommend testing-library for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Hassan Martin· Dec 24, 2024
testing-library has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Aanya Johnson· Dec 20, 2024
testing-library is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Amina Kapoor· Dec 16, 2024
Useful defaults in testing-library — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Amina Jain· Dec 12, 2024
Keeps context tight: testing-library is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Sakshi Patil· Nov 19, 2024
I recommend testing-library for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Aanya Chawla· Nov 15, 2024
Useful defaults in testing-library — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 65