Manual backtesting
Automated backtesting tells you whether a set of rules would have made money. Manual backtesting tells you whether you can trade them. Replay historical charts candle by candle, place trades without knowing what comes next, and have every one of them recorded and measured.
Two questions
Automated backtesting
Fast across thousands of trades, perfectly consistent, and completely unaffected by how you feel. It also requires your strategy to be fully expressible as code: every entry, filter and exit.
Manual backtesting
Slower and smaller sample, but it tests the thing that actually happens in live trading: you, reading a chart in real time, making judgement calls under uncertainty. The only honest test of a discretionary edge.
If your strategy depends on context (structure, confluence, “does this look clean”), then a coded backtest is not testing your strategy. It is testing a simplified approximation of it, and the gap between those two is where live results disappear.
The usual failures
Problem 01
Scrolling back, switching timeframe, or glancing at the right edge tells you what happens next. Your test becomes a memory exercise.
In BacktestFlowThe replay is clamped to its present edge, and switching timeframe rebuilds the last candle from bars you have already replayed, so a higher timeframe never shows price that hasn't happened.
Problem 02
Fifty replayed trades later, all you have is an impression, usually a flattering one. The losers blur, the winners stay vivid.
In BacktestFlowEvery close opens its trade card (notes, tags, your checklist, up to 10 screenshots with the order lines still on the chart) and the replay waits until it is saved.
Problem 03
Sizing by feel makes results meaningless: a few oversized winners can carry a strategy with no edge.
In BacktestFlowSize by risk % or by lots, priced through each instrument's contract size and quote currency, with position sizing consistency reported back to you.
Problem 04
Setups you passed on never enter the record, so a strategy looks more selective than it was.
In BacktestFlowKeep a skipped setup as a case study: it stays in the record without touching your results, so the data shows what you passed on.
The session
Nothing to install: no plugin, no MetaTrader, no broker account, and no difference between macOS and Windows. Pick an instrument and a start date, and the chart loads with everything after it hidden. Switch on a prop firm challenge if you want its rules measured as you trade; how to backtest a prop firm challenge covers the method.
Step candle by candle or run at one of four speeds, with keyboard shortcuts for both. A clock shows which markets (Sydney, Tokyo, London, New York) are open at the chart's own instant.
Market, stop and limit orders from the side panel, or draw a Long or Short with TradingView's position tool and turn it into a real order. Entry, stop and target are draggable, and positions close in parts.
Each candle fills pending orders and checks stops and targets, then pauses on any event so nothing is decided off screen. Misread a move? On the Max plan, rewind 1 to 50 candles, with a red line showing the cut before you confirm.
Notes, tags and your strategy checklist, with screenshots captured while your order lines are still on the chart. The replay moves on once the trade is saved.
More than 40 metrics in five sections build themselves as you go. The free plan opens the Verdict and Edge sections: win rate, profit factor, expectancy, payoff and R distribution. Paid plans add drawdown, Monte Carlo and breakdowns by pair, session, hour and weekday.
Evidence
The clearest evidence that manual backtesting is under served is not our opinion: it is that traders keep building their own tools for it. MQL5, MetaTrader's own developer community, publishes articles like this one.
“Manual Backtesting Made Easy: Building a Custom Toolkit for Strategy Tester in MQL5”
You do not write a custom toolkit for a workflow a platform already supports natively. Estimates from community guides put a single year of manual replay at 10 to 40 hours depending on timeframe, which is why the difference between a tool built for this and a tool tolerating it compounds quickly.
Related
FAQ
Manual backtesting means replaying historical price data candle by candle and placing trades yourself, as though the market were live, without knowing what happens next. It contrasts with automated backtesting, where a coded set of rules is run over historical data.
Chart replay, bar replay and market replay all describe the same mechanic: hiding future price and stepping a historical chart forward candle by candle. Backtesting is what you do with it: placing trades, recording the results, and measuring whether the strategy has an edge. A trading simulator gives you the replay; a backtesting platform also keeps the record and computes the statistics. The distinction matters, because replay without measurement produces a feeling about your strategy rather than evidence.
They answer different questions. Automated backtesting tests whether a specification would have been profitable, and it is far faster over large samples. Manual backtesting tests whether you can execute a strategy in real time, including the judgement calls a discretionary approach depends on. If your strategy cannot be fully written as code, automated testing cannot validate it.
Yes. Manual replay requires no scripting, no Expert Advisors, and no programming. You step through historical candles and place trades on the chart, which is why it suits discretionary and price action strategies that resist being expressed as rules.
Look ahead bias creeps in whenever future price becomes visible: by scrolling forward, switching timeframe, or seeing a chart edge that extends past your replay point. The fix is a replay environment that hard limits history to the current bar, including when you change timeframe, rather than relying on your own discipline not to look.
No installation. BacktestFlow runs entirely in the browser, so it works the same on macOS, Windows and Linux: there is no download, no plugin, no MetaTrader required, and no broker account needed to start. Mac users in particular tend to hit this problem, because several established backtesting tools are Windows only and their documented workaround is to run Windows inside a virtual machine.
Estimates for replaying a single year commonly range from around 10 to 40 hours depending on the timeframe, since lower timeframes contain far more candles. Speed controls and keyboard shortcuts reduce that considerably, but manual backtesting is inherently slower than automated testing: the trade off is that it tests execution, not just a rule set.
Free planNo credit cardRuns in your browser