TradingView Strategy Tester · Strategy Report · Deep Backtesting · Bar Magnifier
TradingView Strategy Tester is one of the best places to challenge a trading idea before risking real money — but a profitable backtest is only useful if you understand how TradingView produced it.
TradingView’s current interface increasingly refers to the results area as the Strategy Report. It now gives you much more than a headline net-profit number: performance charts, trade statistics, risk/performance ratios, detailed trade records, buy-and-hold comparison, commissions, run-up and drawdown analysis, Deep Backtesting, and more realistic order-fill tools such as Bar Magnifier.
This August 2026 guide shows you how to use the Strategy Tester / Strategy Report from the beginning, how to read the current tabs, how Deep Backtesting differs from regular chart backtesting, how commissions and slippage change results, how the broker emulator fills orders, and how to avoid the most common forms of backtest self-deception.
New to TradingView? TradingView currently says eligible new users referred through its Partner Program receive a $15 discount coupon toward a new TradingView plan. Eligibility and offer terms are controlled by TradingView.
Key Takeaways
- TradingView calls the current results workspace the Strategy Report. You still reach it by adding a strategy to a Superchart.
- Only one strategy can run on a chart at a time. You can use built-in strategies, Community strategies, or your own Pine Script strategies.
- Do not judge a strategy from Net P&L alone. Read drawdown, profit factor, trade count, average win/loss, equity behavior, costs, and trade-level results together.
- Deep Backtesting is available on Premium and higher plans. It can test data beyond what is currently loaded on the chart, with up to 2 million bars and 1 million trades per calculation.
- Deep Backtesting trades do not appear on the chart. They exist only inside the Strategy Report, so chart trades and Deep Backtesting results can differ.
- Bar Magnifier uses lower-timeframe data to improve historical order-fill precision. It is especially useful when stop and limit orders depend on what happened inside a bar.
- TradingView strategies can model commissions, slippage, margin, order sizing, pyramiding, limit-order verification, and recalculation behavior.
- Heikin Ashi and other non-standard chart assumptions can distort fills. TradingView provides a standard-OHLC fill option for Heikin Ashi strategy testing.
- A backtest is a research model, not proof of future performance. Robustness matters more than a perfect historical screenshot.
Table of Contents
- What Is TradingView Strategy Tester?
- Strategy vs Indicator
- How to Open Strategy Report
- Current Strategy Report Tabs
- How to Read Overview
- How to Read Performance
- Trades Analysis
- Risk/Performance Ratios
- How to Use List of Trades
- Strategy Properties That Matter
- Commission and Slippage
- How TradingView Fills Historical Orders
- Bar Magnifier
- Deep Backtesting
- Why Deep and Regular Results Can Differ
- Heikin Ashi and Standard OHLC
- Backtesting vs Forward Testing
- How to Export Strategy Data
- How to Test Robustness
- How to Avoid Overfitting
- A Better Testing Workflow
- Common Strategy Tester Mistakes
- FAQ
What Is TradingView Strategy Tester?
TradingView Strategy Tester is the platform’s historical strategy-testing workflow. A Pine Script strategy creates simulated orders on historical bars, and TradingView turns those orders into a Strategy Report.
The report helps answer questions such as:
- Did the rules make or lose money during the test?
- How large were the drawdowns?
- How many trades produced the result?
- Were profits spread across many trades or driven by one outlier?
- Did long and short trades behave differently?
- Did the strategy outperform simply buying and holding the asset?
- How much did commissions reduce the result?
- How did individual trades behave before they closed?
- Does the idea still work when you change the market, timeframe, costs, or test period?
The important word is historical. Strategy Tester does not predict what will happen next. It measures how a defined ruleset behaved under TradingView’s historical data and execution assumptions.
Best mindset: use Strategy Tester to find reasons your idea may be weaker than you think. If you use backtesting only to prove yourself right, optimization can manufacture impressive results surprisingly quickly.
Do You Need a Paid TradingView Plan for Strategy Testing?
No — not for normal strategy backtesting. TradingView’s current plan table includes Pine Script and backtesting for trading strategies on Basic, so beginners can learn the workflow before paying. Premium becomes materially different when you need deeper history through Deep Backtesting or more precise intrabar fill modeling through Bar Magnifier.
| Testing Need | Plan Decision | Why |
|---|---|---|
| Learn Strategy Report and run normal backtests | Start with Basic | Regular Pine strategy backtesting is available without starting on Premium |
| More chart history and wider platform capacity | Compare paid plans | Historical bars and other platform limits increase by tier |
| Deep Backtesting | Premium or Ultimate | Tests deeper stored history, up to 2 million bars and 1 million trades per calculation |
| Bar Magnifier | Premium or Ultimate | Uses lower-timeframe data for more precise historical order-fill modeling |
Strategy vs Indicator: What’s the Difference?
| Type | What It Does | Strategy Report? |
|---|---|---|
| Indicator | Calculates and displays signals, lines, values, bands, labels, or other chart information | No automatic strategy report |
| Strategy | Calculates logic and simulates orders such as entries and exits | Yes |
An indicator can display perfect-looking buy and sell arrows and still tell you almost nothing about historical performance. To get Strategy Report metrics, the script needs strategy logic that generates simulated orders.
If you want to write or edit those rules yourself, our updated TradingView Pine Editor guide now uses Pine Script v6 and covers strategy code, commissions, slippage, debugging, and migration from older v5 scripts.
How to Open TradingView Strategy Report
- Open a TradingView Superchart.
- Click Indicators in the top toolbar or use the / shortcut.
- Choose a strategy from Technicals → Strategies, Community, or your own saved scripts.
- TradingView adds the strategy to the chart and opens the Strategy Report at the bottom.
- Review the default result before changing inputs or strategy properties.
Only one strategy can run on a chart at a time. That is useful because the report always belongs to one defined strategy rather than mixing results from several systems.
Do not optimize immediately. First record the original settings, date range, symbol, timeframe, and result. Otherwise you lose the baseline you need for comparison.
Current TradingView Strategy Report Tabs
The current Strategy Report separates the result into several areas so you can move from headline performance to detailed behavior.
| Tab / Area | What It Answers |
|---|---|
| Overview | What did the strategy do overall, and what did the equity path look like? |
| Performance | How much did it make or lose, what were the costs, and how severe were run-ups/drawdowns? |
| Trades analysis | What did the average winner, loser, trade duration, and trade distribution look like? |
| Risk/performance ratios | How do returns compare with risk and downside volatility? |
| List of trades | What exactly happened in every simulated trade? |
The names and layout can evolve, so focus on the analytical job rather than memorizing where each card appears. Your goal is to explain how the final result was produced.
How to Read the Strategy Report Overview
Overview is the fastest health check. TradingView currently highlights metrics and charts including Total P&L, Max equity drawdown, Total trades, Profitable trades, Profit factor, Buy & Hold comparison, and trade run-up/drawdown behavior.
| Metric | What It Means | Beginner Question |
|---|---|---|
| Total P&L / Net P&L | Overall result after the modeled strategy activity | Is the result still positive after realistic costs? |
| Max equity drawdown | Largest peak-to-trough equity decline | Could I realistically tolerate this? |
| Total trades | Number of completed trades in the sample | Is this enough evidence to mean anything? |
| Percent profitable | Share of trades that closed as winners | Does the win rate fit the average win/loss relationship? |
| Profit factor | Gross profit divided by gross loss | Are gains meaningfully larger than aggregate losses? |
| Buy & Hold | Passive benchmark over the period | Did active rules actually add value? |
The performance chart is especially useful because a final number hides the path. A strategy that reaches the same final profit through a smooth, diversified equity curve is very different from one that spends years underwater before one giant winning trade rescues the result.
How to Read the Performance Section
The current Performance section goes deeper into returns, benchmarking, and equity behavior. It can include metrics such as Net P&L, Gross profit, Gross loss, Commission paid, Expected payoff, Buy & Hold P&L, strategy outperformance, Sharpe ratio, Sortino ratio, run-up, and drawdown measurements.
TradingView also separates all-trade, long-trade, and short-trade statistics where relevant. This is important because one direction can hide the weakness of the other.
| Performance Question | Why It Matters |
|---|---|
| How much gross profit was generated? | Shows total winning contribution before subtracting losses and modeled costs |
| How large was gross loss? | Shows how much losing trades gave back |
| How much commission was paid? | Shows the direct transaction-cost burden of the strategy |
| Did the strategy beat Buy & Hold? | Tests whether active complexity produced value versus passive exposure |
| How deep and long were drawdowns? | Shows whether the equity path was realistically tolerable |
| Are long and short results similar? | Reveals whether one side of the strategy is carrying the system |
Commission paid is already reflected in Net P&L when commission is configured. Slippage is a separate execution assumption and is not simply another commission line item.
How to Use Trades Analysis
Trades analysis tells you what the typical trade looks like instead of only showing the final equity result.
- Total trades and open trades
- Winning and losing trades
- Percent profitable
- Average P&L
- Average winning trade
- Average losing trade
- Average win / average loss ratio
- Largest winner and loser
- Average bars per trade
- Average bars in winners and losers
This section is where the win-rate myth becomes obvious. A strategy can win only 40% of the time and still work if the average winner is much larger than the average loser. A strategy can also win 80% of the time and still fail if the occasional loss is enormous.
Look for dependence on outliers. If one or two giant winners contribute most of the gross profit, test what happens when those trades disappear or occur later than expected.
Risk/Performance Ratios: Sharpe, Sortino and Profit Factor
Risk-adjusted metrics help answer a different question from Net P&L: how much return did the strategy produce relative to instability or downside?
| Metric | Simple Interpretation | Do Not Assume |
|---|---|---|
| Sharpe ratio | Return relative to overall return variability | A high Sharpe guarantees future stability |
| Sortino ratio | Return relative to downside deviation | It replaces drawdown analysis |
| Profit factor | Gross profit relative to gross loss | One high value is enough without a reasonable sample |
| Margin calls | Shows whether strategy leverage caused forced liquidations | Leverage is harmless because historical net profit was positive |
No single risk ratio proves robustness. Use these metrics as additional evidence alongside drawdown, trade distribution, realistic costs, and the equity path.
How to Use the List of Trades Tab
The List of Trades is where you stop treating the backtest as a summary and start auditing actual behavior.
The current trade list can include details such as trade number, type, date/time, signal, execution price, position size, Net P&L, favorable excursion, adverse excursion, and cumulative P&L.
| Audit Check | What You Are Looking For |
|---|---|
| Entries and exits | Do orders occur where the written rules say they should? |
| Loss clusters | Does the strategy fail repeatedly in a specific market regime? |
| Trade duration | Does holding time match the intended style? |
| Outlier winners | Is total profit dependent on a tiny number of unusual trades? |
| Outlier losses | Can one event erase months of normal profits? |
| Position size | Is the strategy trading an amount you could realistically execute? |
| Execution price | Do historical fills look plausible? |
If you only have time to inspect one area after the headline report, inspect the trade list. It often reveals bugs, unrealistic fills, overtrading, and regime dependence faster than any summary metric.
Strategy Properties That Matter Most
TradingView’s strategy properties control how the broker emulator and performance calculations behave. Ignoring them is one of the fastest ways to produce unrealistic results.
| Property | What It Controls | Why It Matters |
|---|---|---|
| Initial Capital | Starting account balance | Position feasibility and percentage calculations |
| Base Currency | Currency used for report calculations | Keeps P&L and risk metrics interpretable |
| Order Size | Fixed quantity, cash amount, or % of equity | Changes capital usage and compounding |
| Pyramiding | Number of same-direction entries allowed with strategy.entry() | Can increase exposure dramatically |
| Commission | Modeled fees on executed orders | Can destroy high-turnover strategies |
| Verify Price for Limit Orders | Makes historical limit fills stricter | Reduces overly easy historical limit fills |
| Slippage | Tick adjustment to market/stop fills | Models execution worse than ideal price |
| Margin | Capital requirement for long/short positions | Controls leverage and possible margin calls |
| Recalculate | When the strategy recalculates | Can change live behavior and repaint risk |
| Fill orders | Bar Magnifier, bar-close behavior, standard OHLC | Changes execution assumptions |
These settings can also be defined in Pine through the strategy() declaration. The advantage of coding them is that the assumptions travel with the script instead of depending on someone remembering to configure the Properties tab correctly.
Commission and Slippage: Make the Backtest Less Perfect
TradingView can model several commission styles, including percentage of transaction value, cash per contract, and cash per order. Commission is applied to entries and exits.
Slippage is configured separately in ticks and adjusts modeled fills for market and stop orders. It can help approximate spread and execution friction, especially in faster or less liquid markets.
Why Costs Matter So Much
A strategy making 10 trades per year may tolerate small cost assumptions. A strategy making hundreds or thousands of trades can have a completely different edge after fees and slippage are applied.
A useful stress test is to make costs slightly worse than your optimistic estimate. If a small deterioration turns a strong backtest into a weak one, the strategy may have very little margin for real-world execution error.
How TradingView Fills Historical Orders
TradingView strategies use a broker emulator. Historical bars usually provide OHLC information, not a perfect tick-by-tick record of the path price took inside every bar. That means the emulator needs assumptions about order execution.
This becomes especially important when your strategy can enter and exit inside the same candle, uses stop or limit orders, or depends on precise intrabar sequencing.
A backtest price touching your order level does not automatically mean a real trade would have filled exactly that way. Execution assumptions are part of the model.
TradingView provides tools such as stricter limit-order verification, modeled slippage, Bar Magnifier, and standard-OHLC fills on Heikin Ashi charts to reduce some obvious sources of unrealistic execution.
What Is Bar Magnifier?
Bar Magnifier improves historical order-fill precision by using lower-timeframe data to understand price movement inside a higher-timeframe bar.
Without that detail, the broker emulator must infer an intrabar path from the chart bar. With Bar Magnifier enabled, it can use lower-interval bars to determine more accurately whether an entry, stop, or exit could have happened and in which order.
This matters when a single higher-timeframe bar touches both an entry and an exit level. The order of those movements can completely change the simulated trade.
| Chart Timeframe | Example Lower Interval Used by Bar Magnifier |
|---|---|
| 1 minute | 10 seconds |
| 5 minutes | 30 seconds |
| 15 minutes | 2 minutes |
| 30 minutes | 5 minutes |
| 60 minutes | 10 minutes |
| 4 hours | 30 minutes |
| 1 day | 60 minutes |
| 1 week | 1 day |
Bar Magnifier is available on Premium and higher tiers. TradingView currently limits the lower-timeframe history requested for the magnifier, so very early chart history may not always receive the same intrabar detail as recent history.
Premium upgrade test: do not upgrade only because Bar Magnifier sounds more advanced. It is most useful when intrabar order sequence materially changes the research question — especially with stop and limit orders that can interact inside the same higher-timeframe bar.
New-user partner benefit: TradingView currently says eligible new users referred through its Partner Program receive a $15 discount coupon toward a new TradingView plan. TradingView controls eligibility, availability, and offer terms.
What Is TradingView Deep Backtesting?
Regular Strategy Report calculations are tied to the historical bars currently available in the chart session. Deep Backtesting is a separate report mode that can calculate a strategy over much deeper stored history for the selected symbol.
TradingView currently makes Deep Backtesting available on Premium and higher plans. A calculation can use up to 2 million bars and produce up to 1 million trades.
- Add a strategy to the chart.
- Open Strategy Report.
- Select the date range you want to test.
- Deep Backtesting starts for the selected historical range.
- When strategy settings change, update the report to recalculate.
- Return to the normal chart-session calculation when you are finished.
The amount of actual historical coverage still depends on the symbol and interval. Daily data can extend much further than some intraday histories because exchanges and data feeds do not provide infinite low-timeframe history.
Critical difference: Deep Backtesting trades are not plotted on your chart. Deep results live inside Strategy Report. The trade markers visible on the chart belong to the regular chart-session calculation.
Why Can Deep Backtesting and Regular Results Be Different?
Seeing different results does not automatically mean one mode is broken. The calculations can begin from different available histories, and the starting point can affect indicators, strategy state, compounding, and trade sequencing.
| Regular Chart Backtest | Deep Backtesting |
|---|---|
| Uses bars available in the chart session | Can use deeper historical storage |
| Trade markers appear on the chart | Deep trades appear only in Strategy Report |
| Starting history depends on loaded chart data | You can choose a historical test range |
| Useful for chart-level inspection | Useful for larger historical samples |
For this reason, compare modes deliberately. Do not look at a Deep Backtesting report and then try to explain every Deep trade by clicking chart markers from regular mode — they are not necessarily the same trade set.
Heikin Ashi and Standard OHLC Strategy Fills
Non-standard chart types can create another testing trap. Heikin Ashi candles use transformed prices, so a strategy filling orders directly at those synthetic chart values can produce fills that do not correspond to actual market OHLC prices.
TradingView provides a Using standard OHLC option for Heikin Ashi strategy fills. This forces the broker emulator to use actual market OHLC prices rather than the synthetic Heikin Ashi values for order execution.
If you backtest on Heikin Ashi: understand whether the chart is only being used for signal logic or whether synthetic prices are also affecting modeled fills. Those are very different assumptions.
Backtesting vs Forward Testing
Backtesting recreates strategy behavior on historical data. Forward testing observes the strategy as new real-time bars arrive.
A strategy can look excellent historically and behave differently in forward testing because real-time bars update, spreads and slippage change, market regimes shift, and some recalculation settings behave differently on live bars.
| Backtesting | Forward Testing |
|---|---|
| Historical sample | New live market data |
| Fast to test many years | Slow because time must pass |
| Easy to over-optimize | Harder to change the past after seeing results |
| Execution is simulated | Still simulated unless paired with a separate execution workflow |
| Useful for idea rejection and historical structure | Useful for checking whether behavior survives unseen data |
Paper Trading and Bar Replay add two more useful layers. Paper Trading lets you practice a live-style process with virtual funds, while Bar Replay lets you move through historical price action without seeing the future candles in advance.
Use our TradingView Bar Replay guide if you want to combine systematic results with discretionary historical practice.
How to Export TradingView Strategy Data
TradingView lets you export strategy-report data so you can compare tests outside the chart interface.
Export becomes useful when you want to:
- compare the same strategy across several symbols
- compare different timeframes
- track parameter changes systematically
- audit large trade samples in a spreadsheet
- build your own robustness or distribution analysis
Pine strategies run on one symbol at a time. If you want a true multi-market comparison, one practical workflow is to test each symbol separately, export the results, and compare them in a spreadsheet instead of pretending one excellent ticker proves universality.
How to Test Strategy Robustness
A robust strategy should survive reasonable changes without collapsing immediately.
| Robustness Test | What You Want to Learn |
|---|---|
| Different symbols | Does the logic depend on one unusually favorable market? |
| Different timeframes | Is the result tied to one exact bar structure? |
| Different date ranges | Does it survive more than one market regime? |
| Slightly worse commission | Is the edge large enough to survive costs? |
| Higher slippage | Does execution sensitivity destroy performance? |
| Nearby input values | Is there a stable range or one magical parameter? |
| Long vs short separately | Is one direction carrying the strategy? |
| Remove the best trade | Is the entire result dependent on one outlier? |
ChartWiseHub’s Backtest Quality Checker is designed for exactly this stage: challenge the quality of the result before you become attached to it.
You can also use our Strategy Tester Metrics Interpreter if you want help turning report metrics into a structured review.
How to Optimize Without Overfitting
Optimization is the process of changing strategy parameters and comparing results. Overfitting happens when the strategy becomes too specifically tuned to the historical sample you already saw.
The danger is easy to understand: if you test enough combinations, eventually something will look impressive by chance.
Better Optimization
- Change one important input at a time
- Prefer stable parameter ranges
- Keep costs realistic
- Validate on unseen periods
- Test other markets
- Record every meaningful test
Overfitting Warning Signs
- One exact setting is dramatically better than nearby values
- One ticker looks perfect while similar markets fail
- Performance collapses after modest costs
- Removing one giant winner ruins the result
- You keep changing rules after every losing period
- You optimize and validate on the same data
Better question: do not ask “Which setting gives the highest historical profit?” Ask “Which reasonable range still works when the market, costs, and test period change?”
A Better TradingView Strategy Testing Workflow
| Step | What to Do | Why |
|---|---|---|
| 1 | Write the trading rule in plain English | Make the idea testable before coding it |
| 2 | Run the simplest working strategy | Create a clean baseline |
| 3 | Set realistic capital and order size | Make simulated trades feasible |
| 4 | Add commissions and slippage | Reduce obvious historical optimism |
| 5 | Read Overview and Performance | Understand return and drawdown together |
| 6 | Audit List of Trades | Verify the strategy behaves as intended |
| 7 | Use Bar Magnifier where execution sequence matters | Improve intrabar fill assumptions |
| 8 | Use Deep Backtesting if available and useful | Expand the historical sample |
| 9 | Test other periods, symbols, and nearby settings | Challenge robustness |
| 10 | Forward test before considering real capital | Observe behavior on unseen data |
This workflow intentionally makes the test harder to pass. That is a feature. Weak ideas are cheaper to discover in research than after deployment.
Common TradingView Strategy Tester Mistakes
Judging Net Profit Alone
A large profit can hide unacceptable drawdown, tiny trade samples, or one giant outlier winner.
Ignoring Costs
Commission and slippage can completely change active strategies with small per-trade edges.
Assuming Every Historical Fill Is Realistic
Historical bars do not automatically reveal the exact path price followed inside every candle.
Confusing Deep Trades with Chart Trades
Deep Backtesting results are report-only. The chart continues to display regular-session strategy trades.
Optimizing One Symbol Forever
Eventually you are fitting the quirks of that exact history rather than testing a reusable idea.
Using Synthetic Chart Prices Carelessly
Heikin Ashi and other transformed charts require extra thought about signal prices versus realistic execution prices.
Make the Backtest More Realistic Before You Make It More Profitable
Use realistic costs, inspect individual trades, challenge execution assumptions, test more than one market regime, and use Deep Backtesting or Bar Magnifier when those tools genuinely answer a research question.
Plan decision: stay on Free if regular backtesting already answers the question. Compare Premium or Ultimate when deeper stored history or intrabar fill detail has become a real research requirement.
Conclusion: Use Strategy Tester to Challenge Your Idea
TradingView Strategy Tester / Strategy Report is far more useful than a simple “profit or loss” calculator. The current report gives you a structured view of returns, drawdowns, trade behavior, risk ratios, individual executions, commissions, benchmarking, and historical robustness.
Premium and higher plans extend that workflow with Deep Backtesting and Bar Magnifier. Those tools can improve historical depth and fill precision, but they do not remove the basic limitations of backtesting: historical data is still historical, execution is still modeled, and optimization can still overfit.
The strongest habit is simple: make your test more realistic before trying to make the result more impressive. If a strategy survives realistic costs, imperfect fills, other periods, other markets, nearby parameter values, and forward testing, then it has earned further research.
Continue with our TradingView Pine Editor guide if you want to build strategies, our Bar Replay guide for historical practice, or the Backtest Quality Checker for a structured robustness review.
FAQ: TradingView Strategy Tester
What is TradingView Strategy Tester?
TradingView Strategy Tester is the historical testing workflow for Pine Script strategies. The current results area is commonly called the Strategy Report and includes performance, risk, trade-analysis, and trade-level data.
How do I open the Strategy Report?
Open a Superchart, add a strategy from Indicators or your own Pine scripts, and TradingView opens the Strategy Report at the bottom of the chart.
Can I run more than one strategy on the same chart?
TradingView currently runs one strategy on a chart at a time for Strategy Report calculations.
What should I look at first in a backtest?
Start with Net P&L, max drawdown, trade count, profit factor, percent profitable, commissions, and the equity curve. Then audit the individual trades.
Do I need a paid TradingView plan to use Strategy Tester?
No. TradingView’s current plan table includes Pine Script and normal strategy backtesting on Basic. Premium or Ultimate becomes relevant when you specifically need features such as Deep Backtesting or Bar Magnifier.
Can new TradingView users get a $15 discount through ChartWiseHub?
TradingView currently says eligible new users referred through its Partner Program receive a $15 discount coupon toward a new TradingView plan. Eligibility and coupon terms are controlled by TradingView and can change.
What is Deep Backtesting?
Deep Backtesting is a Premium-and-higher Strategy Report mode that can calculate a strategy over deeper stored historical data instead of being limited to the bars currently available in the chart session.
How much data can Deep Backtesting use?
TradingView currently supports up to 2 million bars and up to 1 million trades per Deep Backtesting calculation, subject to the historical data actually available for the selected symbol and timeframe.
Why do Deep Backtesting trades not appear on my chart?
Deep Backtesting results are displayed only in Strategy Report. Trade markers visible on the chart belong to the regular chart-session strategy calculation.
Why are Deep Backtesting and regular results different?
The modes can use different historical starting data and calculation ranges. That can change indicator state, trade sequencing, compounding, and the resulting performance.
What does Bar Magnifier do?
Bar Magnifier uses lower-timeframe data to model price movement inside historical chart bars more precisely, which can improve the realism of simulated stop, limit, entry, and exit fills.
Which plans have Bar Magnifier?
TradingView currently makes Bar Magnifier available on Premium and higher-tier plans.
Can TradingView model commissions?
Yes. Strategies can model commissions as a percentage, cash per contract, or cash per order. Commission is applied to executed strategy orders.
Can TradingView model slippage?
Yes. Strategy properties include slippage in ticks for modeled market and stop-order fills.
Is Strategy Tester accurate?
It is useful for historical research, but results depend on data, strategy code, costs, order-fill assumptions, timeframe, chart type, and parameter choices. It is not a guarantee of future execution or performance.
Should I backtest on Heikin Ashi charts?
You can, but understand that Heikin Ashi uses transformed prices. TradingView provides a standard-OHLC fill option so strategy orders can use actual OHLC prices rather than synthetic Heikin Ashi prices.
What is the difference between backtesting and forward testing?
Backtesting evaluates strategy behavior on historical data. Forward testing observes the strategy on new incoming data that was not part of the historical optimization process.
Can I export Strategy Report data?
Yes. Exporting results is useful when comparing tests across symbols, periods, timeframes, or parameter sets in a spreadsheet or another analysis workflow.
How do I avoid overfitting?
Prefer stable parameter ranges, test other symbols and periods, include realistic costs, keep an unseen validation sample, and avoid repeatedly tuning the strategy to the same historical data.
Related Articles
About ChartWiseHub
ChartWiseHub helps traders and investors learn TradingView step by step with clear tutorials, practical workflow guides, current plan comparisons, and free tools. We focus on making research more repeatable and helping users understand what TradingView metrics actually mean before they rely on them.
Transparency & Risk
ChartWiseHub is reader-supported and this article contains affiliate links. Read our Affiliate Disclosure, Financial Disclaimer, and Editorial Standards.