A trading interface can look convincing while hiding problems in the setup. Treat a demo run as a software acceptance check: you are trying to find out whether the actual release behaves as intended on your terminal, broker and account.
Record the environment first
Write down the EA version, MT5 build, broker, symbol name, account type and preset. Keep a copy of the preset you test. Without that record, a later comparison may quietly involve a different configuration.
Check one complete cycle
Follow a setup from observation to order request, execution and closure. Confirm the side, size and exit rules against the settings. Review the terminal and EA logs when no trade occurs; a rejected setup is not automatically a malfunction.
Test the quiet moments
Normal operation includes doing nothing. Observe behavior outside your trading session, during a configured news pause and when data or an API connection is unavailable. Make sure you understand whether the software waits, rejects a new entry or uses a documented fallback.
Verify the limits
A risk setting is useful only if its definition matches your expectations. Determine whether a boundary concerns balance or equity, when it resets and whether it blocks new entries or also closes existing positions. Demo testing should include those edge cases, not only a sequence of successful entries.
Separate operation from performance
A demo check can establish that the software runs and follows its rules in the conditions tested. It cannot establish that a strategy will remain profitable. Execution, spreads, slippage and future conditions may differ.
Use the ChatGPTFX setup guide for the product workflow and read the risk disclosure before considering live use.