test-ids
WHAT: Test ID constants with hierarchical naming for React Native automated testing. WHEN: unit tests with Testing Library, E2E tests with Maestro, testing interactive elements. KEYWORDS: testID, TEST_IDS, cons...
Découvrez les skills tools testing, comparez leurs dépôts et consultez leurs instructions.
WHAT: Test ID constants with hierarchical naming for React Native automated testing. WHEN: unit tests with Testing Library, E2E tests with Maestro, testing interactive elements. KEYWORDS: testID, TEST_IDS, cons...
WHAT: Constants organization with naming conventions and type-safe as const assertions. WHEN: defining test IDs, animation durations, query keys, feature flags. KEYWORDS: constants, SCREAMING_SNAKE_CASE, Pascal...
Runs unit and E2E tests for API, analyzes failures, identifies flaky tests, checks coverage, and suggests fixes
Web application testing principles. E2E, Playwright, deep audit strategies.
Run appropriate tests based on changes using node:test, Testcontainers, and Playwright
Work on a kspec task with proper lifecycle - verify, start, note, submit, PR, complete.
E2E multiplayer testing using Playwright API with multi-client browser contexts. Validates server-authoritative patterns, state synchronization, and anti-cheat measures. Use when testing multiplayer features.
Generate unit tests using Jest with mocking, AAA pattern (Arrange-Act-Assert), and 80%+ coverage target. Use when testing business logic, handlers, or services in isolation.
WHAT: Test ID patterns with data-testid attribute for web testing. WHEN: E2E with Playwright/Cypress, component tests with Testing Library, targeting specific elements. KEYWORDS: data-testid, test ID, getByTest...
Generate integration tests for CQRS handlers with mocked dependencies and co-located fixtures using Jest. Use when testing handlers, database operations, or event publishing in isolation.
WHAT: Jest and @testing-library/react patterns for web component testing. WHEN: testing components with providers, user interactions, async content, form validation. KEYWORDS: testing-library, Jest, screen, use...
E2E test creation and execution for QA. Validates implementations using Playwright API tests that become persistent artifacts for regression.
Guidelines for running and writing unit and E2E tests. Use this when asked to run tests, write tests, debug test failures, or verify code changes. Also use this before performing any merge commands or pushing c...
Guides test creation for Polibase following strict testing standards. Activates when writing tests or creating test files. Enforces external service mocking (no real API calls), async/await patterns, test indep...
CLI testing guidance and patterns. Loaded by /ops/test/cli command or subagents for comprehensive Navigator CLI testing.
Validate integration impact and regression risks via claude-delegator (Code Reviewer expert). Use for complex tasks or API integration.
Run project tests using the X07 test harness (x07 test), producing a machine-readable JSON report.
Run targeted tests using src.agents.scripts.test after code changes. Use when you need to execute only affected tests, pass a custom pytest command, or collect JSON test summaries with sub-agent fixes.
Run end-to-end tests using Playwright MCP. Requires a test plan document. Use: /e2e-test [--prod] [--continue]. Stops on first failure by default. Keywords: e2e, test, playwright, qa, end-to-end.
Expert in authoring Gherkin-compliant behavior specifications (Given, When, Then). Use when defining executable scenarios for feature specifications or acceptance tests.
Park Golf Platform 계약 테스트 가이드. Pact를 사용한 Consumer-Driven Contract Testing, OpenAPI 스펙 검증, NATS 메시지 스키마 검증 방법 안내. "계약테스트", "contract", "pact", "스키마 검증" 관련 질문 시 사용합니...
Park Golf Platform 통합 테스트 가이드. API 테스트, 서비스 간 통신 테스트, E2E 테스트 실행 방법 안내. "통합테스트", "integration", "API 테스트", "서비스 테스트" 관련 질문 시 사용합니다.
Generator สำหรับสร้าง Bruno API test collections อัตโนมัติจาก OpenAPI specs หรือ endpoint definitions
Gates สำหรับ enforce API contract testing ระหว่าง services ด้วย Pact หรือ OpenAPI validation
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é.