condition-based-waiting
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
Trouvez la capacité idéale pour votre agent.
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.
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.
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.
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.
Activates when generating unit tests, integration tests, or test cases for code
Next.js/TypeScriptプロジェクト向けGherkinシナリオ自動生成スキル。 以下の場合に使用: (1) ユーザーストーリーからBDDシナリオ作成時 (2) PRD/仕様書からテストシナリオ生成時 (3) APIエンドポイントの振る舞い定義時 (4) ページ遷移・UIインタラクションのシナリオ化時
Use this skill when working with SkylineTester or the test list file.
Testing patterns for Jest, Vitest, and Pytest. Covers test structure (AAA pattern), mocking strategies, fixtures, assertions, and testing best practices. Trigger: When writing tests, when setting up test frameworks, when implementing mocks, when creating test fixtures, when following TDD practices.
Comprehensive guide for debugging failing Playwright tests in this Cucumber project. Use this when tests are failing, elements are not found, or timeouts occur.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
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
Stabilize Playwright codegen recordings into reliable, maintainable automations. Use when a Playwright script recorded via codegen is flaky, fails when replayed, or requires frequent edits due to unstable locators, timing issues, popups/dialogs, multi-window flows, or dynamic DOM. Provides a repeatable workflow: convert recordings into intent-based locators, centralize selectors and tunables in config, add step contracts and diagnostics (trace/screenshot/HTML/a11y dumps), and use Playwright MCP (if available) to debug failures and validate fixes.
Run tests and systematically fix all failing tests using smart error grouping. Use when user asks to fix failing tests, mentions test failures, runs test suite and failures occur, or requests to make tests pass.
分析unit/integration/e2e测试分配比例,建议60/30/10比例平衡。当AICTXT/测试策略确定后使用,优化测试执行效率和覆盖质量。
Enterprise testing framework with pytest 8.4.x, Vitest 4.x, Playwright 1.48.x, Testing Library 15.x, httpx 0.28.x, k6 load testing, and accessibility testing
End-to-end truth-case orchestration for the Phoenix VC fund-modeling platform. Use when running tests/truth-cases/runner.test.ts, computing module-level pass rates, updating docs/phase0-validation-report.md and docs/failure-triage.md, or deciding between Phase 1A/1B/1C.
Create and maintain tests for the Raamattu Nyt monorepo using Vitest and React Testing Library. Use when: - Writing new tests for hooks, components, or utility functions - Analyzing recent git commits to identify code needing tests - Reviewing existing tests for correctness and coverage - Creating mocks for Supabase, auth, or other dependencies - Debugging test failures or flaky tests Triggers: "write tests", "test this", "add tests", "need tests for", "analyze test coverage", "fix failing tests", "mock this", "review tests"