test▌

JUnit 5 patterns for testing utility classes, static methods, and pure functions without mocking complexity. \n \n Covers testing strategies for string manipulation, calculations, collections, data validation, and format utilities with edge case and boundary condition handling \n Uses AssertJ assertions for readable test code and @ParameterizedTest for testing multiple similar scenarios efficiently \n Emphasizes null handling, empty inputs, extreme values, and floating-point precision as critica

Structured framework for designing statistically rigorous A/B tests with mandatory validation gates. \n \n Enforces hypothesis lock, metric freezing, and sample size calculation before any implementation begins \n Includes hard gates at three critical points: hypothesis validation, assumptions review, and execution readiness \n Defines primary, secondary, and guardrail metrics to prevent harmful wins and ensure valid interpretation \n Covers test type selection, duration estimation, and strict r

Unit test external REST API integrations with WireMock HTTP mocking and request verification. \n \n Stub HTTP responses with configurable status codes, headers, and JSON bodies; verify request details including headers, query parameters, and request bodies \n Test error scenarios (4xx/5xx responses, timeouts, malformed responses) without calling real APIs or hitting rate limits \n Use dynamic port allocation to avoid conflicts in parallel test execution; automatic cleanup between tests via JUnit

Isolated unit testing patterns for Spring service layer using Mockito and JUnit 5. \n \n Covers mocking injected dependencies, verifying service interactions, and testing business logic without database or external API calls \n Includes patterns for exception handling, complex workflows, argument capturing, and verification of call order and frequency \n Supports testing async/reactive services with CompletableFuture and provides best practices for constructor injection and spy-based partial moc

You are an expert in App Store product page optimization and A/B testing. Your goal is to help the user design, run, and interpret tests that improve their App Store conversion rate.

Downloads artifacts from a GitHub Actions integration test run, generates a summarized skill invocation report, and files GitHub issues for each test failure with root-cause analysis.

Store and manage API response test fixtures for provider parsing validation. \n \n Fixtures are organized in __fixtures__ subfolders within provider packages, using naming conventions documented in existing examples \n Supports two testing patterns: generateText (log raw response to console and copy into fixture) and streamText (use includeRawChunks and saveRawChunks helper to capture streaming chunks) \n Recommends storing true provider responses unless size constraints require semantic-preserv

Use this skill to create or review unit tests for Vue components, composables, and Pinia stores. Keep tests small, deterministic, and behavior-first.

Comprehensive test case generation from PRD documents and user requirements with full coverage mapping. \n \n Transforms product requirements into structured, executable test cases organized by category: functional, edge case, error handling, and state transition scenarios \n Generates requirement-driven test cases with unique IDs, priority levels, preconditions, step-by-step actions, and measurable expected results \n Includes traceability matrix linking each requirement to corresponding test c

Visual snapshot testing for web renderer components using vitest fixtures. \n \n Create test fixtures in packages/web-renderer/src/test/fixtures that define a React component, dimensions, frame rate, and duration \n Register fixtures in packages/web-renderer/src/test/Root.tsx to enable preview functionality \n Write test cases that render stills using renderStillOnWeb() and validate output with testImage() snapshot comparison \n Run tests with bunx vitest src/test/video.test.tsx and update docum