Unit Testing

测试指南 - 测试设计和实现的原则与最佳实践。包含测试设计模板和断言最佳实践。

Run a comprehensive code quality review. Checks security, performance, maintainability, project conventions (CLAUDE.md), architecture, and testing. Runs rustfmt and bazel test. Use /quality to check code quality or validate before committing.

Reads MetaTrader 5 log files to validate indicator execution, unit tests, and compilation errors. Use when user mentions Experts pane, MT5 logs, errors, or asks "did it work".

Use cargo nextest instead of cargo test for running Rust tests. This skill should be invoked whenever running tests in a Rust project. Cargo nextest provides superior test output, filtering with expression language, wrapper script integration, retries, and profiling capabilities. Always use `cargo nextest run` instead of `cargo test`.

This skill should be used when teams need to adopt Supertester to build deterministic Elixir OTP tests with isolation, synchronization, and supervision coverage.

Dynamic skill discovery and matching for any task context.Invoke when:- Starting any task to discover relevant skills- Need to find specialized skills for current context- Agent/command needs skill recommendationsTrigger phrases: "match skills", "find skills", "what skills for","recommend skills", "which capabilities", "skill lookup", "applicable skills"Examples:- "Match skills for TDD cycle with zod validation" → outputs backend-zod, backend-vitest- "What skills for React landing page?" → outputs frontend-master, frontend-aceternity

Testing patterns and standards for this codebase, including async effects, fakes vs mocks, and property-based testing.

Step-by-step guide for creating new widgets in the Hex1b TUI library. Use when implementing new widgets from scratch, including widget records, nodes, extension methods, theming, reconciliation, and tests.

Use vitest + jsdom for fast, lightweight unit tests for front-end apps

Pragmatic Rust conventions to keep code readable, testable, and performant for this project.

Generates detailed Given/When/Then acceptance criteria when user describes feature behavior or requirements. Enhances user stories with testable scenarios.

Log experiment metrics, parameters, and artifacts using MLflow Python API. Query and analyze runs with DataFrame operations. Use when user mentions "log backtest", "MLflow metrics", "experiment tracking", "log parameters", "search runs", "MLflow query", or needs to record strategy performance.

Multi-language static application security testing using Horusec with support for 18+ programming languages and 20+ security analysis tools. Performs SAST scans, secret detection in git history, and provides vulnerability findings with severity classification. Use when: (1) Analyzing code for security vulnerabilities across multiple languages simultaneously, (2) Detecting exposed secrets and credentials in git history, (3) Integrating SAST into CI/CD pipelines for secure SDLC, (4) Performing comprehensive security analysis during development, (5) Managing false positives and prioritizing security findings.

[YOUR_DESCRIPTION] - Be specific about what the skill does, when to use it, and include trigger keywords. Example: "Deploy applications to production with automated testing, health checks, and rollback capabilities. Use when deploying, shipping to production, or when users mention deployment, release, or going live."

Write comprehensive tests with emphasis on ALL error paths, edge cases, and regression coverage for code changes

Write comprehensive Storybook stories for React components with proper TypeScript types, args, controls, decorators, and interaction tests. Use this skill when the user asks to create or improve Storybook stories for components in the /components workspace.

Автоматизация тестирования и проверки качества кода

Create or update test files for React hooks. Use when user asks to "create hook tests", "test useMyHook", "generate tests for hook", "update hook tests", or mentions needing tests for a React hook. Generates vitest test files with renderHook, Fake context providers, and proper test structure.

Create or update test files for React components. Use when user asks to "create component tests", "test MyComponent", "generate tests for component", "update component tests", or mentions needing tests for a React component. Generates vitest test files with render, mocked sub-components, and proper test structure focusing on logic and prop validation.

Bun runtime patterns including native APIs, SQLite, testing, HTTP server, WebSocket, file handling, and shell operations. Use when working with Bun runtime, bun:sqlite, Bun.serve, bun:test, or when Bun, --bun flag, SQLite, or Bun-specific patterns mentioned.