Manual backtesting
Manual backtesting on the TradingView chart you already trade
Manual backtesting means stepping through past candles with the future hidden and taking every trade by hand, the way you would live. It tests a discretionary playbook that cannot be written as code. TestingView adds the session, the risk, the journal, and the statistics to your own TradingView layout.
Works in Chrome, Edge, and Firefox, and in TradingView Desktop on Windows. The free Starter plan holds 20 trades per session.
What manual backtesting is
A backtest asks one question: if you had followed these rules on past prices, what would the record have been? An automated backtest answers it with code. A strategy script reads every bar and fires the entries itself. A manual backtest answers it with you. You replay history bar by bar, decide on each setup as it forms, and write down what happened.
Manual testing is the right tool when the rules live in your judgment: a level you read off a higher timeframe, a pattern you recognize, a session you only trade when it looks a certain way. Those decisions are hard to code honestly. A coded approximation tests the approximation, not you.
Manual and automated backtesting answer the same question with different tools. | Manual backtesting | Automated backtesting |
|---|
| Who takes each trade | You, bar by bar, with the future hidden | The script, on every bar |
|---|
| What you need first | A written playbook and the chart you trade | Code, for example a Pine Script strategy or a Python framework |
|---|
| Speed | Hours for a sample of dozens of trades | Seconds for thousands of trades |
|---|
| Best at | Discretionary setups, execution practice, trade management | Fully mechanical rules, parameter tests, very long samples |
|---|
| Main way it misleads | Hindsight and samples that are too small | Overfitting and fills that assume too much |
|---|
The longer version, with when to switch from one to the other, is on the blog: manual vs automated backtesting.
What to measure
- Expectancy: the average result per trade, after the losers. This is the number that says whether the playbook paid.
- Profit factor: gross profit divided by gross loss.
- Maximum drawdown: the deepest drop in the session balance, and whether you could have sat through it.
- Win rate, next to average win and average loss: a high win rate with small winners can still lose money.
- Results by hour and weekday (Explorer and Trader): where the money actually came from.
Formulas, and how TestingView computes each one, are on the methodology page. For a longer read on why win rate is the wrong headline, see which numbers matter.