Backtesting guide

Compare live trading performance with backtest P&L and drawdown

To compare live trading performance with backtest P&L and drawdown, align the same strategy version, market, period, position sizing, currency, and cost definitions, then reconcile trades before comparing summary metrics.

Read the practical guide

Key Takeaways

  • Match code, inputs, data period, sizing, currency, and metric definitions before comparing results.
  • Reconcile expected signals, submitted orders, fills, fees, and missed trades at the trade level.
  • Separate strategy drift from implementation, data, and execution differences.
  • Use historical-report analysis and live journaling as separate evidence streams.

Create an apples-to-apples comparison

Rerun the backtest over the exact live dates using the same code and inputs. Normalize account currency, contract multiplier, quantity, deposits, withdrawals, and realized versus unrealized P&L. Use the same drawdown definition, such as closed-equity or mark-to-market peak-to-trough, because two correct reports can disagree when their definitions differ.

Reconcile the trades before the metrics

For each expected signal, record whether an order was submitted, accepted, filled, partially filled, rejected, or missed. Compare expected and actual timestamps, prices, quantity, commission, spread, slippage, and exit reason. This explains whether the gap came from strategy logic, live data, alert or broker behavior, or the backtest fill model.

  • Match signal identifiers and strategy versions.
  • Separate missing trades from worse fills.
  • Record fees and financing consistently.

Investigate divergence without arbitrary thresholds

There is no universal percentage at which live and backtest results become unacceptable. Compare the observed gap with the strategy's expected trade variability and the documented execution model. Pause and investigate unexplained missing signals, order-state errors, risk-limit breaches, or a persistent cost gap. A journal preserves live evidence; a backtest report preserves the historical baseline.

Direct Pineify workflow

Keep the historical baseline and live record separate

Use Backtest Deep Report for a compatible TradingView Strategy Tester CSV and Trading Journal for ongoing live trade records. Compare the two only after normalizing definitions and reconciling trades.

Backtest Deep Report

Analyze the TradingView historical trade-list export used as the baseline.

Analyze the backtest CSV
Trading Journal

Organize the live trade record needed for a trade-level reconciliation.

Open Trading Journal

Boundary: Backtest Deep Report does not run or verify the original strategy. Trading Journal does not recreate the historical simulation. Neither product guarantees future performance.

Primary sources

This page is educational and does not provide investment advice. Backtests are hypothetical, depend on their data and assumptions, and do not guarantee future results. Trading can result in substantial loss.

Frequently Asked Questions