integration-test-patterns
Best practices for writing integration tests using Testcontainers and EF Core. Use when creating or modifying integration tests.
Best practices for writing integration tests using Testcontainers and EF Core. Use when creating or modifying integration tests.
Writing unit tests with vitest and vue-test-utils following project patterns. Use when creating tests for components, composables, utilities, or stores.
Strategies for exploring and testing tightly-coupled BitZero code. Use when code seems untestable, has singleton dependencies, or you need to understand complex game logic before writing tests.
Delegate fix verification to a QA agent. Use after implementing a fix when you want end-to-end verification without cluttering your context with build/test output.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Run regression testing suite to verify existing functionality still works after changes
**TDD GUARDIAN**: '테스트 작성', '테스트 만들어', 'TDD', '단위 테스트', '통합 테스트', '커버리지', 'mock', '모킹' 요청 시 자동 발동. *.test.ts/*.spec.ts/test_*.py 파일 작업 시 자동 적용. Fake Test 탐지, 80% 커버리지 게이트. Jest/Vitest/PyTest/JUnit 템플릿.
Test-Driven Development workflow. Use when implementing new features with tests first. Activated by "TDD", "test first", "write tests".
Use when tests have race conditions, timing dependencies, or inconsistent pass/fail behavior - replaces arbitrary timeouts with condition polling to wait for actual state changes, eliminating flaky tests from timing guesses
Expert stratégie et méthodologie de tests - pyramide, qualité et automatisation. Utilise ce skill quand: (1) définition d'une stratégie de tests, (2) tests unitaires, intégration, e2e, (3) tests de performance, (4) tests de sécurité, (5) tests d'accessibilité, (6) CI/CD et automatisation des tests.
Rust testing patterns (unit, integration, property-based)
Guide backend service and API testing for TapScore. Use when writing or running backend tests for services, database operations, or API endpoints. Ensures in-memory database testing and comprehensive CRUD coverage.
RPA workflow testing with Playwright browser automation. Covers page object model, wait strategies, screenshot testing, and browser node testing patterns. Use when: testing browser nodes, page object model, wait strategies, screenshot testing, visual regression, browser automation tests.
Write tests with Pest/PHPUnit, feature tests, unit tests, mocking, and factories. Use when testing controllers, services, models, or implementing TDD.
Homeostatic actuator auto-generating missing tests for requirements with low coverage. Creates unit tests, edge cases, and error cases for REQ-* without sufficient test coverage. Use when validate-test-coverage detects gaps.
Use when (1) verifying a feature is complete against acceptance criteria, (2) running QA checklist before release, (3) validating PR changes meet requirements. Performs systematic QA verification with documented results.
Test-Driven Development (TDD) using Vitest and TypeScript. Use when the user requests help with TDD, writing tests before code, test-first development, Vitest test setup, TypeScript testing patterns, unit testing, integration testing, or following the Red-Green-Refactor cycle with Vitest.
Use when implementing end-to-end tests, using Playwright or Cypress, testing user journeys, debugging flaky tests, or asking about "E2E testing", "Playwright", "Cypress", "browser testing", "visual regression", "test automation"
test-engineer skill Trigger terms: testing, unit tests, integration tests, E2E tests, test cases, test coverage, test automation, test plan, test design, TDD, test-first Use when: User requests involve test engineer tasks.