Project specifications
- Market
- XAUUSD / EURUSD
- TF
- M15
- Platform
- MT5
- Client type
- Existing EA owner
- Delivery window
- 8 weeks
- Stack
- MQL5, settings files, run-id logging
- Strategy
- Local parameters instead of copied builds
- Modules
- Per-account settings + run ids
- Testing
- Four accounts from one build
Who this was for
Sarve Trading Team
- Role
- Multi-account execution team
- City
- Shiraz
- Project reference
- TBT-1408-30
The client's idea
Sarve Trading Team works XAUUSD / EURUSD on M15; the opening brief was: One build runs on four accounts and change management has become painful — tidy it up.
Initial challenge
The team kept one copied build per account: every fix had to be applied four times and the copies slowly drifted apart.
Solution
A single build with a separate settings file per account, a run id in every log line, and the gratuitous differences between copies removed.
Why this design
The run id on every log line makes it easy to trace one account's problem without reproducing it. It matches how XAUUSD / EURUSD is actually traded and can be tested against the data already available.
Safeguards and risk control
Every change starts from a saved backup, and the previous behaviour is kept as the test reference.
Our next-step proposal
The next step is a full technical review of the expert and clearing the old code's debts.
Portfolio
Measured results
These are the figures the test produced — not a promise about future performance.
- 100 % Parity with the previous build
- 9 Defects fixed
- 12 scenarios Scenario test coverage
- 26 Configurable inputs
Portfolio
How the delivery ran
Every project moves through these five phases, with the window for each agreed in the specification.
-
Discovery and problem framing
CompletedAuditing the existing code, finding the cause of the fault and fixing the change scope on XAUUSD / EURUSD.
Day 2–6
-
Written specification
CompletedA written list of approved changes — and of what stays untouched at this stage.
Day 7–17
-
Implementation
CompletedApplying small, reviewable changes instead of needlessly rewriting healthy parts.
Day 18–37
-
Testing and validation
CompletedRegression testing the old behaviour and targeted testing of what had to change.
Day 38–49
-
Handover and support
CompletedHandover of the fixed build with a change report and the reason behind each change.
Day 50–53