Quintara Gold. The MT5 backtest walkthrough.

The recorded example

The video uses MarkQuant’s developer build of Quintara Gold v4.27 with additional stop-request checks, tested in MT5 build 6230, with VTMarkets-Live 9 Gold history and a refreshed embedded news-calendar snapshot covering the test period. This is a tested development build, not a claim that the same update is already available on MQL5 Market. Customers can follow the workflow with the official Market demo and its matching preset.

One month, with 100% real ticks reported by MT5. The test reaches the end of the requested period without an early calendar stop. Gold’s last market tick in this interval is on Friday 9 October; the remaining dates are the weekend. The report contains 56 trades, including 11 losing trades.

The updated build adds request validation and explicitly handles a position closing during a stop update. MT5 still records one native rejection. Read the warning explanation below; a 100% history-quality score describes the data, not flawless execution or future profitability.

Use this recording to learn the testing workflow. A single month cannot establish robustness or predict live returns. The calendar resource covers the test period. The strategy rules, preset and 10 ms delay were preserved; request validation and diagnostic handling were updated.

Deposit, leverage, delay, and sizing are illustrative assumptions. Record your own broker’s costs and execution conditions when evaluating the software.

Why does MT5 still show “Invalid parameters”?

In this run, the position closed at take profit while a stop update was in transit. At 03:31:10 broker time on 28 September 2026, position 391 was open when its update was sent. During the simulated execution delay, take profit closed it. MT5 then rejected the update because the position no longer existed.

1. The EA checks the stop-update request before submitting it.
2. If the position closes during submission, the updated build records that outcome, clears the resolved intent and does not retry.
3. The original MT5 warning remains visible. The EA does not claim the requested stop was installed.

The journal’s “#0” is part of MT5’s failed-modification display after the position closed; the submitted request targeted position 391. Checking a request first cannot guarantee that a position will remain open while the request is processed.

This specific event did not change the trades or results. Every order and deal row matches the prior build, and no unresolved stop requests remain at completion. This explanation applies to the verified event in this test; other “Invalid parameters” messages can have different causes and need investigation.

Results and evidence from the latest rerun

These figures describe one selected historical month. They do not establish long-term robustness or predict live returns. The latest build compiled with zero errors and zero warnings; a compiler warning is different from a trade-execution message.

Download the settings, build fingerprint and result summary · Read the relevant tester journal excerpt

1. Get the demo and matching settings

Open the official Quintara Gold listing on MQL5 and use its free demo option. Install it in the desktop version of MetaTrader 5. The Market demo works in Strategy Tester; it does not unlock an online trading chart.

Download the preset from the Quintara Gold setup guide. Match it to your installed EA version. Keep the original file so you can identify exactly what you tested.

You will need a broker connection with historical Gold data. Quintara uses an XAUUSD M15 hedging setup. Check your broker’s Gold symbol name, contract specifications, trading sessions, and account compatibility.

2. Select Quintara Gold in Strategy Tester

1. Open View → Strategy Tester in desktop MT5.
2. Select a single test and choose the installed Quintara Gold Expert Advisor. You can also right-click the EA in Navigator and select Test.
3. Choose your broker’s Gold symbol and the M15 timeframe. Symbol suffixes vary by broker.
4. Leave optimization disabled for your first run. This walkthrough examines one known configuration.

On macOS, MT5’s Windows menus may look slightly different because the desktop app runs through Wine. Use the menu names rather than relying on a Mac keyboard shortcut.

3. Load the preset, then check the inputs

In the tester’s Inputs tab, open the context menu and choose Load. Select your version-matched .set file. Verify the values after loading; the filename alone is not confirmation.

The standard v4.27 Auto Risk preset is named Quintara_v4.27_15_10_AUTO_BASE_1pct_PropOFF.set. It selects Auto Balance Risk with a 1% base target, enables all five engines, uses the scheduled news filter with 15 minutes before and 10 minutes after, and leaves the optional prop-firm daily guard off.

Summit uses twice the base target: a 1% Auto Risk base target means a 2% target for Summit. With a $1,000 starting balance, those initial planned stop-risk amounts are $10 and $20 respectively, before costs and execution differences. Several positions can overlap, and minimum-lot constraints can increase exposure relative to a percentage target. Neither setting caps total account loss.

Confirm the tester’s broker-time alignment against the guide. The preset’s historical winter and summer offsets must suit the broker you are testing. Keep notes of any changes instead of silently overwriting your baseline.

4. Record the conditions before pressing Start

Choose your dates before viewing the result. Use Every tick based on real ticks where the broker provides the data, and check the journal afterward for gaps or substitutions. A selected modelling option alone does not establish data quality.

Use realistic assumptions for the account you intend to evaluate. Check symbol specifications and the resulting deals for costs; do not assume that an attractive profit figure includes every live trading expense.

Download the blank test log (CSV) to keep the conditions with your report.

