The best backtest run is a candidate, not a conclusion
Optimization compares many parameter combinations. That is useful for mapping a strategy, but the search process also creates selection pressure. After enough alternatives are tried, the historical winner may contain noise that happened to fit the chosen sample. Research on backtest overfitting formalizes this problem and explains why the number of tried alternatives matters when evaluating a result [5].
MetaTrader 5 forward testing addresses one part of this problem by reserving the later part of a selected date range and rerunning selected optimization results there [1, 2]. That makes forward testing a useful filter on an optimization decision. It is not a forecast of future returns and it does not convert an optimized EA into a proven system.
Freeze the experiment before you inspect the forward result
Before optimization starts, record the EA build, symbol, timeframe, date range, tick model, spread or commission assumptions, execution-delay setting, initial deposit, leverage, parameter ranges, optimization mode and ranking criterion. MT5 exposes these choices in the Strategy Tester. If several of them change between optimization and validation, you are no longer testing the stability of the same experiment.
MQL5 also allows an EA to return a custom optimization criterion through OnTester(), and TesterStatistics() can supply tester statistics to that logic [3, 4]. Treat the criterion as part of the experiment design. Rewriting the score after seeing which definition creates the most attractive leaderboard simply adds another layer of selection.
Worked example: investigate rank collapse instead of hiding it
Consider a hypothetical optimization with 600 parameter sets. Suppose the ten highest in-sample candidates are forwarded. One candidate ranks first in optimization but drops near the bottom of those ten in the forward segment, while several mid-ranked candidates remain clustered with similar trade counts and drawdown. These figures are illustrative only and are not BamaUp backtest results.
Do not average the two equity curves into one comforting number. Investigate why the ranking changed. Compare trade count, maximum drawdown, average trade, exposure and strategy-specific diagnostics. Then inspect sample trades that exist in one segment but not the other. A rank collapse can reflect overfitting, but it can also expose regime dependence, too few observations, a spread-sensitive rule or a parameter boundary that worked only in one slice of history.
A forward period can become part of development
A reserved forward period is most useful before it influences design decisions. If you inspect that result, change code or parameter ranges, and repeatedly optimize against the same forward period, it gradually becomes part of the research process. After that, it should not be described as untouched evidence. Keep another later period or rolling evaluation window untouched when the project is important enough to justify it.
There is no universal pass percentage for this step. A low-frequency system and a high-frequency system produce very different sample sizes, and a small numerical change can be critical for one design but irrelevant for another. Define acceptance and failure conditions from the strategy's claimed behavior before you look at the validation result.
Practical acceptance test for your next MT5 optimization
Run one documented optimization, save the candidate set, and lock the optimization inputs. Enable MT5 forward testing for the reserved later segment. Record the same metrics for each forwarded candidate and flag unexplained behavior changes rather than promoting the highest single metric automatically. If the forward result causes a code or parameter change, record that exposure in the experiment notes.
The MetaTrader and MQL5 references cited here were rechecked on 28 September 2026. Broker history quality, symbol specifications, execution assumptions and future market behavior remain external limitations. Continue with BamaUp's free Auto-Trading Foundations path and EA validation checklist. Historical and forward testing can expose fragile assumptions, but neither can guarantee future returns.
