Strategy Tester reports a simulation

TradingView Strategy Tester applies coded order rules to historical chart data under selected assumptions. It can summarize net profit, drawdown, number of trades, win rate, average trade, and other statistics. These numbers describe the simulation, not an actual customer account. Historical data, bar construction, order timing, costs, and script logic all shape the report.

A strategy can appear precise because every trade is listed, but the precision belongs to the model. Actual orders face bid and ask spreads, slippage, queue position, latency, partial fills, outages, and user intervention. Read the report as a research instrument. It cannot establish that the same results were achievable or will occur in a future market.

Inspect Properties before the overview

Begin with initial capital, order size, pyramiding, commission, slippage, recalculation settings, and date range. Confirm the symbol, source, timeframe, session, and candle type. A strategy tested on synthetic bars may use values that were not executable. A continuous futures contract can also differ from the contract actually traded during each period.

MtnSkyAlgo Pre-Alpha Boss and Post-Alpha Hero have stated one-hour futures configurations. Changing the instrument or timeframe changes the tested model. Use regular candlesticks and realistic costs. If Bar Magnifier is available, understand what lower-timeframe data it uses and whether sufficient history exists.

Read more than net profit and win rate

Net profit without drawdown and exposure can hide a difficult path. Win rate without average win and loss can be misleading. Review maximum drawdown, profit factor, average trade, largest loss, number of trades, and how results change over time. Determine whether a small number of outliers produce most of the return.

Inspect the list of trades and the equity curve. Look for long flat periods, sudden clusters, and sensitivity to a particular date range. Separate in-sample data used to develop or tune the strategy from unseen data used for evaluation. Repeatedly changing rules until the same history looks attractive increases the risk of overfitting.

Stress the assumptions

Increase commission and slippage, shift the date range, and compare nearby parameter values. A result that disappears after a small realistic cost increase may be fragile. Test multiple regimes, including volatility changes and sideways periods. Avoid selecting the best combination from hundreds of trials without accounting for how much searching occurred.

Forward observation or paper testing can reveal timing, alert, and workflow issues that historical calculations do not show. Preserve a version of the strategy and settings before the observation begins. Do not continue retuning the same sample while describing it as out-of-sample evidence.

Use a responsible review checklist

Strategy Tester can help compare coded hypotheses consistently, but it cannot remove market risk. Every displayed result should be accompanied by the full simulated-performance limitations and the assumptions needed to reproduce it.

  • Confirm symbol, timeframe, candle type, and data source.
  • Review order size, commission, slippage, and recalculation.
  • Inspect drawdown, trade distribution, and exposure.
  • Separate development data from unseen evaluation.
  • Stress costs, dates, and nearby settings.
  • Forward observe without continual retuning.
  • Never present simulated results as an actual performance record.