Skip to content
TradingTune
Pine Script and TradingView Workflow

TradingView strategy tester

Learn how to use TradingView's strategy report to inspect a backtest and understand the assumptions behind it.

On this page

Key takeaways

  • A strategy report describes simulated trades under the conditions used in the test.
  • Record the chart, strategy inputs and testing assumptions before you compare runs.
  • Inspect individual trades as well as summary measures when investigating a result.
  • A parameter search is a starting point for further checks, not proof that a strategy will hold up.

What does the strategy tester show?

TradingView’s strategy report shows the hypothetical performance of a simulated strategy (strategy documentation, checked 2026-11-14). A backtest is a simulation that applies a strategy’s rules to past data, so the report describes what happened under the conditions of that test rather than what happened in an actual account.

The useful question is not simply whether a summary looks appealing, but which script produced it, which market data it used, and what assumptions shaped the simulated orders. A change to any of those can change what the report means, even if the strategy has the same name in your notes.

For example, a strategy might have a configurable lookback, meaning the amount of past data used in a calculation. Comparing lookbacks can help you examine how the rules respond to a change, but the comparison remains tied to the chart, period and other settings used for the test.

Start with a question you can explain in plain words, and write down the rule you expect to trigger an entry as well as the rule that closes it. That note gives you something concrete to check against the report, rather than treating a summary as an answer without examining the trades behind it.

What needs to be on the chart?

TradingView says a strategy can be added from its strategy menu or written in the Pine Editor and added to the chart (strategy documentation, checked 2026-11-14). Pine Script is the language used to write scripts for TradingView, and the Pine Editor is where you can inspect or write that code.

A strategy is different from a visual study that only draws information on a chart, because a backtest also needs rules for simulated entries and exits. TradingView’s strategy FAQ says that converting an indicator into a strategy requires a strategy declaration and order placement commands (strategy FAQ, checked 2026-11-14).

A marker on the chart does not, by itself, explain how a simulated position is opened, sized or closed, so check those rules when you review your script. Before examining the report, identify the version you intend to test, and save a note describing any changes you make to its code.

An input change and a code change answer different questions: the former changes a value supplied to the rules, while the latter may change the rules themselves. If the expected report or simulated trades are absent, check the script, chart, entry conditions and test assumptions before deciding what that absence means.

Which chart details belong in the test record?

A useful test record names the symbol, the timeframe and the period examined, because those details describe the data against which the strategy rules were evaluated. A timeframe is the span represented by each chart bar, while a bar is a summary of market data for that span.

Record the chart type alongside those details so you can distinguish a test using ordinary market prices from one using calculated chart values. TradingView cautions that simulated trades on non-standard charts use synthetic prices by default, which can make the results unrealistic (strategy documentation, checked 2026-11-14).

Synthetic prices are calculated chart values rather than necessarily the prices available in the underlying market, so consider whether they fit the question behind the test. A display may help you study a pattern without establishing that its simulated fills reflect prices available for an order.

The amount of history matters because a period that includes different market conditions can answer a different question from a narrowly chosen period. The backtest date range guide covers that choice, while your immediate task is to record the period so that later reports can be compared on a known basis.

What should you check in strategy properties?

TradingView lists capital, order size, commission, slippage and fill behavior among the settings in a strategy’s Properties tab (strategy properties, checked 2026-11-14). These are assumptions about the simulation, and they belong in the test record alongside the strategy inputs and chart details.

Order size describes how large a simulated position is, while initial capital is the starting amount used in the simulation. Together they affect the scale and context of a report, so a comparison can be hard to interpret if those assumptions differ between runs.

Commission means a trading fee, and slippage is the difference between an expected order price and its fill price. A fill is the simulated completion of an order, and the assumptions used to model it can affect the report even when entry and exit rules stay unchanged.

Keep a note of the assumptions you use and why they fit the question, instead of relying on a report without its surrounding context. If you change an assumption, treat the new report as a separate test and retain the earlier notes so you can see what changed.

The guide to modeling slippage and commission explains the cost settings in more depth, including why assumptions about costs matter when interpreting a historical simulation.

How do you read the report without relying on a summary?

TradingView describes a Metrics tab for summaries and a Trades tab that lists simulated trades in chronological order (strategy documentation, checked 2026-11-14). Read a summary as an index to questions, then use the trade list and chart to investigate the behavior behind it.

A metric is a measure that summarizes an aspect of the test, and different measures describe different parts of that behavior. A single measure cannot explain every trade or every assumption, so the backtest metrics guide explains what common measures do and do not show.

Choose a trade from the report, locate it on the chart, and compare its entry and exit with the rules you wrote down before the test. If the timing looks surprising, check the order type and fill assumptions before deciding whether the discrepancy comes from the script or your expectations.

Inspect trades from different parts of the test period rather than selecting only an example that makes the report look better or worse. If the list is sparse, the trade count guide can help you consider how much weight to place on a summary of that sample.

The aim is to explain what the simulated strategy did under the recorded conditions, including behavior that raises questions for a later review. A trade that is difficult to explain belongs in your notes, especially if it points to an assumption you had not considered.

Why can a simulated fill differ from an expected price?

