GARUDAALGO RESOURCE CENTRE

A repeatable demo-testing workflow

Testing should answer whether you understand the software's behaviour and whether the setup is working as intended. A profitable test does not guarantee future returns.

Record the starting configuration

Write down the EA version, terminal build, broker demo server, symbol, chart period and every input you changed. Keep a copy of the original input values. Decide which behaviours you want to observe: whether orders are submitted correctly, whether position sizes match the configured rules and whether any dependency or permission errors appear. Obtain the product-specific settings from support; do not infer them from another EA's tutorial.

Separate historical tests from demo observation

A strategy tester runs the software against historical data and simulation assumptions. A demo account lets you observe it against ongoing quotes and a broker's demo execution. They answer different questions. Historical performance is affected by data and execution assumptions, while demo execution can differ from a live account. Treat neither result as a promise.

Inspect more than the final balance

Review individual trades and logs. Record costs, trade count and periods of losses alongside any gain. Use the tester's report to understand its stated drawdown and data quality rather than relying on a single headline number. Watch for unexpected orders, missing stops or errors, and ask the developer about behaviour you cannot explain. Avoid judging a system solely from a short run with only a few trades.

Change one thing at a time

Keep a baseline configuration, then document each change and its reason. Changing the timeframe, symbol and several inputs together makes it difficult to identify what caused a different result. Do not select a configuration only because it produced the best result in one historical interval. If you compare different periods, keep the assumptions visible so the comparison remains interpretable.

Keep a simple test log

For each run, record its dates, configuration, platform errors, observed order behaviour and unresolved questions. Save reports privately and avoid sharing account credentials or download tokens. Pause testing if software behaviour is unexplained. Contact support with reproducible details rather than continuing to change settings at random.

Reference: MetaTrader 5 Strategy Tester documentation. This is educational workflow guidance, not a recommendation to trade a particular market, allocate capital or use specific risk settings.