vitest
Vitest testing framework patterns for test setup, async testing, mocking with vi.*, snapshots, and test performance (formerly test-vitest). This skill should be used when writing or debugging Vitest tests. This...
Découvrez les skills testing security testing, comparez leurs dépôts et consultez leurs instructions.
Vitest testing framework patterns for test setup, async testing, mocking with vi.*, snapshots, and test performance (formerly test-vitest). This skill should be used when writing or debugging Vitest tests. This...
Playwright testing best practices for Next.js applications (formerly test-playwright). This skill should be used when writing, reviewing, or debugging E2E tests with Playwright. Triggers on tasks involving test...
Test-Driven Development methodology and red-green-refactor workflow (formerly test-tdd). This skill should be used when practicing TDD, writing tests first, designing tests before implementation, or reviewing t...
MSW (Mock Service Worker) best practices for API mocking in tests (formerly test-msw). This skill should be used when setting up MSW, writing request handlers, or mocking HTTP APIs. This skill does NOT cover ge...
Use when writing or changing tests, adding mocks - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies
Use to audit test quality with Google Fellow SRE scrutiny - identifies tautological tests, coverage gaming, weak assertions, missing corner cases. Creates bd epic with tasks for improvements, then runs SRE task...
Use when implementing features or fixing bugs - enforces RED-GREEN-REFACTOR cycle requiring tests to fail before writing code
Systematically inspect unit and E2E tests to verify they test the right behavior, provide meaningful coverage, and catch real regressions
Automated webapp testing with Playwright. Server management, UI testing, visual debugging, and reconnaissance-first approach.
Never test mock behavior. Never add test-only methods to production classes. Understand dependencies before mocking.
Write the test first, watch it fail, write minimal code to pass
Add new example use cases to the Examples feature
Run tests with local database setup and repository pattern
Use this skill for browser automation, E2E testing, visual regression testing, and web application testing with Playwright or similar tools.
Write tests for Dojo models and systems using spawn_test_world, cheat codes, and assertions. Use when testing game logic, verifying state changes, or ensuring system correctness.
Generate workflow templates with coherent node graphs and integration tests
Your approach to handling testing unit tests. Use this skill when working on files where testing unit tests comes into play.
Your approach to handling testing coverage. Use this skill when working on files where testing coverage comes into play.
Your approach to handling testing test writing. Use this skill when working on files where testing test writing comes into play.
Provides Playwright MCP testing workflow for the web application. Use when testing UI changes, verifying chat functionality, debugging frontend issues, or validating state transitions in the browser.
A valid test skill with proper formatting. This skill should pass all validations and serves as a reference for the expected format.
Comprehensive Flutter testing guidance covering unit tests, widget tests, and integration tests. Use when working with Flutter applications to write unit tests for functions/methods/classes, create widget tests...
Automatically suggest tests for new functions and components. Use when new code is written, functions added, or user mentions testing. Creates test scaffolding with Jest, Vitest, Pytest patterns. Triggers on ne...
Before declaring any task complete, actually verify the outcome. Run the code. Test the fix. Check the output. Claude's training optimizes for plausible-looking output, not verified-correct output. This skill f...
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.