The client's idea
Parsianrah Financial Holding works EURUSD / XAUUSD / US30 on H1; the opening brief was: We run six terminals on two servers — tell us which setting lives where.
Project and starting point
As the team grew nobody held a complete picture of the live settings, and every execution problem was solved by guessing.
Solution architecture
One inventory of every run with version and setting tags, a consistent naming scheme, and a record of when each change landed on which terminal.
Version tags on every run moved problem tracing from asking colleagues to reading one table. It matches how EURUSD / XAUUSD / US30 is actually traded and can be tested against the data already available.
Why this design
Version tags on every run moved problem tracing from asking colleagues to reading one table. It matches how EURUSD / XAUUSD / US30 is actually traded and can be tested against the data already available.
Implemented capabilities
Modules and components built: Settings inventory + version tags.
Delivered output:
Trading terminal fleet documentation — EURUSD / XAUUSD / US30 (H1)
Specification document and the rule-to-code mapping table
Full MQL5 source, commented
Test report: Reconciliation across six terminals
Parameter document and install guide (7 weeks)
Safeguards and risk control
Every first run happens on a demo account, and the pre-live checklist is filled in before the live connection.
Backtest and forward test method
Test method: Reconciliation across six terminals.
Testing runs in three stages: a backtest on historical data, limited optimisation inside the contract's scope, and a forward run with the parameters frozen.
Tools and stack: MQL5, settings files, a version inventory.
Every figure from this project is published together with its measurement conditions: the data window, the tick model, the spread, the commission and the build of the executable. Without them a number cannot be compared with anything.
Publishable results
Finding the source of an execution bug dropped from hours to minutes, and the team ran its first quarterly review from that inventory.
Limitations and cautions
Every first run happens on a demo account, and the pre-live checklist is filled in before the live connection.
Every test result depends on the quality of the historical data, the broker's spread and market conditions, and none of it is a promise about the future. Through a severe price gap or a broker disconnection a stop loss cannot be guaranteed, so behaviour in those conditions must be reviewed separately.
Our next-step proposal
The next step is a quarterly settings review and keeping the documentation current with broker changes.
Portfolio
Measured results
These are the figures the test produced — not a promise about future performance.
- 15 scenarios Scenario test coverage
- 100 % Parity with the previous build
- 99.8 % Runtime stability in test
- 5 Defects fixed