testing-vitest

Étoiles4

Forks0

Mis à jour4 juillet 2026 à 10:30

Use when writing or configuring Vitest unit tests in TypeScript or TSX files. Covers mocking patterns, setup files, snapshots, coverage, and DOM testing.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

Adimac93

Adimac93/built-with-ai

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Analystes en assurance qualité des logiciels et testeursProfessions informatiques et mathématiques·SOC 15-1253

SKILL.md

readonly

name	testing-vitest
description	Use when writing or configuring Vitest unit tests in TypeScript or TSX files. Covers mocking patterns, setup files, snapshots, coverage, and DOM testing.

Vitest Guidelines

Use vi.fn() for function mocks, vi.spyOn() to monitor existing functions, vi.stubGlobal() for global mocks
Prefer spies over mocks when you only need to verify interactions without changing behavior
Place vi.mock() factory functions at the top level — the factory runs before imports are processed
Use mockImplementation() or mockReturnValue() for dynamic control during tests
Define global mocks, custom matchers, and environment setup in setup files referenced in vitest.config.ts
Use inline snapshots (toMatchInlineSnapshot()) for readable assertions visible in code review
Configure coverage thresholds in vitest.config.ts only when asked; focus on meaningful tests over percentages
Run vitest --watch during development for instant feedback; use -t to filter specific tests
Use vitest --ui to navigate large test suites visually during development
Set environment: 'jsdom' for frontend component tests; combine with testing-library for user interaction simulation
Group related tests with describe blocks; follow Arrange-Act-Assert pattern
Use expectTypeOf() for type-level assertions; ensure mocks preserve original type signatures

Plus depuis ce dépôt

même dépôt

coding-practices-git

Adimac93/built-with-ai

Use when committing to the repository, writing commit messages, naming branches, structuring commits, or managing git history.

2026-07-044

coding-practices-github

Adimac93/built-with-ai

Use when changing GitHub configuration, setting up branch protection rules, configuring CODEOWNERS, pull request templates, or GitHub repository settings.

2026-07-044

coding-practices-monorepo

Adimac93/built-with-ai

Use when creating a new package, changing workspace configuration, setting up shared tooling, or making decisions about monorepo structure and package boundaries.

2026-07-044

devops-github-actions

Adimac93/built-with-ai

Use when configuring GitHub Actions workflows, writing CI/CD pipelines, setting up composite actions, or managing workflow secrets and environment variables.

2026-07-044

frontend-angular

Adimac93/built-with-ai

Use when writing Angular TypeScript or HTML template files. Covers modern Angular patterns: standalone components, signals, inject(), control flow syntax, and lazy loading.

2026-07-044

frontend-aria

Adimac93/built-with-ai

Use when writing front-end components that require ARIA attributes, accessible custom widgets, screen reader support, or dynamic content announcements.

2026-07-044

name	testing-vitest
description	Use when writing or configuring Vitest unit tests in TypeScript or TSX files. Covers mocking patterns, setup files, snapshots, coverage, and DOM testing.

Vitest Guidelines

Use vi.fn() for function mocks, vi.spyOn() to monitor existing functions, vi.stubGlobal() for global mocks
Prefer spies over mocks when you only need to verify interactions without changing behavior
Place vi.mock() factory functions at the top level — the factory runs before imports are processed
Use mockImplementation() or mockReturnValue() for dynamic control during tests
Define global mocks, custom matchers, and environment setup in setup files referenced in vitest.config.ts
Use inline snapshots (toMatchInlineSnapshot()) for readable assertions visible in code review
Configure coverage thresholds in vitest.config.ts only when asked; focus on meaningful tests over percentages
Run vitest --watch during development for instant feedback; use -t to filter specific tests
Use vitest --ui to navigate large test suites visually during development
Set environment: 'jsdom' for frontend component tests; combine with testing-library for user interaction simulation
Group related tests with describe blocks; follow Arrange-Act-Assert pattern
Use expectTypeOf() for type-level assertions; ensure mocks preserve original type signatures