testing_skill

Overview

This skill provides a strict pre-commit testing and validation workflow for a Rust algorithmic trading bot. It enforces formatting, linting with zero warnings, comprehensive tests (including async safeguards), and optional release verification to catch regressions early. The goal is to ensure code quality, prevent hangs in async tests, and keep CI green before any commit.

How this skill works

Run the validation steps locally before committing: format the code, run clippy with warnings treated as errors, execute the full test suite, and optionally build in release mode. Async tests must include timeouts and avoid unbounded loops to prevent CI hangs. A short checklist and quick commands make the workflow easy to follow and repeatable.

When to use it

• Before every commit (mandatory)
• After implementing a new feature
• When validating a refactor or bug fix
• When tests or CI are failing intermittently
• Before preparing a release candidate

Best practices

• Run formatting and linting locally and fix all issues; no clippy warnings allowed
• Add or update tests to cover edge cases and behavior changes
• In async tests, always use timeouts for channel operations and avoid infinite loops
• Justify any lint allow attributes with clear comments; prefer fixing the cause
• Perform an optional release build to verify optimizations before publishing

Example use cases

• You added a new trading strategy—format, lint, and run tests before committing
• You refactored a concurrency module—validate async tests with timeouts to avoid hangs
• You fixed a bug uncovered by CI—run full validation locally to reproduce and confirm
• You prepared a release—run a release build to ensure the optimized binary compiles
• You wrote integration tests for exchange adapters—run targeted integration test commands