Short answer: TradingView exports full backtest trade history as a CSV from the Strategy Tester (‘List of Trades’ tab). That CSV is the starting point for catching overfitting, uncounted slippage, and other errors before trading live — a dedicated backtest auditor exists precisely because eyeballing the equity curve isn’t enough.
The TradingView backtest is only step one
Thousands of algo traders use TradingView’s Strategy Tester as the testing ground for their Pine Script strategies. The tool isn’t the problem — what happens (or doesn’t happen) to the results after seeing an equity curve that goes up and to the right is.
A clean equity curve in the Strategy Tester guarantees nothing about future performance. The exported trade history itself holds the clues why: too few trades to be statistically meaningful, concentration in a single market regime, or an assumed commission that doesn’t match the real fee on the exchange you’ll actually trade on.
What to check in the exported CSV before trusting the result
The ‘List of Trades’ export includes, trade by trade: entry and exit date, price, position size, gross P&L, and commission applied. With that you can already compute metrics the Strategy Tester summary doesn’t show by default — a Sharpe ratio adjusted to the target exchange’s real fee, or the distribution of winning vs. losing trade duration.
Data gaps in price or time coverage matter too: if the backtest ran over a series with holes in it, the result can be inflated without it being obvious from the chart alone.
That’s why we audit the CSV, not the screenshot
TGL’s backtest auditor takes exactly that file — TradingView’s native export, no pre-processing — and scans it for the patterns that usually inflate a result artificially: overfitting to a specific date range, missing slippage, and signs of look-ahead bias in the strategy logic.
The goal isn’t to replace a trader’s judgment, it’s to give a second, objective opinion before moving a strategy to live capital — the same transparency principle behind how we document our own datasets: better to catch a flaw early than discover one with real money on the line.
TradingView as a data source, not just a chart
Beyond a single backtest, TradingView is also where most algo traders prototype indicators in Pine Script before shipping them to a live bot. If you’re already using the platform for that, it’s worth knowing the rest of its ecosystem — plans, alerts, and the Strategy Tester with extended data — before duplicating that infrastructure elsewhere.