🧪 Backtesting vs forward testing (and how to do both without fooling yourself)
You want two types of evidence:
Backtesting answers: “Does this have an edge when executed correctly?”
Forward testing answers: “Can I execute it live under pressure?”
Backtesting: do it in two passes (fast → strict)
Pass A: “Spot-check backtest” (speed + pattern recognition)
Goal: validate that the setup occurs often and behaves as expected.
Sample size: 100 valid occurrences
Data: at least 3–6 months, same session
Capture only:
Did the full checklist happen? (Y/N)
If entered, did it hit 1R before stop? (Y/N)
Max favorable excursion (MFE) and max adverse excursion (MAE) roughly
This pass prevents you wasting weeks on a setup that rarely completes or has ugly MAE.
Pass B: “Rule-locked backtest” (accuracy + numbers)
Goal: get real performance metrics with your exact rules.
Sample size: 50–150 trades depending on frequency
Rules frozen: entry trigger, stop placement, TP model, session window
Track at minimum:
Win rate
Average R
Expectancy (avg R per trade)
Max losing streak
MAE distribution (tells you if stops are too tight)
Time-to-TP (prop account consistency & psychology)
A healthy target for many funded styles is something like:
Expectancy: +0.20R to +0.50R (or more) with clean risk control
Even +0.20R can work if you’re consistent and don’t overtrade.