test-runner
Run Vitest tests for the Babylon.js game project. Use when the user wants to run tests, check test coverage, debug failing tests, or validate code functionality.
Run Vitest tests for the Babylon.js game project. Use when the user wants to run tests, check test coverage, debug failing tests, or validate code functionality.
PHP 8.4+ best practices with PHPUnit 11, Composer, PSR-12 standards,
E2E and browser testing for RawDrive using Playwright MCP. Use for testing UI flows, verifying frontend functionality, debugging visual issues, and capturing screenshots.
Auto-Claude spec creation and management. Use when creating feature specs, understanding spec pipeline phases, modifying requirements, or managing spec lifecycle.
Strict test-driven development state machine with red-green-refactor cycles. Enforces test-first development, meaningful failures, minimum implementations, and full verification. Activates when user requests: 'use a TDD approach', 'start TDD', 'test-drive this'.
This skill should be used when the user asks about "Go test conventions", "ADR-008", "test naming", "table-driven tests", "go testing patterns", "testify", "how to write go tests", or needs guidance on Go testing methodology. Provides comprehensive guidance on high-quality Go testing following established conventions.
Build comprehensive test suites for FastAPI applications using pytest and pytest-asyncio. This skill should be used when users want to write unit tests, integration tests, or end-to-end tests for FastAPI endpoints, async functions, database operations, and business logic. Covers test organization, fixtures, mocking, async testing, and CI/CD integration. Always fetches latest pytest and pytest-asyncio documentation before implementation.
ページ分析からE2Eテストを自動生成。UI要素検出、ユーザーフロー特定、カバレッジ向上。既存ページのテスト追加やカバレッジ拡大に使用
Generate comprehensive unit, integration, and E2E tests with edge cases, mocks, and assertions. Use when writing tests for functions, classes, APIs, or implementing TDD.
Write comprehensive tests (unit, integration, e2e), manage test coverage, and ensure code quality. Use when writing tests, improving coverage, or debugging test failures.
Integrate Excel (.xlsx) data into Playwright codegen scripts by replacing hardcoded values with config-driven lookups, loading data with polars, and validating every step with Playwright MCP (start MCP from the repo if not running). Use for Playwright automation updates that require Excel-backed data, config.yaml centralization, or MCP validation/reporting.
Python testing with pytest framework for unit, integration, and API tests. Use when: (1) Writing test cases for Python code, (2) Setting up pytest fixtures, (3) Testing async functions with pytest-asyncio, (4) Mocking dependencies, (5) Parameterizing tests, (6) Testing FastAPI/Flask endpoints, (7) Setting up test coverage, (8) Creating test factories with factory_boy, (9) Configuring CI/CD test pipelines.
Run tests and analyze failures with actionable fixes. Use when user wants to run tests or debug test failures.
Use TDD workflow (Red-Green-Refactor-Validate) when creating or modifying any business logic, use cases, or domain code. MANDATORY for all implementations. Apply when user requests new features, bug fixes, or refactoring that involves testable code.
Your approach to handling testing sphinx test. Use this skill when working on files where testing sphinx test comes into play.
Use when working with unit tests in any capacity - reading, writing, updating, planning, evaluating, or reviewing tests - applies TDD principles with focused test coverage, filtering out redundant tests while ensuring critical paths, edge cases, and state changes are verified
Tests pure functions, utilities, and logic with Vitest. Input: Function/module to test. Output: Test file with unit tests for all cases.
Comprehensive testing guide for Yoto Smart Stream - covering authentication testing, functional testing, Playwright UI automation, and test-and-fix development loops. Use when writing tests, debugging test failures, or implementing test coverage.
End-to-end frontend testing with Playwright Java and Chromium. Use for UI validation, form testing, API interaction verification, and screenshot capture on failures.
Apply pytest best practices and project testing conventions. Use when writing or modifying tests.
Playwright E2E testing for customer frontend Use when: Writing E2E tests for Angular customer frontend, testing authentication flows, testing game listings, testing profile/KYC workflows
Write and run unit tests for discord_api following best practices. Use when the user asks to write tests, add test coverage, or run tests for API code.