Status: Production Ready
Works with
Last Updated: 2026-02-06
Version: 16.x
User Event: 14.x
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiontesting-libraryExecute the skills CLI command in your project's root directory to begin installation:
Fetches testing-library from jezweb/claude-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate testing-library. Access via /testing-library in your agent's command palette.
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 environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
695
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
695
stars
Status: Production Ready Last Updated: 2026-02-06 Version: 16.x User Event: 14.x
# 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
import '@testing-library/jest-dom/vitest';
import { cleanup } from '@testing-library/react';
import { afterEach } from 'vitest';
// Cleanup after each test
afterEach(() => {
cleanup();
});
// vitest.config.ts
export default defineConfig({
test: {
globals: true,
environment: 'jsdom',
setupFiles: ['./src/test/setup.ts'],
},
});
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 |
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');
| 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 |
// 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');
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',
});
});
});
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(elementPrerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
jezweb/claude-skills
jezweb/claude-skills
jezweb/claude-skills
jezweb/claude-skills
jezweb/claude-skills
jezweb/claude-skills
testing-library reduced setup friction for our internal harness; good balance of opinion and flexibility.
Keeps context tight: testing-library is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for testing-library matched our evaluation — installs cleanly and behaves as described in the markdown.
I recommend testing-library for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
testing-library has been reliable in day-to-day use. Documentation quality is above average for community skills.
testing-library is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Useful defaults in testing-library — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Keeps context tight: testing-library is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend testing-library for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
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