Testing & evaluation
MT5 real ticks: check the data behind your backtest
The selected modelling mode is the beginning of a data-quality check. A useful test record also shows which broker supplied the history and which dates were actually available.
Check the available interval
Use the exact broker server and symbol, including its suffix. Request the intended dates and inspect the tester journal for downloads, missing history and the actual testing interval. A date entered in the settings is not evidence that the server supplied complete tick history for that entire period.
Understand what the mode does
The real-tick mode uses broker-recorded ticks where available. MT5 documents how missing or inconsistent tick intervals can be handled using generated ticks. Read the tester messages and report quality information before describing a run as entirely recorded real-tick history.
Keep a compact evidence sheet
- Broker server and full symbol name.
- EA build, inputs and selected timeframe.
- Requested dates and actual covered dates.
- Modelling mode, deposit, leverage, costs and execution delay.
- Report and relevant journal messages.
Change data sources consciously
A different broker can have different quotes, sessions and contract rules. If you repeat a test elsewhere, describe it as a separate environment. Keep the original run so you can tell whether a result changed because of code, inputs or data. This makes published reviews easier for readers to follow.
Make it yours with MQLume
MQLume’s Learn reviews put test settings beside the results. Read the The Gold Reaper review to see how context helps turn a chart into a useful explanation.