table-testing
Table-driven testing patterns using @kitz/test. Triggers on creating test cases, parameterized tests, or when writing .test.ts files.
Table-driven testing patterns using @kitz/test. Triggers on creating test cases, parameterized tests, or when writing .test.ts files.
Use when writing or changing tests, adding mocks, or tempted to add test-only methods to production code - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies
Comprehensive web application testing using Playwright. Tests accessibility (WCAG 2.1 AA), UX principles, and functional correctness. Generates reusable test files for CI/CD integration.
Unit and component testing for Umbraco backoffice extensions using @open-wc/testing
Gate 6 - Verify tests exist and cover critical paths. Issues result in WARNINGS (encourages tests, doesn't block).
Use when writing unit tests, adopting Swift Testing framework, making tests run faster without simulator, architecting code for testability, testing async code reliably, or migrating from XCTest - covers @Test/@Suite macros,
The agent automatically generates comprehensive test tasks from feature requirements, ensuring every implementation task has corresponding test coverage with proper acceptance criteria.
Use this skill to diagnose and repair broken tests with a methodical, surgical approach. AUTO-ACTIVATE when user mentions (FR/EN): - test cassรฉ, broken test, failing test, test fail, test รฉchoue - erreur test, test error, assertion failed, timeout test - rรฉparer test, fix test, corriger test, debug test - npm test fail, jest error, test suite failed AGENTS: Specialized agents (backend-specialist, frontend-specialist, database-specialist) MUST invoke this skill when asked to fix tests. Use: Skill("test-doctor") CRITICAL: NO mass corrections. ONE test at a time with validation. ALWAYS diagnose before fixing. ALWAYS consult DONT_DO.md first. Context: 1211 test files, 5561/6101 passing (540 failing). Stack: Jest, React Testing Library, Prisma, Next.js 15, TypeScript 5.
Write feature tests for HTTP endpoints, controllers, and full request/response cycles using Pest v4. Use when ANY business logic is added to codebase. Feature tests are the PRIMARY testing approach - use for all Controllers, Actions, Form Requests, and application behavior. This is your default testing strategy.
Create mocks using mockall and trait-based abstractions. Use when unit testing code with external dependencies.
Component documentation, visual testing, interaction testing
TDD London School (mockist) specialist for mock-driven, outside-in development. Use for behavior verification testing, contract-driven development, testing object collaborations, or when focusing on HOW objects interact rather than WHAT they contain.
Guide TDD workflow, design tests, and create mocking strategies
cloudflare-operator ็ซฏๅฐ็ซฏๆต่ฏใๆๅฏผ้ๅฏน็ๅฎ Cloudflare API ๆต่ฏ CRDใ้็จไบๆต่ฏ Operator ๅ่ฝใ้ช่ฏ CRD ๆ่ฟ่ก้ๆๆต่ฏใ
ใในใใขใผใญใใฏใใฃ่ชๅพ้ฉ็จSkillใADR_020ใฌใคใคใผรใในใใฟใคใๅ้ขๆนๅผใปๅฝๅ่ฆๅใปๅ็ ง้ขไฟๅๅใปๆฐ่ฆใในใใใญใธใงใฏใไฝๆใใงใใฏใชในใ้ฉ็จใunit-test/integration-test Agentไฝๆฅญๆใปๆฐ่ฆใในใใใญใธใงใฏใไฝๆๆใซไฝฟ็จใ
Reference for @umbraco/playwright-testhelpers package - fixtures, API helpers, and UI helpers for E2E testing
Creates NixOS VM-based integration tests using testers.runNixOSTest with OpenTelemetry observability. Use when writing isolated system tests for Sway, daemons, multi-machine networking, or any NixOS feature requiring QEMU VM testing with full telemetry to Grafana.
End-to-end testing using Playwright MCP. Automate user workflows, take screenshots, validate UI/UX, perform visual regression testing, and verify complete user journeys. Use after feature implementation or before deployment.
Playwright ๋ธ๋ผ์ฐ์ ์๋ํ ๋ํผ. MCP ๋์ CLI ์ง์ ํธ์ถ. E2E ํ ์คํธ, ์คํฌ๋ฆฐ์ท, ์น ์๋ํ์ ์ฌ์ฉ.
"Custom test patterns and fixtures for {project}. Covers E2E, integration, and specialized testing requirements."