testing-async
Use when testing async code with Swift Testing. Covers confirmation for callbacks, @MainActor tests, async/await patterns, timeout control, XCTest migration, parallel test execution.
Use when testing async code with Swift Testing. Covers confirmation for callbacks, @MainActor tests, async/await patterns, timeout control, XCTest migration, parallel test execution.
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
Plan and (when feasible) implement or execute user acceptance tests (UAT) / end-to-end acceptance scenarios. Converts requirements or user stories into acceptance criteria, test cases, test data, and a sign-off checklist; suggests automation (Playwright/Cypress for web, golden/snapshot tests for CLIs/APIs). Use when validating user-visible behavior for a release, or mapping requirements to acceptance coverage.
End-to-end testing with UUV (Useful User Verification)
Generate diagnostic koans to test reasoning boundaries and edge cases.
Run integration tests after workstreams complete to verify system-level behavior. Triggers after unit tests pass but before code review. Starts required services (via docker-compose), runs integration test suites, and verifies API contracts. Use when: - All workstreams in a plan complete - Unit tests pass - Before code review phase - User asks "run integration tests" If no integration tests exist: Warn but proceed (don't block).
Comprehensive testing guidance for RSSVibe project using TUnit framework, test organization, and HTTP client patterns. Use this skill when writing tests, running tests, or reviewing testing practices.
pytest, data validation, Great Expectations, and quality assurance for data systems
Ejecuta 🔄 FASE 1 del Ciclo de Validación Automática - Renderizado completo exams2*.
Testa aplicacoes web usando Playwright. Captura screenshots, executa E2E tests, analisa logs do browser. Integrado com qa-analyst para Phase 6. Use quando: testar frontend, capturar screenshots, validar UI, executar E2E.
Vitest testing framework expert for Vite integration, Jest migration, browser mode testing, and performance optimization
Generates modern maintainable Laravel applications unit and feature (integration) tests with a focus on performance by default and for best testing style practices.
Use to validate reported issues. Confirms reproducibility and documents validation evidence.
sdd-initで作成したSpecドラフトを入力として、TDDを回せるだけのテスト観点(ハッピー/代表的失敗/境界/不変条件/非機能)をSpecに網羅する。ここではテスト実装・プロダクション実装は行わない。スコープ変更・要件追加もしない(必要なら未決事項として質問を起票し、合意が取れるまでTDDへ進ませない)。出力は「Specの更新(テスト戦略・テストケース一覧・カバレッジチェック)」「ブロッカー/未決事項」「tdd-redに渡す“次に書くべきテスト1つ”候補」に限定する。
Deploy resonant probes to test system response patterns.
TDDのリファクタ(REFACTOR)フェーズを厳密に実行する。全テストGREENを維持したまま、重複排除・命名改善・関心分離など内部構造を改善する。仕様変更が必要なら先にSpecとテスト期待値を更新してから実装を調整する。
Use this to run the Rust suite quickly with `cargo nextest`, starting targeted and widening to full CI parity.
Focused workflow for TUI E2E testing with Termwright. Use for fast agent guidance when running step files, capturing artifacts, and debugging with trace output.
Write technical tickets with structured acceptance criteria and state transitions. Use when user asks to create a ticket, write a task, document a feature, or plan implementation work. Follows [service-name] title convention with detailed acceptance criteria.
Ensures comprehensive test coverage following Rails testing best practices
フロントエンド(TypeScript/Svelte 5/Vitest)のテスト実装とデバッグを行います。テストの作成、テストの実行、テストエラーの修正、Svelte 5 コンポーネントのテスト、国際化対応のモックなどのテスト関連タスクに使用します。
Generate comprehensive unit and integration tests for JavaScript/TypeScript code