How Backtesting Works, And What It Can't Tell You
Backtesting replays a strategy against historical data. What the process does, why results look better than they were, and how to read a report honestly.
Hot Topic
Testing a strategy against history: how engines work, why results flatter, and what validation can and cannot establish.
2 pieces published on this topic · Updated
A backtest answers one narrow question well: given this exact rule set, applied to this exact historical period, with these assumptions about costs and fills, what would have happened? Every word in that sentence is carrying real weight, and most disappointing live results trace back to one of them having been quietly ignored.
The value is real but negative in character. A backtest is far better at eliminating strategies than at endorsing them. A rule set that fails over ten years of data has been usefully ruled out. A rule set that succeeds has passed one test, on data that already exists, in a period that will not repeat. This is a much weaker statement than it feels like.
The failure modes are well documented and mostly structural rather than mathematical: lookahead bias, where a rule reads information it could not have had; survivorship bias, where delisted instruments are missing from the data; and overfitting, where a strategy has been tuned until it describes the noise in one particular history. None of these show up as an error. They show up as good results.
Blog posts covering this topic.
Engineering deep-dives covering this topic.
Describe a strategy in plain language, backtest it against historical data, and paper trade it before any capital is committed.