← Research archive
NQ2026-08-14

How to Backtest a Trading Strategy Without Fooling Yourself

How to backtest a trading strategy honestly: baselines, sample size, and avoiding p-hacking traps.

Most backtests aren't tests at all — they're exercises in convincing yourself that something works. I've spent the past year running a systematic research project on Nasdaq-100 futures price action, testing dozens of session-timing and entry hypotheses against historical data, and the biggest lesson had nothing to do with indicators. It was about how easily a backtest lies to the person running it. If you're trying to figure out how to backtest a trading strategy in a way you can actually trust, the process matters more than the strategy itself.

Write the Rule Down Before You Touch the Data

The single most common mistake is testing a "strategy" that only exists in your head as a vibe — "buy pullbacks in an uptrend," "fade the open," "wait for confirmation." None of that is testable until it's written as an unambiguous rule: exact entry trigger, exact stop, exact target, exact session window. I write every hypothesis as a numbered statement before I run a single query. If I can't code the rule into a deterministic script, I don't trust the backtest, because that usually means I'm secretly eyeballing chart patterns after the fact and calling it a system.

Set a Baseline Before You Get Excited

A win rate or an equity curve means nothing on its own. The question isn't "did this make money," it's "did this beat doing nothing, or doing the naive thing." Before I evaluate any entry idea, I run the same test against a random-entry baseline in the same session window. If patient, confirmed entries and random entries produce similar results, the "edge" I thought I found is just the underlying volatility of the session, not my rule. This single habit has killed more of my own ideas than any other part of the process — and that's the point.

Respect Your Sample Size

Twenty trades is a story. A hundred trades is data. I hold a hard floor of at least 100 occurrences before I'll draw any conclusion from a backtest, and even then I treat the result as a hypothesis worth more testing rather than a proven edge. Small samples are dangerous because they're persuasive — a 15-trade sample with an 80% win rate feels like discovery, but it's usually noise wearing a costume. The market doesn't owe your sample size statistical significance just because you were excited to test it.

Watch for Granularity and P-Hacking Traps

This is the one that gets sophisticated traders too. If you test 40 variations of a stop-loss distance, a time window, or an indicator length and report only the best one, you haven't found an edge — you've found the best-fitting noise out of 40 tries. I've caught myself doing this: narrowing a session window from "9:30–10:30" down to "9:47–10:12" because that's where the historical numbers looked cleanest. That's not a strategy, that's curve-fitting with extra steps. The fix is boring but effective: decide your parameter ranges in advance, test the whole range, and expect performance to degrade smoothly at the edges rather than spike at one magic number.

Test Out of Sample, Then Test Again in Real Conditions

Split your data before you start — build the rule on one period, validate it on a period you haven't looked at yet. If the edge disappears out of sample, it was never there. And even a rule that survives that step still has to survive contact with live execution, where slippage, hesitation, and your own psychology show up in ways no backtest captures. In my own journal, one of the clearest findings has been that patient, confirmed entries systematically outperform impulsive entries taken in the first ten minutes of the New York session — but I only trust that finding because it held up across a large sample, against a baseline, and across multiple market conditions, not because one clean-looking equity curve told me so.

The Takeaway

A backtest isn't there to confirm what you already believe — it's there to try to break your idea and see if it survives. Write the rule first, compare it to a baseline, respect your sample size, avoid cherry-picking parameters, and validate out of sample before you validate with real money. Most "backtested strategies" fail not because backtesting doesn't work, but because the person running it was, consciously or not, looking for a reason to believe.

If you want research like this tailored to your sessions every morning, see what I offer at eviantyus.com.

This article is educational research, not financial advice. Trading involves substantial risk.

Want research like this for your sessions?

Daily, AI-assisted, tailored to your instruments.

See services →