TradingView backtests: seven pitfalls that flatter results — Illustrative trading workspace, not a product or performance screenshot

AIMarkt · knowledge & practice

TradingView backtests: seven pitfalls that flatter results

TradingView’s Strategy Tester shows how rules would have performed historically. Useful for testing ideas, but a smooth curve says little if costs, execution and overfitting are ignored.

Illustrative trading workspace, not a product or performance screenshot

Ignoring fees, slippage and spread

Backtests often run with zero or low costs by default. With many trades, fees and slippage consume much of the result. Set realistic commission and slippage and compare the net outcome.

Overfitting and repainting

Tuning parameters until the past fits perfectly creates a strategy that knows history, not the future. Indicators that revise values afterwards or use future data produce signals that never existed live. Test on a period not used for optimisation.

From backtest to live

Live trading adds liquidity, latency and API outages. A demo or small live phase should follow the backtest. AIMarkt bases its rules on extended testing and analysis, but those TradingView reports remain confidential and are neither independently verified evidence nor a guarantee of future results.

Checks before proceeding

  1. Set realistic commission and slippage.
  2. Test outside the optimisation period.
  3. Review maximum drawdown, not just profit.

Worked example

400 trades at 0.1% per side cost 0.2% each, or 80% of a 1,000 USDT position cumulatively: 800 USDT in fees that can erase a 12% gross gain.

Sources and limitations

These articles use AIMarkt package terms and general execution explanations. Examples are illustrative, not customer results. No independent performance report or proof of every platform feature is published here. Consult official platform documentation and the FCA for UK rules. Translation does not establish permission to provide services in the UK.

Continue reading