Skip to article
ONYX
ENRU

ONYX / MT5 STRATEGY TESTER

Same EA. Different execution conditions.

Why can an EA backtest change when you switch brokers? Entry logic is only one part of the answer. Compare symbol specifications, tick history, trading costs and execution settings before drawing a conclusion.

Inspect four conditions

01 / METHOD

Conditions first. Report numbers second.

Repeat these four checks for each broker or account. This is a comparison method, not an ONYX test result or a broker recommendation.

  1. 01

    Specify

    Which instrument did you actually test?

    In Market Watch → Specification, record the broker's exact symbol, digits, contract size, tick size and value, spread type, volume minimum and step, stop level and execution mode. The same XAUUSD label does not prove identical trading conditions.

  2. 02

    Model

    Which prices and costs entered the test?

    Record the broker server, history period, tick-generation mode, spread, commission and swap assumptions. Use broker-provided real ticks when available. A report built from generated ticks is a different test, not a failed version of a real-tick run.

  3. 03

    Stress

    Does the result survive less ideal execution?

    Keep the EA version, dates and Inputs fixed. In separate runs, examine the tester's execution-delay settings and supported symbol or account-cost settings. Compare changed fills and possible slippage. Do not change several assumptions at once or call an ideal no-delay run a live forecast.

  4. 04

    Explain

    Where did the difference arise?

    Compare Journal, Orders, Deals and the report: rejected requests, unfilled pending orders, fills, costs, drawdown and losing periods. If small plausible condition changes reverse the conclusion, record the sensitivity rather than selecting only the best-looking run.

02 / RUN RECORD

Keep a record that makes the comparison useful.

For two runs, keep dates, EA version and Inputs the same; change only the condition under investigation. Do not publish account IDs, credentials or licence keys.

Instrument
Exact broker symbol, contract and tick specification
Data
Server, date range, tick mode and available history
Execution
Delay setting, spread, commission, swap, volume and stop rules
Result
Orders versus deals, net result, drawdown and losing periods

03 / INTERPRETATION

A difference is a question, not a promise.

Spread

Symbol specification shows spread in points or a floating-spread designation. One specification snapshot does not describe every historical spread change.

Delay

The tester can emulate trade-request delay. This is a sensitivity check, not an exact record of future fills.

Demo

A historical run shows behaviour under its chosen conditions. Inspect the Journal and real account constraints before judging suitability.

04 / YOUR NEXT CHECK

Apply the method to a demo, not a claim.

Published ONYX demos run in the MT5 Strategy Tester. Read the selected product's requirements, then save the conditions of each run. Purchase and rental are available only through MQL5 Market.

How to run a Market demoCompare four Expert AdvisorsMT5: symbol specificationMT5: Strategy Tester

Trading can result in loss. A historical test cannot guarantee future profit or identical execution on another account.