Tick vs OHLC Backtesting

What Is Tick Backtesting?

Tick backtesting uses every individual price change recorded by the broker. It simulates the market with maximum precision, including spread, slippage, micro‑movements and intra‑candle volatility.

• • Models every tick of price movement
• • Accurate spread and slippage simulation
• • Realistic stop‑loss and take‑profit triggering
• • Essential for scalping and high‑frequency systems

What Is OHLC Backtesting?

OHLC backtesting uses only four values per candle: Open, High, Low and Close. It is significantly faster but less precise, especially for strategies sensitive to intra‑candle movement.

• • Uses candle‑level data only
• • No tick‑level volatility
• • Faster but less accurate
• • Suitable for higher‑timeframe systems

Key Differences Between Tick and OHLC

Execution Accuracy

Tick data models real execution conditions, while OHLC assumes idealized fills.

Stop‑Loss & Take‑Profit Behavior

Tick backtesting triggers stops based on real price flow. OHLC may trigger stops in the wrong order or miss them entirely.

Spread & Slippage

Tick data includes spread changes and slippage. OHLC assumes constant spread and zero slippage.

Scalping & Intraday Strategies

Scalping requires tick data. OHLC is insufficient for micro‑timing strategies.

When to Use Tick Backtesting

• • Scalping systems
• • Breakout strategies
• • High‑frequency entries
• • Tight stop‑loss logic
• • Execution‑sensitive EAs

When OHLC Backtesting Is Enough

• • Higher‑timeframe strategies (H1–D1)
• • Trend‑following systems
• • Mean‑reversion with wide stops
• • Early‑stage prototyping
• • Parameter exploration before tick validation

Hybrid Workflow: Best of Both Worlds

The most efficient approach combines both methods:

• • Use OHLC for fast parameter exploration
• • Validate finalists using tick data
• • Perform walk‑forward and Monte Carlo on tick‑validated sets
• • Deploy only strategies that pass tick‑level robustness checks

Implementation in Quantisca

Quantisca’s Backtesting & Optimization Suite uses a hybrid model:

• • OHLC for rapid prototyping
• • Tick‑level validation for final models
• • Realistic execution simulation
• • Spread, slippage and latency modeling
• • Multi‑asset tick‑based robustness testing

Conclusion

Tick vs OHLC backtesting is not a matter of “better or worse”, but “fast vs accurate”. OHLC accelerates development, while tick data ensures real‑world reliability. A professional workflow uses both — fast exploration followed by precise validation.