MT5 Every Tick vs. Real Ticks: What the Tester Models
Quick Answer
MT5 Strategy Tester offers different ways to model price movement between bars. “Every tick based on real ticks” uses available historical tick data for the test period, while generated tick modes construct ticks from available bar data. Less detailed modes can be useful for screening some strategies, but results may differ for systems sensitive to intrabar order, stops, spreads, or tick-by-tick conditions. No tester mode guarantees live fills.
Key Facts
| Test mode | General use | Main caution | |---|---|---| | Every tick based on real ticks | Detailed test when suitable tick history exists | History coverage and broker feed still matter | | Every tick | Generated intrabar ticks for detailed logic testing | Generated path is not the actual historical tick sequence | | 1 minute OHLC | Faster rough checks using minute OHLC points | Intraminute path is simplified | | Open prices only | Strategies that make decisions at bar open and do not depend on intrabar behavior | Unsuitable for many stop/tick-sensitive systems |
Availability and data quality depend on symbol, date range, terminal, and broker history. The tester may need to download or prepare data, and the selected model should be verified in the test configuration rather than assumed from a saved report title.
Why the Modelling Mode Changes Results
An EA can make decisions on each OnTick() event. If it moves a trailing stop, reacts to a price threshold, or evaluates a condition several times inside one candle, the order of intrabar prices matters. A simplified model can therefore produce different entries and exits from a real-tick test.
Bar-based strategies can also be sensitive to assumptions. A candle's OHLC values do not reveal every path price took between its open and close. If both a stop and target fall within a bar, the tester needs intrabar information or a modelling assumption to determine what happened first. A generated path can differ from the historical path.
The term “real ticks” describes the historical input used by the tester, not a promise that historical data is complete or that future execution will match. Real trading includes changing liquidity, broker routing, latency, requotes, and other factors that historical simulation cannot fully reproduce.
Data quality is part of the test model. Verify the symbol and date range, check whether tick history exists for the whole period, and review tester messages about downloaded or substituted data. A model label cannot compensate for gaps in history or a symbol specification that differs from the live account. Also record the spread mode and commission assumptions with the report so a later comparison is meaningful.
A Practical Testing Workflow
- Use a quick mode for early screening only when the strategy logic fits its assumptions.
- Retest candidates with detailed tick modelling if the EA depends on intrabar changes, pending orders, tight stops, or trailing.
- Check history coverage and warnings for missing or substituted data.
- Use realistic spread, commission, and symbol settings. A detailed price path does not compensate for incorrect costs.
- Compare trades, not only summary profit. Inspect entry and exit timestamps, stop behavior, and differences around volatile periods.
- Forward-test on demo and compare live signal timing with the backtest.
When comparing TradingView to MT5, first align signals on completed bars, then investigate data and fill differences. See our guide to why strategy results differ and the MQL5 lot-size calculation guide for another source of performance variation.
For a strategy that only evaluates once at the open of a new bar, a faster mode may help screen logic, but validate the final candidate under more detailed assumptions if execution inside the candle matters. Conversely, a complicated tick model is not automatically useful if the EA's decisions do not depend on intrabar events. Choose the model based on the EA's behavior, then explain that choice in any published test result.
Frequently Asked Questions
Match the Model to the Strategy
Choose test settings based on how the EA behaves, document the selected mode, and rerun important candidates under more detailed assumptions. CodeFlowOS can help translate strategy logic into compiler-verified MQL5; the Strategy Tester setup and later demo validation remain your responsibility.