What a demo test can and cannot prove
A demo test can show whether a bot connects, receives market data, submits the intended contract request, handles the result, and follows its restart or stop rule. It can also reveal invalid stake values, unavailable contracts, and logic that loops unexpectedly.
It cannot prove future profitability. Market sequences change, and execution under real conditions may differ. Use demo as a technical and behavioural test, not as a prediction.
Build the smallest safe version first
Remove optional recovery systems and complex money-management logic. Begin with one market, one contract type, a small fixed demo stake, one purchase condition, and an explicit stop rule.
- Confirm the correct account is marked Demo.
- Check the selected currency and minimum stake.
- Verify duration and barrier settings.
- Make sure only one purchase path can fire at a time.
Watch the complete contract lifecycle
Do not judge the bot only by whether it placed a trade. Confirm the proposal, purchase, open-contract update, settlement result, profit or loss value, and final running state. The summary and journal should agree with the broker-side record.
Record failures before adding complexity
Write down the exact market, time, settings, browser message, and journal entry when something fails. Reproduce the issue with the simplest strategy possible. Only add progression systems or additional conditions after the basic lifecycle is stable.