MT4 EA demo testing checklist

Download the free demo test log

Download the MT4 demo test log (CSV). Open it in Excel, Google Sheets or another spreadsheet. Keep a separate copy for each release and configuration. The blank rows let you record what you expected and what the terminal actually did.

1. Record your starting conditions

Write down the EA version, installation date, broker, exact demo server, symbol including any suffix, chart timeframe, starting balance, account currency and leverage. Save the input settings you used. Note the broker’s minimum lot size and lot increment: the same input can behave differently under different contract specifications.

Choose a demo account and confirm its status inside your trading terminal. The MR SOLANKI 15-day trial is for demo accounts only. A live account does not become eligible simply by adding the word “demo” to a label. Use the separate trial download in the members area.

2. Check installation and connection

1. Use desktop MT4 and follow the MT4 installation guide. This release does not run inside the MT4 mobile app or on MT5.
2. Install the correct EA build and attach it to the intended chart. Confirm the terminal and EA settings permit automated trading.
3. For online licence checks, allow only the WebRequest addresses supplied with your current download. Copy them exactly; do not enable unrelated addresses.
4. Confirm the EA reports an authorised demo connection. If it does not, record the exact Experts or Journal message and check the account, server and licence details.
5. Keep MT4 connected while observing it. A website login alone does not mean the EA is running.

For platform behaviour, see MetaQuotes’ Expert Advisor documentation.

3. Observe actions, not just returns

Record initial entries, later additions, individual lot sizes, combined basket exposure and basket closures. Compare the actual orders with the configured maximum levels and lot limits. Capture the time, spread, prices and log messages around an unexpected action.

Also record occasions when the EA correctly blocks an entry. Market filters and licence checks may prevent trading. No trades during a short test does not by itself prove a fault. Avoid forcing an order merely to make the chart look active.

If you change settings, save the old configuration and start a new test record. Otherwise it becomes difficult to explain which setting caused the result.

4. Measure drawdown and open exposure

Track balance and equity separately. Closed profit can look positive while open trades carry a large floating loss. Record the highest observed drawdown, maximum simultaneous orders, largest combined lot exposure and longest open basket.

MR SOLANKI uses martingale position sizing, which can increase exposure after adverse price moves. Filters and configured loss limits cannot guarantee an execution price or prevent substantial losses. Read the trading risk disclosure and the risk-management guide.

5. Check interruptions and denied access

Observe what happens after a normal terminal restart and reconnection. Record whether the EA recognises existing positions and reports its licence status clearly. Do not deliberately interrupt a running live account to test a failure.

If access is denied, copy the exact reason into the test log. An expired trial, paused account or wrong account type needs a different response from a connection timeout. Contact support@mrsolanki.co.uk with the release version and relevant log lines. Remove licence keys, passwords and unnecessary personal information from screenshots.

6. Review the evidence before making a decision

At the end of the trial, compare the expected behaviour with your records. Resolve unexplained entries, missing closures or licence errors before considering any further use. Fifteen days may not include every market condition or expose every weakness.

Demo execution, liquidity, spreads and slippage can differ from live trading. The membership release’s online licence workflow is not a substitute for a historical backtest; use the testing methods supported by that exact release. A profitable demo period does not establish a safe live configuration.

What to record in the worksheet

For each observation, record the timestamp and time zone, release, server, symbol, settings reference, expected action, observed action, balance, equity, spread, open orders, basket lots and evidence file. Mark each finding “checked”, “needs investigation” or “resolved”. Keep logs factual rather than selecting only profitable outcomes.

This guide is published by the EA developer. It explains testing steps and limitations; it is not an independent product review or a promise of returns.