Start freeSign in
Free tool

Backtest evidence checklist

It is easy to make a backtest look excellent when the idea underneath it is worthless. These 22 checks are the ones that separate a test you can act on from one that flatters a bad idea. Tick what is true of your own strategy. Nothing is sent anywhere, and your answers stay in this browser.

Passing every check does not mean a strategy will make money. It means the test was honest, which is a different claim and the only one anybody can make for you.

0 / 22 Tick the checks that are true of your strategy.

Costs are in the test

A strategy that trades often is the one most flattered by leaving costs out. This is the cheapest way to turn a losing idea into a winning chart.

The sample is big enough to mean anything

Thirty trades tell you almost nothing. The error bars around a win rate estimated from thirty samples are wide enough to contain both a real edge and pure luck.

The parameters were not tuned to death

Try enough variations and one of them will look brilliant by chance alone. That is not a discovery, it is a search result.

It was tested on data it never saw

Tuning and testing on the same data is memorising the answers and then sitting the same exam. This is the single most common way honest people produce dishonest backtests.

Risk was measured, not assumed

A result without its worst moment attached is half a result.

You wrote down what would make you stop

Deciding this in advance is the difference between a plan and a hope.

What to do with the gaps

An unticked box is not a failure, it is the next piece of work. Fix the cheapest one first: costs and the held-back slice cost nothing but discipline, and between them they catch most of what goes wrong.

Sonar Sciences enforces this list by default rather than leaving it to discipline: costs are always on, the out-of-sample gate decides before you can commit money, and the record keeps its losing periods. The Studio is free. Open the Studio →