writing-tests
Write unit tests and integration tests for Go code using testify, go-sqlmock, and mockery. Use when writing tests, creating test files, or testing repositories, use cases, and handlers.
Write unit tests and integration tests for Go code using testify, go-sqlmock, and mockery. Use when writing tests, creating test files, or testing repositories, use cases, and handlers.
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first
Implement comprehensive testing strategies using Jest, Vitest, and Testing Library for unit tests, integration tests, and end-to-end testing with mocking, fixtures, and test-driven development. Use when writing JavaScript/TypeScript tests, setting up test infrastructure, or implementing TDD/BDD workflows.
Generates integration tests for frontend → backend → Genkit flow connections. Use when creating E2E API tests.
This skill should be used when the user asks about testing Rails applications, Minitest, test-driven development (TDD), unit tests, integration tests, system tests, fixtures, factories, mocking, stubbing, test coverage, continuous integration, test organization, or Rails testing best practices. Also use when discussing testing philosophy, test speed, or debugging failing tests. Examples:
Apply when implementing new features, fixing bugs, or refactoring code. TDD ensures tests drive design and all code is covered.
Skill with external file references for testing detection
Mutation testing with Stryker to verify test quality by introducing code mutations and measuring detection rates
Use when writing tests for Flutter code - follows priority-based testing (Repository → State → Widget) after implementation
Generate Vitest + React Testing Library tests for Desktop Ethereal frontend components, hooks, and utilities. Triggers on testing, spec files, coverage, Vitest, RTL, unit tests, integration tests, or write/review test requests.
Use when implementing features to write effective tests. Encourages test-first but allows prototyping.
Provides Android testing patterns and templates for JUnit5, MockK, Turbine, and Compose UI testing. Use when writing tests, implementing TDD, validating code coverage, or reviewing test quality. Use when user mentions: 테스트, TDD, 단위 테스트, UI 테스트, 커버리지, 목(mock), 테스트 작성, 테스트 템플릿, ViewModel 테스트, UseCase 테스트, Compose 테스트.
在声称工作完成、修复或通过之前使用,在提交或创建 PR 之前。需要运行验证命令并确认输出后才能声称成功。证据先于断言。Use when about to claim work is complete - evidence before assertions always.
Generate comprehensive test data for local development using Snaplet and Supabase. Use when adding database schema changes, implementing new features, or creating edge case scenarios. Ensures reproducible test environments with realistic data covering happy paths, error cases, and RLS policies.
Expert in creating comprehensive pytest test suites for Drift project with strict 90%+ coverage requirements. Specializes in unit tests, integration tests, mocking external APIs (Anthropic, AWS Bedrock), and coverage validation using pytest-cov. Use when writing tests, test fixtures, validating test coverage, or implementing mocking strategies for external dependencies.
Type assertion patterns using @kitz/assert. Triggers on type-level tests, .test-d.ts files, or when asserting TypeScript types.
质量验收专家,从用户视角验证交付物可用性/正确性/性能/回归。遵循阻断不合格交付、脚本化验证、数据隔离、覆盖验收标准的工程基线。使用 Playwright(E2E)、Jest+Supertest(API)、k6(性能)等工具。适用于收到 QA 部门任务卡(如 CMS-Q-001)或需要验收交付物时使用。
Generates TDD-ready acceptance criteria from screen spec.md. Extracts requirements from features, interactions, flows, and API mappings in Given-When-Then format. Use when creating implementation task specifications.
Guide experienced developers on test structure, patterns, assertions, and test doubles for effective test-driven development
Guide for testing service layer. Use when asked to test services. Directs to implementation-specific testing skills.
Use when creating new skills, editing existing skills, or verifying skills work before deployment - applies TDD to process documentation by testing with subagents before writing, iterating until bulletproof against rationalization