Before Strategy Tester
Confirm you are testing a strategy, not only an indicator
A chart indicator can visualize conditions, but TradingView's Strategy Tester needs a strategy script that models simulated orders. Start with rules that are explicit enough to inspect: entries, exits, no-trade conditions, position rules, risk controls, sessions, and the intended market and timeframe. The Strategic Edge AI can help translate an approved specification into Pine Script, but you independently review and run the exact source in TradingView before treating it as a testable artifact.
For the current platform behavior and terminology, review TradingView's strategy documentation. This guide explains the research discipline around a test; it is not a substitute for the platform's operating instructions.
Do not change the rules after seeing a favorable report and call the result a baseline. Once the report guides a redesign, it belongs to the development history of the next version.
Set up a traceable test
Record the conditions that produced the report
In Strategy Tester, configure the test surface deliberately. The objective is not one universally correct setting; it is a record that another review can understand and reproduce using the same chart context and simulation assumptions.
| Record for this run | What to preserve | Why it matters |
|---|---|---|
| Strategy and source version | The exact Pine Script strategy, its version identifier, and the approved rule specification it implements. | A result cannot be reviewed cleanly if the script or rules changed after the report was generated. |
| Chart and market context | Symbol and exchange, chart type, timeframe, test date range, and any session or market-condition filters. | The surface being tested affects the historical behavior you are measuring. |
| Strategy Properties | Initial capital, position-sizing method, commissions, slippage, pyramiding, and other enabled simulation settings. | A report is evidence only in the context of the assumptions used to produce it. |
| Order and fill model | Any relevant order-processing or intrabar settings, including whether Bar Magnifier was enabled. | Different fill assumptions can change simulated orders and should be recorded rather than treated as invisible defaults. |
| Evidence package | The performance report, trade list where available, settings, source version, and the question you intend to investigate next. | Preserving the context keeps a later review from relying on memory or a favorable screenshot. |
Model fills deliberately
Treat Bar Magnifier and Properties as recorded assumptions
Commission, slippage, order-processing choices, and intrabar fill modeling can influence a simulated result. If you use TradingView's Bar Magnifier, retain that fact with the report and compare it as part of the test model—not as a switch that proves a result is accurate or transferable.
Make assumptions visible
Save the relevant Properties and chart conditions with the result. A comparison is not interpretable when its cost or fill model is unknown.
Check the current platform guidance
Use TradingView's current documentation for the meaning and availability of settings such as Bar Magnifier. Platform behavior, data availability, and your chosen configuration should be independently reviewed.
TradingView's official reference on Bar Magnifier and its Strategy Properties is the authoritative source for platform-specific options.
Run and inspect
Read more than net profit
A strategy report is evidence about a fixed historical exercise. Review the result against the rules and assumptions you recorded, then ask whether the behavior is stable enough to justify a narrowly defined next question.
Trade count and distribution
Ask whether the result rests on enough trades and whether outcomes are concentrated in a short period, a few trades, or a narrow market condition.
Drawdown and equity path
Read drawdown, losing streaks, recovery behavior, and the equity curve alongside the headline result. A final total can hide an unacceptable path.
Costs and fill sensitivity
Compare the result with the recorded commission, slippage, sizing, and fill assumptions. A thin historical edge may depend on settings that do not transfer.
Rule-to-result consistency
Check that simulated entries and exits match the approved rules. A surprising result can be a script or configuration issue, not a strategy discovery.
Preserve evidence
Keep the report connected to the decision
Save the report, the underlying Properties, the Pine Script version, the strategy specification, and the reason for the next test. When you upload exported evidence to Evolve, the useful question is not “make this better.” It is “given this documented behavior, what single hypothesis should we test next?”
01 · Preserve the baseline
Save the Strategy Tester output, Properties, Pine Script version, and strategy specification before changing anything.
02 · State one question
Describe the observed weakness or trade-off that motivates the next test. Do not begin with a request to improve every metric.
03 · Make one controlled revision
Change one named rule or assumption, then keep the other recorded conditions fixed so the comparison remains intelligible.
04 · Validate separately
Treat holdout, walk-forward, forward, or simulation work as a distinct validation layer—not as a conclusion implied by one historical report.
From history to validation
Keep historical, holdout, and forward work distinct
Historical baseline
A fixed source version is tested on a named historical period under documented Strategy Tester settings.
Holdout or walk-forward work
Later data evaluates earlier decisions when the selection boundaries are written down before the results are reviewed.
Forward or simulation work
A separate phase observes how a frozen strategy behaves after historical development. It is not implied by a backtest result.
Make the next Pine Script test easier to explain
Start with explicit strategy rules, independently review the Pine Script, save the Strategy Tester evidence, and make one controlled revision at a time.
Educational strategy-development content only. The Strategic Edge AI does not provide trade signals, automated execution, financial advice, or guarantees of future performance.