testing▌

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

Vitest testing guide for LobeHub with commands, patterns, and best practices. \n \n Run specific test files with bunx vitest run commands; avoid bun run test which runs 3000+ tests (~10 minutes) \n Prefer vi.spyOn over vi.mock for targeted, maintainable mocks; use vi.stubGlobal for browser APIs \n Test observable behavior rather than implementation details; delete param-forwarding tests that duplicate higher-level coverage \n Includes detailed guides for database models, Electron IPC, Zustand st

Modern Swift testing framework with @Test macros, parameterized tests, traits, and async support. \n \n Write unit tests using @Test macros with #expect and #require assertions; prefer Swift Testing over XCTest for all new tests (Xcode 16+, Swift 6+) \n Organize tests with @Suite for grouping, custom tags for filtering, and traits for conditional execution, time limits, and known issues \n Support parameterized tests via arguments: with enum cases, ranges, or cartesian products; use confirmation

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

Identify and exploit authentication and session management vulnerabilities in web applications. Broken authentication consistently ranks in the OWASP Top 10 and can lead to account takeover, identity theft, and unauthorized access to sensitive systems. This skill covers testing methodologies for password policies, session handling, multi-factor authentication, and credential management.

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

Generates integration test cases for data access artifacts in a single target project. Tests validate behavior consistency when running against Oracle or PostgreSQL.

Fast, scalable Python testing with fixtures, parametrization, and framework integration. \n \n Fixture system provides dependency injection and setup/teardown with function, class, module, and session scopes \n Parametrization enables data-driven tests; markers organize tests by category (unit, integration, slow, custom) \n Built-in support for FastAPI, Django, and Flask with async/await testing via pytest-asyncio \n Rich assertion introspection, mocking via pytest-mock, coverage reporting, and

Comprehensive Kotlin testing patterns for writing reliable, maintainable tests following TDD methodology with Kotest and MockK.

Testing patterns specifically designed for AI-assisted development, where the same model writes code and reviews it — creating systematic blind spots that only automated tests can catch.