TDD Red Phase expert. Activate when: - Starting new feature development with TDD - User mentions "write test first", "failing test", "red phase" - Need to design test cases before implementation - Questions about test structure, assertions, test naming Auto-triggers on: test design, test-first development, TDD start
Standards and best practices for writing effective tests including the testing pyramid, test structure patterns, and coverage guidelines
Reviews UI test scenarios for wording accuracy. Detects variables and dynamic values that cannot be verified from actual UI. Use as part of parallel UI test scenario review.
Identifies redundant or duplicate test cases, removes them while ensuring test coverage is not reduced.
Write Playwright tests, migrate from Cypress, and answer Playwright questions. Use when working with e2e tests, browser automation, Playwright, or migrating from Cypress.
This skill should be used when user asks "/playwright-test", "/test", "test automation", "Playwright test", "E2E test", "web test", "multi-agent test", "functional/visual/API/performance test", "테스트 자동화", "웹 테스트", "기능 테스트", "성능 테스트", or wants to run comprehensive web application testing.
Web application testing principles. E2E, Playwright, deep audit strategies.
Implements testing strategies for React Native components, MST stores, and services using Jest, React Testing Library, and Maestro. Use when writing unit, integration, or E2E tests in Purrsuit Mobile App.
Demonstrates unsafe patterns for testing audits. Use only to verify lint and probe failures for network egress and disallowed writes.
Generates initial view components with mandatory unit tests. Creates HomeView.vue, PageNotFoundView.vue, and their .spec.ts test files (4 files total).
Enforce tight coupling between components, tests, and stories with exact naming conventions. Use when creating new components, writing tests, or ensuring test/story files exist for all user-facing components.
Generate Vitest test files for the dealflow-network project with proper setup, teardown, database patterns, and assertion styles. Use when creating tests for new features, database operations, or API endpoints.
Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use when user wants to test websites, automate browser interactions, validate web functionality, or perform any browser-based testing.
Testing FastAPI applications with pytest using Test-Driven Development (TDD). Use when writing tests for FastAPI endpoints, setting up test fixtures, testing async routes, mocking dependencies, database testing with rollback isolation, or running test coverage. Triggers on requests like "write tests for my API", "add unit tests", "test this endpoint", "set up pytest", "check test coverage", "use TDD", "write tests first", or "red-green-refactor".
生成したプラグイン全体の整合性・完全性を検証する。プラグイン検証時、品質チェック時、またはユーザーがプラグイン検証、整合性確認、完全性チェック、品質保証、バリデーションに言及した際に使用する。
Python testing best practices with pytest, unittest, and mocking
Testing patterns and conventions. Use when writing tests, reviewing test coverage, or organizing test infrastructure. Triggers: _test.go, TestXxx, t.Run, table-driven tests, black-box testing, package name_test, test coverage, t.Fatal, t.Error, t.Errorf. File patterns: tests/**/*.go, *_test.go
