Backtesting on TradingView

Decoded TradingView backtesting workflow for forex and crypto (Bitcoin, altcoins) using 5-minute entries with 4-hour higher-timeframe analysis.

Published · Updated · Methodology: Mixed

Part of: Moving Average Strategies

  • Methodology: Mixed
  • Content type: educational
  • Timeframes: 5 minutes, 4 hours (for higher temporal analysis)
  • Markets: Forex, Cryptocurrencies (Bitcoin, Altcoins)

Indicators used

  • Moving Average

Source video

Decoded from: 📣Cómo hacer BACKTESTING de FOREX en tradingview 📊 by Gerard Garcia — watch the original

Key timestamps:

  • 0:00 - Introduction to backtesting
  • 1:10 - Why manual backtesting is better than automated programs
  • 2:00 - Setting up TradingView for backtesting (Replay function)
  • 2:40 - Example strategy setup (EMA 55 & 21)
  • 3:40 - How to use the long/short position tool for risk management
  • 4:40 - Recording results and adjusting stop loss/take profit
  • 6:00 - Example of a short trade setup
  • 7:30 - Moving stop loss to break-even after first take profit
  • 9:00 - Analyzing backtesting results and making adjustments
  • 10:00 - Importance of short take profits for scalping strategies

Strategy overview

A moving average smooths price into a single line that most traders use to read trend direction, and pairs of them are the standard demonstration setup for a crossover rule. That is exactly the role the averages play here: this entry is not really a setup at all, but a method video. Gerard Garcia's Spanish-language "Cómo hacer BACKTESTING de FOREX en tradingview" is about the act of testing, and an example built on a pair of exponential moving averages is the disposable vehicle he drives through it.

The chapter map makes the thesis explicit in its second entry: manual backtesting is presented as better than automated programs. That inverts the usual relationship on a page like this one — the indicator becomes the prop and the tester becomes the subject. The workflow that follows is a loop rather than a rule set: open TradingView's Replay function, drop an example setup on the chart, use the long/short position tool to frame risk on each simulated trade, then record the outcome. Swap the averages for any other trigger and the loop is unchanged, which is the clearest sign of where the video's real content sits.

The last chapter is also the one that deserves the most scepticism, and it is worth naming plainly: recording results while adjusting stop loss and take profit is where a manual test is most fragile. Bar-by-bar replay is run by someone who already knows the chart, and tuning exits against outcomes you have partly seen is how a test quietly becomes a fit. The two timeframes compound it — an execution chart of five minutes with a four-hour reference means the higher-timeframe context has to be reconstructed as it stood at that moment, not as it reads today. No extracted rule set is on file for this entry, which is consistent with a video that teaches a procedure rather than a system, so the useful questions here are about the procedure's discipline rather than about the averages themselves.

Topics

tradingview backtesting · manual backtesting · forex strategy backtesting · crypto backtesting · pine script strategy · trading strategy · ema strategy · moving average strategy · 5 minute strategy · 4 hour strategy · btc trading strategy · altcoin trading strategy · trading tutorial · strategy tutorial · replay function tradingview

Frequently asked questions

What is manual backtesting on TradingView?

It means stepping a chart forward bar by bar with TradingView's Replay function and evaluating each trade by hand — marking the entry, framing the stop and target with the position tool, and logging the outcome — instead of letting a script compute results over a data set automatically.

Is manual backtesting really better than using an automated backtester?

The source video argues that it is, and there is a real case for it: working trade by trade forces you to read context the way you would in live conditions. The trade-offs are equally real, though — manual review covers far fewer samples, takes far longer, and is exposed to hindsight because the person clicking through the replay already knows the chart.

Why is adjusting stop loss and take profit during a backtest risky?

Because you are changing the rules after seeing the results. Tuning exits to fit outcomes you have already observed produces a curve that flatters the past and says little about the future. If exits are adjusted, the honest approach is to treat the run as exploratory and re-test the revised version on data you have not already walked through.

Does the moving average setup matter in this video?

It functions as a teaching example rather than the point — the same replay workflow would apply to almost any entry trigger. Strategy Decoder catalogues entries like this one so you can tell method videos apart from rule-based setups before deciding what is worth testing.

About this strategy page

This trading strategy was decoded by Strategy Decoder's AI from a public YouTube trading video and turned into a structured, reviewable specification. In the interactive app this page shows the full entry and exit logic, risk management settings, the indicators involved with their parameters, AlgoWizard-compatible logic and a Pine Script export ready for TradingView backtesting — plus an automated backtest verdict when one has been computed for this strategy.

Strategy Decoder catalogs 2,229 decoded strategies. Each one is extracted with confidence scoring, cross-linked to the indicators it uses, and kept up to date as new videos are processed daily. Load this page with JavaScript enabled to use the interactive tools, or start from the strategy explorer to filter by methodology, market and timeframe.

Other versions of this strategy

More decoded strategies