trading bot failure simulator

The problem

Trading bots often perform perfectly in backtests but fail catastrophically during live deployment due to network instability or exchange API quirks. Identifying every edge case like partial fills, race conditions, and stale data before risking real capital is manually intensive and prone to oversight.

What it does

• Generates detailed failure scenario cards for API outages, including 5xx errors and rate limits.
• Simulates order lifecycle edge cases such as duplicate orders on timeout and partial fills followed by disconnects.
• Designs stress tests for market anomalies like flash crashes, price gaps, and extreme spread volatility.
• Provides concrete injection methods and validation metrics for each failure mode.
• Structures scenarios with expected resilient behaviors to guide your error handling implementation.

Frameworks & tools

Agnostic to specific bot frameworks. Applicable to systems interacting with REST and WebSocket APIs like Binance, Coinbase, or Kraken. Works best with mock exchanges, API proxies, and testnet environments.

Why this beats prompting it yourself

Writing individual test cases for complex race conditions is tedious and misses subtle failure modes. This skill uses a specialized taxonomy of trading-specific failures to ensure you cover high-risk scenarios like runaway retries and clock skew that are often overlooked by general QA prompts.

Use cases

• Design a test suite for a new exchange integration to verify idempotency and retry logic.
• Simulate network partitions to ensure your bot reconciles state correctly after a WebSocket drop.
• Stress test risk management modules against sudden volatility and exchange circuit breakers.
• Audit circuit breaker logic to prevent runaway order submissions during API degradation.

Known limitations

Scenarios require manual implementation in your test environment. Never use these simulations on live accounts with real funds.