testing▌

Comprehensive testing patterns for Spring Boot applications covering unit, slice, integration, and container-based tests. \n \n Covers four test types with performance targets: unit tests (< 50ms), slice tests (< 100ms), integration tests (< 500ms), and full context tests with Testcontainers \n Includes patterns for Mockito-based unit testing, JPA/MVC slice testing with focused Spring contexts, and REST API testing with MockMvc and WebTestClient \n Demonstrates Spring Boot 3.5+ @S

Generate complete VectorBT backtesting scripts with data fetch, signals, stats, and plots. \n \n Supports 10+ pre-built strategies (EMA crossover, RSI, Donchian, Supertrend, MACD, SDA2, momentum, and more) with template-based script generation \n Fetches data from OpenAlgo API or loads directly from DuckDB; auto-detects Historify vs custom formats \n Uses TA-Lib for standard indicators and OpenAlgo ta for specialty indicators (Supertrend, Donchian, Ichimoku); includes signal deduplication via ex

Run tests for React codebase across multiple release channels and configurations. \n \n Supports six release channels: source (default), experimental, www, www with variant false, stable, and classic, each with distinct feature flag configurations \n Accepts test patterns, watch mode for TDD, and variant flags to test different code paths \n Requires explicit test pattern argument to avoid running the entire test suite; uses --silent flag to surface failures and --no-watchman for sandboxing comp

Execute and diagnose Go acceptance tests for Terraform providers with structured troubleshooting. \n \n Run focused acceptance tests using go test -run=TestAccFeatureHappyPath with TF_ACC=1 environment variable \n Diagnose failures progressively: retry with -count=1 , enable verbose output with -v , activate debug logging via TF_LOG=debug , and persist Terraform workspace with TF_ACC_WORKING_DIR_PERSIST=1 \n Validate test reliability by intentionally breaking a TestCheckFunc, re-running the test

Creates a GitHub issue in microsoft/github-copilot-for-azure for integration test failures.

Comprehensive guidance for unit, widget, and integration testing across Flutter applications. \n \n Covers three test types with trade-off analysis: unit tests for isolated logic (fast, low maintenance), widget tests for UI components (higher confidence, more dependencies), and integration tests for end-to-end flows (highest confidence, slowest execution) \n Includes practical examples for all three test categories, from basic Counter tests to complex user flows and performance profiling \n Prov

Analyze a single target project to identify data access artifacts that require integration testing, then produce a structured, actionable testing plan.

Guide for extending Playwright with new APIs, MCP tools, CLI commands, and vendored dependencies. \n \n Covers monorepo structure, build/test/lint workflows, and coding conventions via CLAUDE.md reference \n Includes detailed walkthroughs for implementing client/server APIs, writing tests, and modifying protocol layers \n Explains how to add MCP tools, CLI commands, and configuration options within the Playwright ecosystem \n Documents the vendoring process for bundling third-party npm packages

Write, review, and improve Swift Testing code with modern APIs and best practices. \n \n Validates test structure, assertions, dependency injection, async patterns, and actor isolation against Swift Testing conventions \n Guides migration from XCTest to Swift Testing, including assertion mappings and modern concurrency patterns \n Covers new features like raw identifiers, test scopes, exit tests, attachments, and range-based confirmations \n Targets Swift 6.2+ with emphasis on modern Swift concu

Orchestrate TestFlight distribution, tester groups, and release notes via the App Store Connect CLI. \n \n Manage testers and groups with list, create, add, and invite commands; supports pagination for large datasets \n Distribute builds to groups and remove them with confirmation; export and import full TestFlight configuration as YAML \n Create and update \"What to Test\" notes per build and locale for release communication \n Use IDs for deterministic operations; integrates with the ID resolv