MT5 EA and cTrader cBot testing guide

Optimise first.
Check again later.

The best row in an optimisation table was selected because it fitted the chosen historical dates. Here is how to test those settings on a separate period before drawing a conclusion.

Three records to keep

  1. SelectionDates and inputs used in optimisation
  2. CandidateExact saved settings and build
  3. Independent checkCompleted report from later dates

Before tuning

Keep a later historical period aside

Choose the broker data, symbol, timeframe and full date range before searching for settings. Reserve the later portion for checking a candidate. Write down the split and keep those later results out of the choice of inputs.

MetaTrader 5 has a Forward setting in Strategy Tester optimisation: selected runs are tested on a later, non-optimised segment. cTrader optimisation tests multiple input combinations over the selected historical dates; you can then backtest the chosen settings separately on later dates. A platform label does not make a period independent if you repeatedly tune after seeing it.

MetaQuotes: Strategy Optimization · cTrader: optimise a cBot

Make it repeatable

Save the exact candidate

Record the EA or cBot name and build, applied settings or parameter file, broker symbol, timeframe, starting capital, leverage, data source and trading-cost assumptions. Keep the optimisation report with the settings you actually selected. When the platform provides it, record how many combinations you tried. A screenshot of the top profit figure cannot reproduce the test.

Use our Backtest Plan Generator to capture the setup before running the later check.

After selection

Run the later check unchanged

Apply the saved settings to the reserved dates. Compare trade count, net result and maximum equity drawdown. Inspect whether one trade or short stretch drove the outcome, and note open positions at the cutoff where the report shows them. A small later sample may remain inconclusive even if its curve looks attractive.

If you change inputs, risk limits, costs or broker data, label that run as a different test. If a disappointing result leads you to tune again, the later period has influenced development; it is no longer untouched validation data for the revised settings. Choose fresh data for another independent check when possible.

cTrader: backtest dates and report

Evidence checklist

Keep the reports in order

  1. Save the original optimisation settings and date range.
  2. Save the selected parameter file and reason for selection.
  3. Save the completed later-period report, trade history and relevant logs.
  4. Note cost or data gaps and whether positions remained open at the end.
  5. If the product and marketplace terms allow it, observe the unchanged candidate separately on a broker demo account.

Our backtest reading guide explains how to assess return, drawdown, trade count and costs together. To evaluate a particular product, compare MT5 EAs and cTrader cBots, then read its documentation and current official Store listing.

What this check can and cannot show

A later-period backtest is still a historical simulation. It can expose some fitting problems, but it cannot establish future profitability, a prop-firm pass or live readiness. Automated trading carries substantial risk. We develop and sell ExpertCodeFX trading software; this is general education, not a performance claim.