Crypto Orbit Learning Hub
How to Backtest a Crypto Trading Strategy
Learn why backtesting matters, sample size, entry/exit rules, stop-loss and target tracking, win rate, R:R, max drawdown, and overfitting risks.
Why backtesting matters
Backtesting checks how a strategy would have behaved on historical candles. It does not predict the future, but it helps reveal whether rules are clear, whether risk is measurable, and whether the idea fails too often under realistic conditions.
Without backtesting, a trader may remember only the best examples and ignore the bad ones. A written test forces every signal to be counted, including boring losses and missed trades.
Rules before results
A backtest needs exact entry rules, exit rules, stop-loss rules, target rules, and filters. If the rules change after seeing the result, the test becomes biased. Define the rules first, then run the test.
Examples of rules include: enter after a confirmation close, stop below the swing low, take partial profit at 1R, skip trades during high-impact news, or avoid sideways EMA conditions.
Sample size and metrics
A small sample can be misleading. Ten trades are not enough to trust a strategy. Traders should gather enough examples across different market conditions: trend, range, high volatility, low volatility, and news periods.
Useful metrics include win rate, average R, profit factor, max drawdown, losing streak, and number of trades. A strategy with 45 percent win rate can still work if winners are much larger than losers, but drawdown must be survivable.
Avoiding overfitting
Overfitting happens when rules are tuned too perfectly to past data. A strategy can look amazing on one period and fail later because the rules only matched that exact environment. Too many filters can also reduce trades until the result is not meaningful.
The safer approach is to use simple logic, test across multiple periods, and accept that no strategy works all the time. A robust strategy should have clear conditions for when not to trade.
Fees, slippage, and execution
Crypto backtests should include fees and realistic slippage. A scalping strategy can look profitable before costs and fail after costs. Thin pairs can have worse execution than major pairs like BTC or ETH.
Backtesting should also avoid future leak. A rule cannot use information from a candle before that candle closes. If the strategy requires confirmation close, the entry must happen after that close, not inside the same candle unless the rule explicitly allows it.
Practical example
Example scenario
A trader tests the 9-20 EMA pullback strategy on BTC 5m over 150 trades. They record entry, stop, target, fees, outcome in R, and whether the trade happened during news. After testing, they find the strategy performs better in clear trends and poorly during flat EMA periods.
Instead of forcing more trades, the trader adds a rule to avoid flat/crossing EMAs and then retests. The goal is not to make the past perfect, but to create rules that make sense before the next trade.
FAQ