test-pyramid-advisor
分析unit/integration/e2e测试分配比例,建议60/30/10比例平衡。当AICTXT/测试策略确定后使用,优化测试执行效率和覆盖质量。
分析unit/integration/e2e测试分配比例,建议60/30/10比例平衡。当AICTXT/测试策略确定后使用,优化测试执行效率和覆盖质量。
Automatically generates comprehensive unit tests for Python, TypeScript, and JavaScript codebases. Analyzes function signatures, docstrings, and implementation patterns to produce tests covering happy paths, edge cases, error conditions, and boundary values. Supports pytest, Jest, and Vitest.
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.
Test FastAPI endpoints with pytest and generate API documentation. Use when creating new APIs or verifying existing endpoints work correctly.
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"
Use when pytest fixtures, conftest files, parametrize decorators, and fixture scopes for comprehensive test setup.
Use for bugs/test failures. Reproduce, isolate root cause, fix, and validate with evidence.
QA engineer and test automation specialist with deep expertise in Flutter testing. Use for designing test strategies, writing unit/widget/integration tests, improving test coverage, and ensuring code reliability.
QFAI: Implement acceptance tests from scenarios
TDD方法論に従ってテストを作成します。テストファイルの配置(コロケーション)、命名規則、テスト構造のベストプラクティスに従います。React/TypeScript、Go、Rustで適切なパターンを使い分けます。「テストを書いて」「テストを作成」「単体テストを追加」などのリクエストで起動します。
Guide E2E testing with Playwright for TapScore frontend. Use when writing or running frontend tests for user flows, navigation, forms, or mobile responsiveness. Ensures tests follow Page Object Model and proper async patterns.
Comprehensive web application testing automation using Playwright, including MCP integration, browser automation, E2E testing, visual regression testing, API testing, and CI/CD integration. Use when creating automated tests, setting up test frameworks, debugging test failures, implementing Page Object Model, or integrating testing into deployment pipelines.
Playwright MCPを使用して報告されたバグを再現し、再現テストケースを自動生成します。バグ修正の検証やリグレッションテストの作成に使用します。
Execute tests following TDD cycle: RED (verify test fails) → GREEN (implement to pass) → REFACTOR. Interprets tests.json and performs steps using available tools (browser MCP, API, CLI, etc.). WHEN TO USE: - Starting implementation of a ticket with TDD: yes - After writing test spec (3-spec.md) and tests.json - When user says "run tests", "test this", "TDD cycle" - After fixing a failing test REQUIRES: - Ticket with 3-spec.md - tests.json in .pmc/docs/tests/tickets/T0000N/
Use when writing or changing tests, adding mocks, or tempted to add test-only methods to production code - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies
Setup browser testing configuration. Use when setting up test credentials and organization info for E2E testing.
Write failing test first, then minimal code to pass. Red-Green-Refactor cycle. Use when: implementing features, fixing bugs, refactoring code. Triggers: "implement", "add feature", "fix bug", "tdd", "test first", "write tests", "test-driven".
Always use this skill when writing or editing software tests!