test▌

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

Comprehensive testing specialist for functional, performance, and security test design and execution. \n \n Covers unit, integration, E2E, performance (k6, Artillery), and security testing (OWASP) with structured workflows from scope definition through reporting \n Enforces test quality standards: meaningful assertions, isolated dependencies, edge-case coverage, and flaky-test remediation \n Provides reference guides for TDD methodology, testing anti-patterns, automation frameworks, and QA pract

Comprehensive guide for writing and running Terraform tests with assertions, mocking, and module validation. \n \n Write test files using .tftest.hcl syntax with run blocks that execute in plan or apply mode, supporting sequential and parallel execution with optional state isolation \n Assert conditions on resource attributes, outputs, and data sources; use expect_failures to validate that invalid inputs are properly rejected \n Mock providers (Terraform 1.7.0+) simulate infrastructure behavior

ln-520-test-planner

Category: test

Multi-agent pipeline that generates compilable, passing unit tests across eight programming languages. \n \n Orchestrates a Research → Plan → Implement workflow: researcher analyzes the codebase, planner creates phased test strategy, implementer writes and validates tests across phases \n Supports C#, TypeScript, JavaScript, Python, Go, Rust, Java, and more; auto-detects language, testing framework, build commands, and project structure \n Includes builder, tester, fixer, and linter subagents th