1 comment

Slippage in automated execution typically happens when market orders or stop orders fill at a worse price than expected due to latency, thin liquidity, or high volatility during news events. When testing trading bots and automation, accounting for realistic slippage and transaction costs is essential to avoid curve-fitted results that look great on paper but fail live.
For prop firm traders, unexpected slippage can cause significant issues, especially when dealing with tight daily loss limits or news trading restrictions. A bad fill during high-impact data releases can easily breach a strict drawdown limit before your risk management code has time to react.
How do you factor slippage into your backtests? Feel free to share your approach below!