Full Q&A for TestingView covering sessions, trades, the backtesting journal, statistics, playback, and plans. See feature overview.
TestingView is a backtesting tool that runs on top of TradingView. It adds backtesting session management, simulated position tracking, risk sizing, a journal of backtested trades, snapshots, statistics, and safer candle playback controls.
TestingView can work with the TradingView replay features available on your TradingView account. If your TradingView plan does not allow replay on lower timeframes, TestingView cannot unlock that limitation.
No. TestingView does not unlock TradingView plan limits such as lower-timeframe replay, extra indicators, more charts per layout, or additional historical data.
TestingView may warn you and switch the chart to a higher supported timeframe, such as the daily timeframe, so the session can still run with the historical playback access TradingView allows.
TestingView is built for browser-based TradingView use through the supported extension flow. Install links are browser-specific: Chrome and other Chromium browsers use the Chrome Web Store, Microsoft Edge uses the Edge Add-ons store, and Firefox uses [addons.mozilla.org](https://addons.mozilla.org/en-US/firefox/addon/testingview/). From testingview.com, use **Get extension** or open `/extension` for an automatic redirect.
You must already have TradingView Desktop installed. TestingView is an add-on that runs inside that app. Download **TradingView x TestingView.exe** from testingview.com (**Download desktop app** on the home page, or `/setup`).
Yes. TestingView supports TradingView multi-chart layouts. This is useful for watching multiple timeframes side by side instead of constantly switching chart intervals.
Yes, if your TradingView layout supports multiple charts and symbols. TestingView tracks trades by symbol, while the session keeps one shared account balance, equity, and backtesting journal.
Yes. A common workflow is to open several charts in the same TradingView layout, set each chart to a different timeframe, and let TestingView advance them together during backtesting.
Yes, within your TradingView plan limits. TestingView does not increase the number of indicators your TradingView account can use.
Yes, if the indicator is built to expose compatible TestingView event signals. Ordinary indicators are not automatically treated as stop events.
TestingView can work with TradingView symbols across common asset classes such as forex, stocks, futures, indexes, commodities, crypto, and CFDs, as long as TradingView replay data is available for the symbol.
Yes. TestingView uses symbol and market information to account for differences such as forex lots, commodities, futures point values, indexes, stocks, and other symbol types.
Yes. TestingView uses the timezone shown on your TradingView chart. If that timezone observes Daylight Saving Time, chart times and journal times follow the chart timezone.
Yes. Keeping the chart timezone consistent makes replay times, journal entries, screenshots, and exports easier to compare.
No. TestingView blocks navigation into future dates.
Yes, your session and journal data are tied to your TestingView account. You still need to be logged in with the correct TradingView/TestingView account and have access to the needed TradingView chart data.
No. TestingView uses your TradingView identity for linking access, but it does not ask for or store your TradingView password.
Open TradingView, click the TestingView toolbar button, then create a new session or resume an existing one.
You choose a session name, starting capital, account currency, and start date. The session then becomes the account and journal container for your backtest.
The session currency list includes common fiat and crypto currencies such as USD, EUR, GBP, AUD, CAD, CHF, JPY, NZD, SEK, SGD, ZAR, BTC, ETH, USDT, and others.
ChronoShuffle starts a session at a random date inside a past date range. It is useful when you want to practice without knowing exactly what market period comes next.
Start or resume a session, draw a TradingView Long Position or Short Position tool, set entry, stop loss, take profit, and risk/size, then play candles. When price reaches the entry, TestingView opens and tracks the simulated trade.
Usually yes. If price gaps through your entry between candles, TestingView opens the trade at the new candle open instead.
Yes. Enable the Confirm Entries setting to show a confirmation dialog before a detected position is opened.
TestingView will not open the trade. It shows a warning and removes the invalid position drawing.
TestingView watches TradingView Long Position and Short Position drawings. When price reaches during backtesting the entry level, the drawing becomes a tracked TestingView position.
TestingView closes trades when price reaches stop loss or take profit, when a user manually closes the trade, or when trade-management logic such as break-even changes the active stop.
On a candle where both levels are touched, the exact order can be ambiguous unless lower-timeframe price movement is available. For best accuracy, use the smallest practical playback step when managing active trades.
Yes. Active trades can be closed manually from the journal/trade controls.
TestingView replaces the original setup drawing with managed entry, stop, target, and break-even lines. Use those managed lines to adjust the active trade.
Yes, but only when there are no open positions and the requested date does not conflict with existing closed trades.
Review mode lets you revisit previous trades from the journal. You can jump to a trade, inspect it, and then return to the active session date.
Review mode is available only when the session has enough trade history and no active open position.
Yes. You can add a playback stop line on the chart. When price reaches or crosses the line, TestingView stops playback.
Predefined hours are specific times, such as `09:30`, `12:30`, or `15:30`, where TestingView can automatically pause playback.
Chart events are compatible indicator or integration signals that can tell TestingView to stop playback when a specific plotted event appears.
TestingView exits its active session flow because it needs TradingView replay to remain active for accurate tracking.
TestingView calculates risk from entry price, stop price, quantity, contract size, point value, and the position tool's currency conversion at entry.
Lot size comes from the Long/Short Position tool and the selected risk settings. TestingView then normalizes the quantity for the symbol being traded.
Yes. Use the TradingView position tool to set a fixed money risk amount before the trade opens.
Yes. Use the TradingView position tool to set percentage-based risk before the trade opens.
Yes. Risk, profit, balance, equity, run-up, drawdown, and statistics are shown in the session's account currency.
TestingView stores the conversion rate from the position setup at trade entry and uses that saved value for risk and PnL calculations.
Yes. Move the managed stop-loss line on the chart. TestingView updates the trade and journal values.
Yes. Move the managed take-profit line on the chart. TestingView updates the active trade and journal values.
Yes. Stop loss must remain on the valid side of the current price and cannot cross an active break-even level.
Yes. Take profit must remain on the valid side of the current price and cannot cross an active break-even level.
Yes, on plans that include break-even. When price reaches the configured BE level, TestingView moves stop loss to entry.
TestingView removes the BE trigger, moves SL to entry if your plan allows it, updates the journal, and can capture an automatic snapshot if snapshots are enabled.
TestingView shows a warning and does not automatically move the stop to entry.
Yes. The BE line must be placed between entry and target, on the profitable side of entry, and must not conflict with the current SL or TP.
Yes, if your plan allows quantity editing and the session setting for modifying quantity is enabled.
TestingView recalculates risk, profit, balance/equity impact, and journal metrics based on the new quantity.
Yes, on plans that include slippage/spread tools. These values are used in statistics and performance analysis.
Run-up is the maximum favorable movement reached by a trade while it was open.
Drawdown is the maximum unfavorable movement reached by a trade while it was open.
RR is the reward-to-risk relationship between the trade's target and stop. TestingView stores and updates it with the trade.
Yes. TestingView automatically saves sessions, simulated trades, journal values, snapshots, and settings while you backtest.
Default columns include Trade, Date/Time, Price, Symbol, Lots, RR, Risk, Profit, Cumulative Profit, Run-up, Drawdown, BE Run-up, Snapshots, Notes, and Analysis Time.
Yes, on plans that include journal customization. You can add, rename, reorder, show, hide, and remove custom columns for your backtesting journal.
Supported column types include text, rich text, number, checkbox, date, time, datetime, dropdown-style values, and action columns.
Yes. Custom columns can use predefined values such as setup type, confidence, grade, market condition, or mistake category.
System columns are protected so TestingView can keep trade calculations and actions working correctly. You can still choose which columns are visible where supported.
Yes, on plans that include journal export. The export creates an Excel workbook from your session’s backtesting journal.
Yes. TestingView can save TradingView snapshot links to the trade journal.
Yes. Enable Auto Capture Trade Snapshots to automatically capture snapshots around important trade events such as entry and exit.
Yes. In multi-chart layouts, TestingView can capture separate snapshots from each chart when requested.
Yes. The snapshot viewer lets you browse, copy, open, and delete saved snapshots.
Yes. The journal includes a Notes column for trade notes.
Analysis Time tracks how long you actively spend reviewing a trade/chart during the session.
Yes. TestingView supports cloning a session, including trades, journal values, snapshots, and settings.
Yes. You can delete a session from the session list. If you delete the active session, TestingView exits that session.
Yes. New sessions can reuse your most recent journal column setup so you do not have to rebuild the same journal structure every time.
Yes. Selecting or double-clicking journal rows can focus the related trade, redraw the trade shape when needed, or navigate to the trade in review mode.
TestingView can show metrics such as profit, win rate, profit factor, average RR, drawdown, run-up, expectancy, streaks, equity curve, returns, and other performance charts. Some advanced statistics depend on your plan.
No. The journal is for backtested (simulated) trades in TestingView sessions. It is a historical record of your practice trades, not a live trading journal.
TestingView links access to your TestingView account and TradingView username.
Yes. If your account page allows username changes, update the TradingView username there so access is linked to the correct TradingView identity.
The current product plans are Starter, Explorer, and Trader.
Starter lets you resume saved sessions and run core backtesting on TradingView. You can place up to 20 trades per session and use Go to Time up to 10 times per session. You keep one backtesting session at a time, with a basic backtesting journal and standard statistics. Automatic break-even, custom journal columns, Excel export, slippage/spread tools, and editing lots after entry are not included.
Explorer includes everything in Starter, plus up to 50 trades per session, automatic break-even, advanced performance metrics, custom journal columns, and unlimited Go to Time per session. It does not include unlimited trades, multiple concurrent sessions, journal export, slippage/spread modeling, or editing position quantity after entry.
Trader includes everything in Explorer, plus unlimited trades per session, multiple backtesting sessions at once, Excel export of the backtesting journal, slippage and spread modeling in statistics, and the ability to edit position quantity after entry (when enabled in session settings).
Yes. Starter is capped at 20 trades per session. Explorer raises the cap to 50. Trader does not have a trade cap.
Explorer and Trader include automatic break-even.
Explorer and Trader include advanced statistics.
Explorer and Trader include journal customization.
Trader includes journal export.
Trader includes slippage and spread tools.
Trader allows modifying lots after entry, as long as the session setting is also enabled.
Yes. On Starter, each session allows up to 10 Go to Time / custom date jumps. Explorer and Trader include unlimited Go to Time usage per session.
Only Trader allows more than one backtesting session at a time. Starter and Explorer are limited to a single session. The app blocks creating another until you upgrade or delete the existing session.
If access expires, plan-gated features become unavailable until the account is renewed or updated.
Yes. Subscription cancellation is handled through the account/billing area when billing is active.
No. TestingView and TradingView subscriptions are separate. TestingView does not change, upgrade, or cancel your TradingView plan.
TestingView adds play/pause, step forward, fast-forward, skip interval selection, Go to Time, review mode, settings, statistics, and session balance/equity controls.
The minimum skip interval depends on the replay resolutions TradingView makes available for your account, symbol, and chart. TestingView uses the smallest practical available replay resolution unless you choose another supported setting.
Yes. You can set the minimum step-forward resolution in TestingView settings.
Tick and second-based playback depend on TradingView's available recorded ticks. If ticks are missing, playback may jump to the next available tick.
Fast-forward repeatedly advances candles until it reaches the next valid target time or until something important stops playback.
TestingView aligns larger skips with natural candle close times. For example, skipping by one hour from `09:47` targets `10:00`, then `11:00`, then `12:00`.
TestingView prioritizes accuracy and chart stability. It advances candles carefully so entries, exits, break-even triggers, predefined times, and stop events are not missed.
Yes, through Go to Time/custom date when allowed. It is not available while a trade is open, because jumping over candles could miss trade-management events.
No. Go to Time is blocked while a position is open.
Prevent Candle Previews is a setting designed to reduce higher-timeframe candle preview issues when changing timeframes or navigating replay.
Not always. New sessions may start with it disabled, and your previous session settings may carry forward. You can change it in settings.
TestingView tries to keep the session date stable. If Prevent Candle Previews is enabled, it may navigate to a safer completed candle and advance forward to avoid revealing unfinished higher-timeframe candle information.
Warmup Start is not a separate visible setting in the current workflow. The related behavior is handled by Prevent Candle Previews and controlled playback navigation.
Playback can stop for entries, exits, break-even triggers, predefined hours, compatible chart events, a user stop line, future-date protection, or unsafe step size while a trade is open.
Add times such as `09:30`, `12:00`, or `15:30`. TestingView pauses when playback reaches those chart-timezone times.
No. They are intended for smaller playback steps and are disabled on very large step sizes such as four hours or higher.
When enabled, TestingView watches compatible indicator events and pauses when a matching event appears.
Add a stop line at a price. TestingView stops playback when price reaches or crosses that line.
Large steps can skip over stop loss, take profit, or break-even events. TestingView asks you to use a smaller step when needed to protect trade accuracy.
TestingView treats unexpected backward jumps as unsafe and may exit or reload the session flow to avoid saving inaccurate state.
TestingView may warn you and stop trusting automatic current-date tracking, because too much playback movement may have been skipped.
Yes. Large skips can feel slow, lower-timeframe replay depends on TradingView access, tick data may be incomplete, open trades require smaller step sizes, and a single OHLC candle cannot always prove whether SL or TP was hit first.
TestingView exposes shortcuts such as play/pause, step forward, and fast-forward from the replay controls. The exact shortcut is shown in each control's tooltip.
