1. Confirm the exact EA
Use the intended desktop terminal and inspect the selected Expert Advisor, build/version and loaded .set file. A similarly named product, an older EX5 or a different terminal data folder is a different test.
MT5 troubleshooting
EA will not run or
will not trade in Tester?
Start with the evidence. A completed compile or an installed file does not show that Strategy Tester used the intended EA, symbol, settings or data.
2. Check symbol and history
Select the broker’s actual instrument, including any suffix. Confirm the test dates, timeframe, available history, tick/data model and applied spread, commission and swap.
3. Read the Journal first
Record initialization, permissions, symbol, order-validation and runtime messages. An error message is more useful than guessing from an empty trade list.
4. Inspect effective inputs
Check trading switches, session windows, news filters, minimum-history requirements, lot limits and spread gates. A legitimate entry condition may simply not occur in the selected period.
5. Begin with a short visual run
Use a small date range to confirm initialization, timing, calculated volume and order handling. Then run a representative period and save the report.
6. Preserve the evidence
Keep the tester report, Journal/Events, exact parameters, package/build, symbol, dates and data/cost model together. Do not call a test complete until those records exist.
Make the next run comparable
Write the test inputs down first, then use the product’s manual for its exact build. A historical result does not establish future performance or suitability.
Educational checklist only
This page is not trading advice and does not promise that an EA will trade, pass an evaluation or achieve a result. Test on your own data and environment before considering any live exposure.