5. Run the test and inspect the journal

Press Start. The first run may take longer while MT5 retrieves history. Let the run finish and confirm that it covered the intended dates. Enable visual mode to watch the dashboard, pending orders, entries, and exits on the historical chart. The recorded example above uses visual mode, a 10 ms fixed delay, and 1:500 leverage. These are simulated trades, not live account transactions.

Open the Journal and check initialization, data availability, invalid stops or volumes, rejected orders, and errors. A test that finishes with missing data or repeated execution failures needs investigation before its results can be interpreted.

In the graph and backtest report, examine equity alongside balance. Review equity relative drawdown, maximal drawdown, losing sequences, trade count, and individual deals. Keep the original metric labels: relative and maximal drawdown are different measures and can identify different drawdown episodes.

6. Save the evidence and repeat the comparison

Export the completed report from the tester’s report or backtest context menu. Save it together with the preset and journal. Record the MT5 build and broker server so another test can be compared on the same basis.

A short demonstration teaches the workflow; it cannot establish that a strategy is robust. Evaluate longer and different market periods, keep a chronological period apart from settings selection, and test plausible changes in costs and delay. Preserve unsuccessful runs as well as successful ones.

Before sharing screenshots or reports, remove account numbers, private balances, credentials, and personal details. For setup help, send MarkQuant the EA version, preset name, broker symbol, test dates, and a redacted error message.

Common testing questions

Can I use the free demo on a live or online demo chart?

The MQL5 Market demo is for Strategy Tester. An appropriately licensed version is needed for an online chart.

Why does my result differ from another backtest?

Compare the EA version, inputs, broker data, dates, symbol specifications, costs, delay, deposit, and leverage. A difference in any of these can change the result.

Why are there no trades?

Start with the journal. Check that the EA initialized, the correct symbol and period were selected, data is available, and the preset’s filters and broker-time settings are appropriate. Do not disable protective filters simply to produce a more attractive report.

Does a profitable test prove Quintara Gold will make money?

No. A backtest is a historical simulation under stated assumptions. Future market conditions and real execution can differ. Gold trading can produce substantial losses.

Video transcript

0:00 — Start with the test.

Welcome to Mark Quant. This updated Quintara Gold walkthrough uses our version four point two seven developer build with additional stop request checks. We test one month with VT Markets, a one thousand dollar balance, and the one percent Auto Risk preset. We also explain a warning that remains in the tester journal.

0:24 — 01 / Set the conditions

Open Strategy Tester and select Quintara Gold. Choose the VT Markets gold symbol with its E C N suffix, and M fifteen. Set September twelfth to October twelfth, a one month test period. Use one thousand US dollars, one to five hundred leverage, and a ten millisecond delay. Select every tick based on real ticks. Enable visual mode and leave optimization off.

0:53 — 02 / Load the matching preset

In Inputs, right-click and choose Load. Select the standard one percent Auto Risk preset for your installed version. This example leaves the optional prop firm guard off. Always check the values after loading.

1:10 — 03 / Check position sizing

Confirm Auto Balance Risk mode and a one percent base target. On a one thousand dollar balance, that starts at ten dollars of planned stop risk for a base position. Summit targets twice that amount. Multiple positions can overlap, and minimum lot constraints can increase exposure. These settings do not cap total account loss.

1:35 — 04 / Watch the simulated trades

Here is the visual replay from our one month test. Watch the pending orders, entry and exit markers, and the dashboard. Balance reflects closed trades; equity also includes open profit or loss. The replay is accelerated. Check that the test uses your intended broker and gold symbol, and review both winning and losing trades. These are simulated historical trades, not live orders.

2:15 — 05 / Read the latest report

The latest build completes the full month with one hundred percent real ticks. The report contains fifty six trades, including eleven losses, and nine hundred fifty eight dollars and seventy one cents in net profit. Maximum equity drawdown is nine point one seven percent. Every order and deal matches the previous build. These are historical results for one selected month, not a forecast.

2:43 — 06 / Understand the warning

On September twenty eighth, a position hit take profit while its stop update was in transit. The position existed when the request was sent, but had closed when MetaTrader processed it. MetaTrader still logs invalid parameters. The updated build checks the request and explicitly records that the position closed, without retrying or claiming the stop was applied. The strategy settings and ten millisecond delay stay the same. This specific event did not change any trades or results. Investigate other warnings separately.

3:22 — 07 / Keep the evidence

Right-click in Backtest, choose Report, then HTML. Save the report with your preset and journal. Record the broker, symbol, dates, deposit, and execution settings. Use longer periods and realistic costs for a proper evaluation.

3:41 — Make your own test.

Try the free Strategy Tester demo from the official Quintara Gold listing on MQL five. The written walkthrough is at Mark Quant Labs dot com. Historical results do not guarantee future returns. Gold trading can produce substantial losses.