How to backtest sweeps honestly with a small sample
Everyone has a few screenshots of perfect sweeps. That is not a backtest, it is a highlight reel. To test the idea honestly, write down the exact rules first: what level counts, what timeframe, what confirmation, where the stop and target go. Then scroll through the chart bar by bar, hiding the future, and record every occurrence, including the ugly ones. Aim for at least fifty samples before drawing any conclusion, and split them into two groups so you can check whether the result holds on data you did not use to shape the rules. Track win rate, average R, and how many trades you skipped because they were unclear. If the rules need judgment calls, note how often you made them. Be suspicious if your results look too good, because hindsight bias creeps into manual testing easily. A modest, repeatable edge that survives both halves of the sample is worth more than a spectacular result you cannot reproduce live.
How to backtest sweeps honestly with a small sample
How to backtest sweeps honestly with a small sample
It’s Fairman 
Re: How to backtest sweeps honestly with a small sample
Splitting the sample into two halves is the part most people skip, and it's the most useful. One extra step: shuffle which half you build on. If you shape the rules on the older half and test on the newer one, then do it the other way round, you get a sense of whether the result depends on one market period. Sweeps behave differently in trending and ranging months, so a result that only shows up in one half is a warning. Fifty samples is a starting point too. Split by session or pair, the groups get small fast, so read them loosely.
It’s Fairman 
Re: How to backtest sweeps honestly with a small sample
I'd also log the trades you would have been unsure about in real time as their own group. In a manual backtest it's easy to mark an ambiguous sweep as valid when you can see the result, even with the future hidden, because the shape still tips you off. Keeping a separate tag for borderline cases lets you check whether the edge comes from the clean examples or from the ones you'd struggle to call live. If the borderline group is what's carrying the results, that's a sign the rules need tightening before any of it goes near a real account.
It’s Fairman 
Re: How to backtest sweeps honestly with a small sample
One more check for small samples: count how many different weeks the trades come from. Twenty sweep trades that happened across three weeks in one volatile month tell you a lot less than twenty spread over six months. Clusters happen because market conditions cluster, and a strategy can look great just because the sample is mostly from one kind of market. If most of the trades come from a narrow window, I'd treat the result as a description of that window rather than of the setup in general. A quick calendar heatmap of trade dates makes the clustering obvious at a glance.
It’s Fairman 
-
FXS Prop Desk
- Posts: 1692
- Joined: Wed Oct 07, 2026 9:52 am
Re: How to backtest sweeps honestly with a small sample
Writing the rules first is the step that turns screenshots into a test. Scrolling bar by bar with the right side of the chart hidden also matters, because seeing what came next makes it very hard to judge a setup honestly.
With a small sample, it helps to report the result as a range rather than a single number. Twenty trades with a 60 percent win rate could easily come from a true 40 or 75 percent setup. That keeps expectations realistic until more trades are collected.
With a small sample, it helps to report the result as a range rather than a single number. Twenty trades with a 60 percent win rate could easily come from a true 40 or 75 percent setup. That keeps expectations realistic until more trades are collected.
FXS Official Team | The Idea Lab & Strategy
Re: How to backtest sweeps honestly with a small sample
Defining the sweep in writing before you start is the bit I'd stress most. How far past the level does price need to go? Does it need to close back inside, and within how many bars? If the definition is loose, you'll unconsciously count the clean examples and drop the messy ones, and a small sample can't absorb that kind of bias. With a written definition, someone else could go through the same charts and find the same trades. If they couldn't, the backtest is partly measuring your judgement on the day rather than the setup.
It’s Fairman 