An order is an instruction with conditions for entering or leaving a position, and a fill is the completion of that instruction in the simulation. The strategy may identify a condition at one point while the simulation fills the order according to separate rules, so those moments should not be treated as interchangeable.

TradingView notes that its fill settings include an option to attempt order processing on bar close (strategy properties, checked 2026-11-14). The question for your test is whether the chosen assumption matches the timing you intended to represent, not whether it makes a summary look more appealing.

When a trade looks unexpected, write down the bar where the rule became true, the order type and the bar where the report shows a fill. Check whether the difference follows from the chosen properties or from the strategy’s code, so you can separate a timing question from a question about the entry condition.

A historical bar summarizes a period rather than giving a complete account of every market event within it, which limits what you can infer from a simulated fill. The report can help you study the model, but it does not establish that an actual order would have filled at the same price or time.

How can you compare input combinations by hand?

An input is a value exposed by the strategy that you can change without rewriting its rules, while a parameter sweep is a series of tests using different input values. Before starting a sweep, record the original inputs and decide which question the comparison is meant to answer.

For a manual comparison, keep the chart, test period, strategy version and properties fixed while you change the input under study. Inspect the report and record the value alongside your observations, then repeat with the other values you planned to examine under the same conditions.

If other settings change during the process, note them instead of treating the reports as directly comparable, because more than the chosen input may explain a difference. A research note can contain the input values, test context, measures you chose to review and any unusual trades that need investigation.

The purpose of the note is to make each report identifiable after the chart has changed, including reports that did not answer the original question. TradingTune backtests your input combinations and ranks every run live, while the question you ask and your interpretation of the reports remain yours.

The parameter range guide covers how to describe the values to test, including the boundaries and spacing of the values in a search. Preserve your initial test record when you move from a manual comparison to a broader search, so the context stays visible.

TradingTune for Chrome

Stop tuning your strategy's inputs by hand.

Add to Chrome, it's free

Free tier, no API keys. A free account is required to run. Not affiliated with TradingView, Inc.

What can a parameter search tell you?

A search can organize reports produced by different input combinations, but a ranking alone cannot explain why a combination behaved as it did. The script, chart and test assumptions still determine what each report represents, so retain those details with the search record.

Before comparing runs, choose the measure you want to examine and write down why it is relevant to your question, along with what it leaves out. A summary may conceal a small trade sample, unusual fill assumptions or behavior concentrated in a narrow part of the data.

Look at nearby input values as well as the run that sits at the top of a ranking, and ask whether the surrounding reports tell a consistent story. A setting that stands apart from its neighbors may deserve closer inspection before you draw a conclusion about the strategy.

The parameter sensitivity guide explains how to examine the shape of that comparison without treating a single result as conclusive. Keep the search record separate from a later test, and describe any revision you make after seeing the reports as a new research question.

A search can help identify what to investigate, but it cannot establish how a strategy will behave on data that was not part of the search. Record the limits of the test alongside the observations, especially when the reason for a difference between runs remains unclear.

Why might historical and realtime behavior differ?

TradingView defines repainting as script behavior that causes historical and realtime calculations or plots to behave differently (repainting documentation, checked 2026-11-14). Realtime data describes the current, still-developing bar, while historical data describes bars that have already closed.

A value observed while a bar is forming may change before that bar closes, so an event seen during the bar may not match a later historical view. Repainting is a broad term, and the useful question is which behavior occurs in the script and whether that behavior matters to the test.

Review the strategy’s calculation timing and any data it requests from another timeframe, keeping a note of the assumptions you can verify. If you can inspect the code, look for rules that use an unfinished bar or rely on information that would not have been available at the simulated decision point.

If you cannot inspect the code, record that limit instead of assuming that the historical report explains every detail of the calculation. Do not resolve an unexplained difference by changing inputs until the report looks familiar; first consider whether the data, calculation timing or order assumptions could explain it.

The article on lookahead bias discusses the separate problem of using future information in a historical test, which can make a report misleading even when the displayed trades appear orderly.

What should you do after reviewing a report?

Save a clear account of what you tested and what remains uncertain, including the strategy version, chart context, inputs, properties and period examined. Add observations about individual trades when they explain a question that the summary could not answer, or when the cause of a fill remains unclear.

If you selected inputs using a period of data, a later check can use data held apart from that selection. This is called an out-of-sample test: a test on data not used to choose the settings, intended to examine the selected rules under a different slice of history.

Decide how the later period will be used before looking at its results, rather than repeatedly changing the rules after inspecting that same held-out data. Repeated changes weaken its role as a separate check, because the observations can influence the next version of the strategy.

The in-sample and out-of-sample guide explains the split and its limits, including why a later historical test cannot certify future behavior. Keep the search notes and the later test notes distinct so you can tell which information was available when each choice was made.

Finally, distinguish a finding from an open question: a finding describes what the simulation showed under recorded assumptions, while an open question names what you could not establish. Missing data, a fill convention or code you have not inspected can all belong in that second category, making the next review easier to interpret.

Sources

TradingTune for Chrome

Stop tuning your strategy's inputs by hand.

TradingTune runs systematic parameter searches on your own TradingView strategy, right inside the chart page. You keep the strategy, you read the results.

Free tier, no API keys. A free account is required to run. Not affiliated with TradingView, Inc.

Share this post