テスト命名規則を設計し、可読性と一貫性を維持するスキル。 ファイル名、describe/it 構造、シナリオ表現を統一し、チーム運用を支援する。 Anchors: • xUnit Test Patterns / 適用: 命名規則設計 / 目的: 可読性の向上 • Specification by Example / 適用: シナリオ命名 / 目的: 意図の共有 Trigger: Use when defining, reviewing, or enforcing test naming conventions and file structures. test naming, describe/it, file structure
境界値分析と同値分割によるテストケース設計を体系化するスキル。 入力領域の分類、境界値抽出、エッジケース追加、組み合わせ最適化を行い、最小のテスト数で検証精度を高める。 Anchors: • The Pragmatic Programmer / 適用: テスト設計 / 目的: 実践的改善と品質維持 • Software Testing (Glenford J. Myers) / 適用: 境界値設計 / 目的: 代表値選定の明確化 • Rapid Software Testing (James Bach) / 適用: 探索的テスト / 目的: エッジケースの発見 Trigger: Use when designing test cases, validating input boundaries, applying equivalence partitioning, or optimizing test coverage.
Property-based testing for functor laws, monad laws, and naturality conditions using fp-ts and fast-check. Use when validating categorical implementations in TypeScript, testing algebraic laws in functional code, verifying functor/monad/applicative instances, or building test suites for categorical abstractions.
Generates property-based tests using Hypothesis (Python), fast-check (JavaScript/TypeScript), or QuickCheck (Haskell). Use when user asks to "generate property tests", "create hypothesis tests", "add property-based testing", or "generate fast-check tests".
ビジュアルリグレッションテストの専門スキル。 スクリーンショット比較、差分検出、UIテスト自動化を提供します。 Anchors: • 『Test-Driven Development: By Example』（Kent Beck） / 適用: UIテスト / 目的: 視覚的品質保証 Trigger: Use when implementing visual tests, configuring screenshot comparison, setting up UI regression testing, or integrating visual testing into CI/CD pipelines.
This skill should be used when the user asks to "write property tests", "add property tests", "create property-based tests", "use @bupkis/property-testing", or mentions "PropertyTestConfig", "fast-check generators", or "property testing for bupkis assertions". Provides guidance for writing property-based tests for bupkis plugin assertions using @bupkis/property-testing and fast-check.
テストファーストで仕様を定義し、Red-Green-Refactorを小さなステップで回すためのスキル。 設計の創発とレガシー対応まで含めて、テスト駆動開発の実務判断を支援する。 Anchors: • Test-Driven Development: By Example / 適用: TDDサイクル / 目的: 仕様の明確化 • xUnit Test Patterns / 適用: テスト設計 / 目的: 表現の一貫性 • Working Effectively with Legacy Code / 適用: レガシー適用 / 目的: 安全な変更 Trigger: Use when planning or executing test-driven development, defining test-first strategy, or reviewing red-green-refactor quality. TDD, test-first, red-green-refactor, small steps, refactoring
フレーキー（不安定）なテストを検出・修正するスキル。非決定性の排除、リトライロジック、テスト安定性向上パターンを提供。並列実行時の問題解決やタイミング依存の除去を支援。 Anchors: • Test-Driven Development（Kent Beck） / 適用: Red-Green-Refactor / 目的: 安定したテスト設計 • xUnit Test Patterns（Gerard Meszaros） / 適用: テストダブル / 目的: 非決定性の隔離 • Continuous Delivery（Jez Humble） / 適用: パイプライン信頼性 / 目的: CI/CDの安定化 Trigger: Use when tests fail intermittently, detecting flaky tests, eliminating non-determinism in tests, fixing timing-dependent failures, or stabilizing CI/CD pipelines.
統合テストの設計・実装・実行スキル。複数コンポーネント間の相互作用を検証し、エンドツーエンドのワークフローが正しく機能することを確認します。 Anchors: • Growing Object-Oriented Software, Guided by Tests (Freeman) / 適用: 境界テスト設計 / 目的: 契約ベースのテスト • Continuous Delivery (Humble) / 適用: パイプライン統合 / 目的: 早期フィードバック • Testing Microservices with Mountebank (Byars) / 適用: サービス仮想化 / 目的: 分散システムテスト効率化 Trigger: Use when testing component interactions, database integration, external API connections, or E2E workflows. integration testing, database testing, api testing, contract testing, test isolation
End-to-end testing patterns and best practices for web applications using Playwright and Cypress. Covers Page Object Model, test fixtures, selector strategies, async handling, visual regression testing, and flaky test prevention. Use when setting up E2E tests, debugging test failures, or improving test reliability. Trigger keywords: e2e testing, end-to-end tests, Playwright, Cypress, Page Object Model, test fixtures, selectors, data-testid, async tests, visual regression, flaky tests, browser testing.
Sets up visual regression testing using Percy, Chromatic, or Playwright to catch unintended UI changes through screenshot comparison. Use when user asks to "setup visual testing", "add screenshot tests", "prevent visual bugs", or "setup Percy/Chromatic".
Run and verify backend tests for the FastAPI/Python application.
Create or update Fake test doubles for TypeScript interfaces. Use when user asks to "create a fake", "update a fake", "generate test fake", "fix fake", "manage fake", or mentions needing a fake for testing. Generates Initializer interface, Fake class, and Builder class following the testing pattern with getMockingFunction, FakeEntity inheritance, and EventBroker support.
Playwright end-to-end (e2e) testing best practices for user-centric testing using semantic locators. Use when writing E2E tests, integration tests, user flow tests, Playwright tests, test specs, or when the user mentions Playwright, e2e tests, getByRole, test flows, or user testing.
统一使用 mockery + go:generate 为 Golang 接口生成 Mock，禁止手写 mock 结构体；在实现或编写单测时需要为接口创建 mock 时启用本 Skill。
Test-Driven Development (TDD) best practices for pko-tools repository. Use this skill when implementing new features, fixing bugs, or refactoring code in either the Rust backend (src-tauri/) or TypeScript/React frontend (src/). Specifically use when (1) adding new functionality that needs tests, (2) writing tests before implementation (red-green-refactor), (3) debugging failing tests, (4) improving test coverage, or (5) setting up test infrastructure.
Use when building anything non-trivial. Enforces a spec → plan → execute → verify loop that prevents "looks right" failures. Creates spec.md, todo.md, and decisions.md before writing code.
Write and run tests for the python-bsblan library. Use this skill when creating unit tests, working with fixtures, or ensuring code coverage requirements are met.
Create a test plan mapping EARS requirements and Critical Constraints to specific tests
テストカバレッジの計測、ギャップ分析、改善計画の策定を行うスキル。 リスクベースで優先順位を決め、実行可能な改善ステップに落とし込む。 Anchors: • Working Effectively with Legacy Code / 適用: リスク評価 / 目的: 重点領域の特定 • xUnit Test Patterns / 適用: テスト設計 / 目的: 有効なテスト追加 • Test-Driven Development: By Example / 適用: テスト追加 / 目的: 品質改善 Trigger: Use when analyzing test coverage, prioritizing coverage gaps, or planning coverage improvements. test coverage, coverage report, coverage gap, risk-based testing, improvement plan
