A strong in-sample Sharpe often reflects search bias, not alpha. The papers below cover backtest overfitting, adjusted significance tests, and open replication — the minimum reading before you trust a new strategy pipeline.

Overfitting and significance

When you test many variants, the best backtest is almost always lucky. Bailey and Lopez de Prado quantify this; Harvey and Liu extend the logic to published factor discoveries.

The Probability of Backtest Overfitting

CSCV and PBO metrics for estimating how much of a backtest edge comes from selection bias rather than signal.

PDF

The Deflated Sharpe Ratio

Adjusts Sharpe for non-normality, sample length, and the number of trials run before picking a strategy.

PDF

The Minimum Backtest Length

Minimum sample length needed for a Sharpe to be statistically distinguishable from noise given trial count and skew. Pairs with the deflated Sharpe entry above.

PDF

Replication and open data

Modern factor and signal research should be reproducible. Chen and Zimmermann's open-source asset pricing project is the benchmark for checking whether a backtest survives clean data and code.

Recent applied work

Before you ship

  • Report how many variants you tested before picking the winner
  • Use purged or walk-forward validation, not a single random split
  • Replicate on an independent data vendor when possible
  • Apply transaction costs and capacity constraints early

Pair this list with our ML signals reading list for validation methodology in production pipelines.