A strategy video usually shows you a few clean winners. A backtest shows you what happens over the next fifty or five hundred trades, including the ugly ones. Over the last year I've tested more than 35 strategies from YouTube this way, and the process below is what I've settled on.

Step 1: Write the rules down in plain sentences

Before I look at a single trade, I write the strategy out the way you'd explain it to a friend:

  • Market and time. Which market (NQ, MNQ, ES, gold, EURUSD), which chart timeframe, and which hours of the day.
  • Setup. What has to happen before a trade is allowed. For an opening range breakout, that's "mark the high and low of the first 15 minutes after the New York open".
  • Entry. The exact event that puts you in. "A 5-minute candle closes above the range" is a rule. "Price shows strength" is not.
  • Stop and target. Where you're wrong, and where you take profit.
  • When you don't trade. News days, ranges that are too wide, a second trade after a loss.

This step catches the biggest problem with YouTube strategies: most of them have a judgment call hiding in them. When a video leaves something open, I pick one version, write down what I picked, and keep it fixed for the whole test. The judgment calls get their own section on the result page so you can see where my choice might differ from the creator's.

Step 2: Choose replay or code

There are two ways to run the trades, and I use both.

Manual replay. I scroll the chart back in time, hide everything to the right, and step forward one candle at a time, taking trades as the rules say. This is the right tool when the strategy needs your eyes, like spotting a fair value gap or a liquidity sweep. The weakness is size: a replay is usually 20 to 150 trades, because each one takes time.

Coded backtest. I write the rules in Python and run them over years of 1-minute futures data. A coded test can cover 800 or 1,300 trades in seconds, and it can't cheat by "seeing" the right setup. The weakness is that a computer can only follow rules that are written exactly, so any judgment in the strategy has to be turned into a fixed rule first.

The best tests do both. For example, the QuantCrawler ORB passed a short replay challenge, but the 10-year coded version barely made more than it lost. Neither result alone tells the full story.

Step 3: Add the costs

A backtest that leaves out costs looks better than real trading. In my coded tests I charge commission on every contract and add slippage: usually one tick against me on entries and more on stop-outs, because stops fill at worse prices in fast markets. In the Justin Chuk ORB test that meant $2 per contract round trip, 1 tick of slippage on entries and time exits, and 2 ticks on stops.

Costs matter most for strategies with small targets. A scalping strategy that makes 4 points a trade can lose a big share of its edge to fees and slippage.

Step 4: Run it through prop firm rules

Most people watching these videos want to pass a prop firm challenge, and a strategy can make money overall and still fail one. So after the plain backtest, I run the trades through the actual rules of a firm:

  • the profit target (often $3,000 on a 50K account),
  • the maximum drawdown and how it's measured (end of day or intraday, trailing or fixed),
  • the daily loss limit, if there is one,
  • the consistency rule, which caps how much of your profit can come from one day.

For coded tests I start a new simulated challenge on every possible start date, so the result is a pass rate, not one lucky run. That's how the Justin Chuk ORB could make about $12,500 over 7 years with no losing year and still pass only about 27% of challenges at the risk size he uses. My guide to prop firm drawdown rules explains why.

Step 5: Publish the whole thing

Every result page shows:

  • The verdict first, in one or two sentences.
  • The sample size. Twenty trades and eight hundred trades are not the same kind of evidence.
  • The worst stretch. The biggest drawdown and the longest losing streak, because that's what decides whether you'd actually stick with it.
  • The trade log, where I have one, so you can check my numbers.
  • Where the numbers come from, including any place the video's numbers don't add up.

What a backtest can't tell you

A backtest is hypothetical. It doesn't feel fear, it never misses an entry because it was making coffee, and it can't know what the market does next year. If you test enough versions of a strategy, one of them will look great by luck alone. So treat a good backtest as "worth trying on a simulator", not "guaranteed to work".

If you want to test your own numbers, the prop firm pass simulator takes a win rate and a reward-to-risk and shows how often that passes a 50K challenge. And if there's a strategy you want me to test, send it in.