test▌

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.

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

Write failing tests first, then minimal code to pass, then refactor while keeping tests green. \n \n Follows the red-green-refactor cycle: write one failing test, verify it fails correctly, implement minimal code to pass, verify all tests pass, then refactor safely \n Requires watching each test fail before writing implementation code; tests that pass immediately prove nothing about correctness \n Applies to all new features, bug fixes, refactoring, and behavior changes; code written before test

Verification skill demonstrating the skill system's basic functionality and loading mechanism. \n \n Executes when /day1-test-skill is invoked, confirming the skill system is operational \n Outputs a success message and explanation of how skills are loaded on-demand into context \n Designed as an onboarding exercise to help users understand Progressive Disclosure and skill mechanics \n

Category: test

Systematic JUnit 5 patterns for testing numeric limits, null/empty cases, and edge conditions. \n \n Covers numeric boundaries (Integer.MIN_VALUE, MAX_VALUE, zero), string edge cases (null, empty, whitespace), and collection sizes (empty, single, many) \n Includes parameterized test examples using @ParameterizedTest and @ValueSource for efficient multi-case coverage \n Demonstrates floating-point precision testing with tolerance-based assertions, overflow/underflow detection, and special values

Writes failing tests first, establishing a strict implementation contract for test-driven development. \n \n Completes the RED phase of TDD by authoring behavior-focused tests that fail for the right reason, then hands off to implementation agents with objective pass criteria \n Delegates test authoring to a tdd_test_writer subagent when available, ensuring tests remain unmodified during implementation \n Detects existing test frameworks and conventions (pytest, jest, vitest, go test, cargo test