<< All versions
Skill v1.0.1
currentAutomated scan100/100aj-geddes/useful-ai-prompts/frontend-testing
9 files
──Details
PublishedMay 14, 2026 at 09:46 PM
Content Hashsha256:137887fa0337785f...
Git SHA3f5182cfd739
Bump Typepatch
──Files
Files (1 file, 2.5 KB)
SKILL.md2.5 KBactive
SKILL.md · 92 lines · 2.5 KB
version: "1.0.1" name: frontend-testing description: > Implement comprehensive frontend testing using Jest, Vitest, React Testing Library, and Cypress. Use when building robust test suites for UI and integration tests.
Frontend Testing
Table of Contents
Overview
Build comprehensive test suites for frontend applications including unit tests, integration tests, and end-to-end tests with proper coverage and assertions.
When to Use
- Component testing
- Integration testing
- End-to-end testing
- Regression prevention
- Quality assurance
- Test-driven development
Quick Start
Minimal working example:
typescript
// Button.test.tsximport { render, screen, fireEvent } from '@testing-library/react';import '@testing-library/jest-dom';import { Button } from './Button';describe('Button Component', () => {it('renders button with text', () => {render(<Button>Click me</Button>);expect(screen.getByRole('button')).toHaveTextContent('Click me');});it('calls onClick handler when clicked', () => {const handleClick = jest.fn();render(<Button onClick={handleClick}>Click</Button>);fireEvent.click(screen.getByRole('button'));expect(handleClick).toHaveBeenCalledTimes(1);});it('disables button when disabled prop is true', () => {render(<Button disabled>Click me</Button>);expect(screen.getByRole('button')).toBeDisabled();});it('applies variant styles correctly', () => {// ... (see reference guides for full implementation)
Reference Guides
Detailed implementations in the references/ directory:
| Guide | Contents | |
|---|---|---|
| Jest Unit Testing (React) | Jest Unit Testing (React) | |
| React Testing Library Integration Tests | React Testing Library Integration Tests | |
| Vitest for Vue Testing | Vitest for Vue Testing | |
| Cypress E2E Testing | Cypress E2E Testing | |
| Test Coverage Configuration | Test Coverage Configuration |
Best Practices
✅ DO
- Follow established patterns and conventions
- Write clean, maintainable code
- Add appropriate documentation
- Test thoroughly before deploying
❌ DON'T
- Skip testing or validation
- Ignore error handling
- Hard-code configuration values