Testing EdgeDriven Multi Asset Portfolio Across All Six Markets
A Multi Asset test can finish while only part of the intended portfolio has been able to trade. Before judging the profit curve, establish which markets were available and whether their modules could participate at the selected account size.
EdgeDriven Multi Asset Portfolio manages 11 fixed strategy modules from one EA. This guide covers symbol mapping, risk settings and the result checks that distinguish a full-portfolio test from a partial one.
1. Install the demo and check the six markets
Download EdgeDriven Multi Asset Portfolio from Market in desktop MT5. Select the installed demo in Navigator and choose Test to open Strategy Tester. The free Market demo is a historical tester evaluation, not a live-account trial; MQL5's demo-testing guide explains the workflow.
Use hedging position accounting; check the risk-management model under Margin in the tester's advanced account settings. Enable the required instruments in Market Watch, then check the EA's detected mappings against the broker's actual contracts:
| Intended market | Fixed modules |
|---|---|
| USDJPY | 4 |
| BTCUSD | 3 |
| EURUSD | 1 |
| GBPUSD | 1 |
| XAUUSD | 1 |
| US100 | 1 |
Automatic detection supports common aliases and broker prefixes/suffixes; manual mapping is also available for each market. Confirm the underlying instrument and contract specifications, not just a familiar-looking name. An index or Bitcoin contract may have a different trading session, lot size or minimum volume from the reference.
If a market is unavailable, its modules remain inactive while available modules can continue. Their budget is not redistributed. That run can reveal compatibility issues, but it is not a test of the complete six-market portfolio.
2. Choose a repeatable broker-data test
For the first broker-data check in this guide, select the broker's USDJPY as the tester's main symbol and H1 as the main chart period. This is a consistent starting setup for the guide, not a claim that the custom-symbol reference used that same main chart. The EA reads H1, H2 and H4 internally; the selected chart period does not replace those strategy timeframes.
Record the main symbol and ensure the required history is available across all six markets. Choose the test interval before examining the result. Where histories begin on different dates, record the coverage rather than treating unavailable years as years without signals.
The published Standard reference is:
| Setting | Standard Combined reference |
|---|---|
| Test interval | 2017-05-08 through 2026-06-30 |
| Initial simulated deposit | USD 100,000 |
| Leverage / account mode | 1:100 / hedging |
| Modelling method / data | 1 minute OHLC / custom symbols and reference costs |
| Risk Mode | Standard, 5% |
| Risk Base | Balance |
MT5 excludes the end date, so a run including 30 June ends at 2026-07-01. Using your broker's data instead of the reference custom symbols changes the test conditions. Matching the dates and risk inputs alone does not reproduce that dataset.
3. Keep the risk setting visible
The choices are Low 2%, Standard 5%, High 10% and Custom. Standard is the default; Balance is the default sizing basis, with Equity also available. The percentages are sizing settings, not guaranteed maximum drawdowns.
Use a single test with optimization disabled. For a comparison with the Standard row, retain Standard and Balance. Do not compare it as though it used the original 1.10% profile: the published Development, Validation and Final phase rows use that earlier profile, not the current 5% Standard setting.
USD 100,000 is a simulated reference deposit, not a universal funding requirement. A second test at the account size you intend to evaluate is important because smaller accounts may skip more trades at minimum lot. Do not assume the published 5% or 10% results apply to a smaller account, or raise risk just to restore missing trades.
4. Check participation before performance
Review the tester Journal, any available module diagnostics and the deal history. Look for unresolved symbols, unavailable H1/H2/H4 history, initialization failures, margin refusals and minimum-volume skips.
Check that all six markets were available to their modules. This does not mean every module must trade in every short interval. A module with no qualifying signal is different from one unable to access its instrument. Use diagnostics and test coverage to distinguish them; a zero in a trade summary alone is not enough.
Retain the release's documented news and weekend settings and any related messages. A quiet Bitcoin weekend is not automatically a defect: this product has weekend controls and is not designed for continuous weekend Bitcoin trading. A tester run also does not establish that the live Economic Calendar connection is healthy.
5. Judge the portfolio that actually ran
Once participation is understood, examine the equity curve, drawdown, costs and trade count together. Keep the exact drawdown label and money amount, and inspect the contribution of each market where the report or diagnostics provide it.
A missing Bitcoin or index component can make an incomplete test look better or worse. Either way, do not label it a full-portfolio result. Likewise, a lower drawdown on a small account may partly reflect skipped trades rather than the same portfolio operating at a lower scale.
Save the report, inputs, six symbol mappings and relevant Journal messages. If something is unclear, send those details through MQL5 Comments or Messages, with credentials removed. Include the product version, MT5 build, actual dates, model, simulated deposit, currency and leverage.
The published evidence is historical production backtesting. A correctly completed demo is useful for evaluating the tested setup, but it does not predict live returns or guarantee that diversification and risk controls will limit future losses.
