testing
/testing
Pisze testy komponentów: Vitest, Testing Library, jest-axe, Playwright, stories w Storybook i zasady mocków, z asercjami dostępności.
- Autor
- krishna-modi12 ↗
- Repozytorium
- frontend-design-pro ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 20.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 8
- Skrypty
- 4
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 20.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
- 4 skrypty w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.
Skrypty: examples/_r3f-jsx.d.ts, examples/_stubs.d.ts, examples/good-playwright.test.tsx, examples/good-playwright.tsx
Co robi i kiedy
Pisze testy komponentów: Vitest, Testing Library, jest-axe, Playwright, stories w Storybook i zasady mocków, z asercjami dostępności.
Oryginalny opis (EN)
Component testing — Vitest, Testing Library, jest-axe, Playwright e2e, Storybook stories, mock policy. Use when writing or augmenting tests — unit and interaction tests, accessibility assertions, end-to-end flows, Storybook stories, test setup and mocking — or when a component has been delivered without coverage.
Jak działa
- When to Use
- Stack
- Core Rules
- Patterns
- Examples
- Reference Index
- Constraints
Podgląd SKILL.md
---
name: testing
description: Component testing — Vitest, Testing Library, jest-axe, Playwright e2e, Storybook stories, mock policy. Use when writing or augmenting tests — unit and interaction tests, accessibility assertions, end-to-end flows, Storybook stories, test setup and mocking — or when a component has been delivered without coverage.
metadata:
version: "15.0.0"
core-deps:
- core/component-api.md
- core/validate-checklist.md
---
# Testing
## When to Use
Writing or augmenting tests: unit/interaction tests, accessibility assertions, end-to-end flows, Storybook stories, test setup and mocking. Also when a component is delivered without coverage — every shipped component needs a test.
## Stack
Vitest + jsdom · `@testing-library/react` + `user-event` · `jest-axe` · Playwright (e2e) · Storybook 8 CSF3
## Core Rules
1. **Untested UI is incomplete UI.** A component is done when a test asserts the behaviour a user depends on — not when it renders.
2. **Test the public contract**, never implementation. Assert on rendered roles and text, never on state variable names or class strings.
3. **Query priority:** `getByRole` > `getByLabelText` > `getByText` > `getByTestId`. If you can't find it by role, neither can a screen reader — that's a finding, not a test problem.
4. **`userEvent`, not `fireEvent`,** for flows — it fires the full focus/keydown/keyup sequence a real user produces.
5. **Every component gets three tests minimum:** renders (asserting real DOM), one role-based interaction, one `jest-axe` pass.
6. **Mock the dependency, never the component under test.** Typed stubs only — no `any`.
7. **No arbitrary waits.** `await screen.findBy…` or `waitFor`, never `setTimeout`.
8. **No placeholder assertions.** `expect(true).toBe(true)` is not a test.
9. **Per component type:** forms assert error wiring via `aria-describedby`; data components assert the empty state; overlays assert focus return and `aria-hidden` on siblings; interactive components assert keyboard activation.
## Patterns
- **Mock policy** — `motion/react` → passthrough proxy; `next/navigation` → stub router; R3F/drei/`three` → `Canvas` becomes a `<div>` (no WebGL in jsdom); TanStack Query → real provider, mocked fetch; recharts → sized `<div>`.
- **axe pass** — `expect(await axe(container)).toHaveNoViolations()` on mounted DOM; open overlays first.
- **Play functions** — Storybook CSF3 `play` with `userEvent` doubles as an interaction test.
- **e2e** — Playwright with role selectors, `checkA11y`, network mocking, keyboard/focus assertions.
## Examples
Every gold example across all skills ships a colocated `*.test.tsx` — read any of them as a reference implementation. `examples/good-playwright.tsx` demonstrates an e2e dashboard surface.
## Reference Index
Load only for the specific task:
| Task | Load |
|---|---|
| Doctrine, stack, per-type requirements, mock policy, anti-patterns | `references/testing.md` |
| Playwright: role selectors, visual regression, axe, CI config | `references/playwright.md` |
| Storybook 8 CSF3, argTypes, decorators, autodocs, Chromatic | `references/storybook.md` |
## Constraints
Zero `any` in test files · zero placeholder assertions · role-based queries first · typed mocks · every gold has a colocated `.test.tsx` (release Gate 7) · tests compile under `tsc --noEmit --strict`.
Pliki w paczce (8)
- SKILL.md 3 KB
- examples/_r3f-jsx.d.ts 2 KB
- examples/_stubs.d.ts 4 KB
- examples/good-playwright.test.tsx 1 KB
- examples/good-playwright.tsx 22 KB
- references/playwright.md 20 KB
- references/storybook.md 26 KB
- references/testing.md 4 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · krishna-modi12/frontend-design-pro | 100 | MIT |
| iuliandita/skills | 100 | MIT |
| wrongstack/wrongstack | 100 | MIT |
| langwatch/langwatch | 100 | Apache-2.0 |
| mcouthon/agents | 100 | MIT |
| nteract/nteract | 100 | BSD-3-Clause |
| kettleofketchup/DraftForge | 100 | GPL-3.0 |
| skillberry-ai/cap-evolve | 100 | Apache-2.0 |
| TheBeardedBearSAS/claude-craft | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki bd7c31a5df77 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100react-testing
Opisuje testowanie komponentów React z React Testing Library, Vitest lub Jest, MSW, asercjami dostępności z axe oraz granicą między testami komponentów a E2E w Playwright i Cypress. - 100react-testing
Prowadzi testy komponentów React w Testing Library, Vitest lub Jest, z MSW do mockowania sieci i axe do dostępności. - 100react-testing
Przygotowuje testy komponentów React w Testing Library, mocki sieci w MSW i sprawdzenie dostępności przez axe. - 100react-testing
Pomaga testować komponenty React w Testing Library, Vitest lub Jest, z MSW i axe, oraz wybrać Playwright albo Cypress. - 100fe-testing
Pisze stabilne testy front-endu z własnym runnerem: testy jednostkowe i komponentów z Testing Library, e2e z Playwrightem i skany dostępności. - 100react-testing
Pisze testy komponentów React z React Testing Library, Vitest lub Jest, mockami sieci przez MSW i asercjami dostępności przez axe.