See whether the system opened, held, closed, skipped, or flipped and inspect the reasoning behind that state.
Test Mode
Test Bots and Dry Run Mode
Test mode should be the default starting point for new configurations. It uses the decision engine without placing live trades so users can inspect behavior before capital is exposed.
What test mode does
Test mode runs the real decision path with `dry_run=true`. That means the bot evaluates assets, applies rules, chooses actions, and records reasoning without sending live execution requests.
Decision engineLogs and reasonsHypothetical actionsNo live execution
What users can learn from test mode
Understand when risk constraints blocked a new entry or changed what the bot was allowed to do.
Validate allocations, leverage assumptions, and exit posture before enabling live execution.
What test mode does not guarantee
Test mode is for execution-safe validation, not for promising exact live outcomes. It does not replicate live fills, exact slippage, execution timing, or every market microstructure effect.
Recommended validation workflow
- Run the bot in test mode.
- Inspect several cycles of decisions and reasons.
- Check whether skips, holds, and closes align with your expectations.
- Adjust configuration if the behavior is not acceptable.
- Only move toward live mode after a deliberate review.
Promotion to live mode
The correct product model is a review checkpoint, not a hidden toggle. Users should confirm capital, risk posture, and monitoring expectations before promoting a test configuration into live operation.
Honest framing matters
Test mode should be described as safe validation of decision logic. It should never be marketed as a perfect forecast of live performance.
Related Pages
Safe validation
Use test mode before moving capital
The product should encourage inspection, review, and adjustment before any live execution pathway is enabled.