How to Backtest NAS100 in TradingView and Journal Every Trade

A backtest becomes unreliable when the trader changes the rules after seeing the next candles. Before opening TradingView replay, write the exact market condition, entry trigger, invalidation, stop placement and target logic. If those rules are not clear, the backtest is measuring discretion rather than a system.

For NAS100, this matters because the index can move quickly and create tempting hindsight entries. A clean test starts with one playbook. Do not test continuations, reversals, news volatility and range trades in the same sample unless the goal is to compare them separately.

Chart screenshots are useful, but TradingView links make review faster because the trader can reopen the exact context. The Syndicates journal supports timeframe links, so a trader can keep higher timeframe, confirmation timeframe and execution timeframe references attached to the trade row.

This creates a better review loop. If a losing trade looked valid on the entry timeframe, the higher-timeframe link may show that the setup was actually fighting structure. If a winner looked easy, the saved links may show that the stop placement was poor even though the outcome was positive.

A win/loss column is too thin for NAS100 backtesting. The same strategy can look profitable or weak depending on average win, average loss, commission assumptions and whether breakeven trades are counted correctly. R/R makes the test more comparable across account sizes.

The journal should record gross R/R, net R/R, stop size, session, pair, notes and the R/R the trade actually ran. That gives the trader a way to test whether a 1:2, 1:3 or 1:4 target would have made sense across the sample.

The easiest way to ruin a manual backtest is to treat future information as if it was available at entry. A fixed review rule helps. Once the trade qualifies, record the trade before scrolling forward. If the trade loses, do not remove it because it looked obvious later.

A clean backtest counts boring losses, missed winners, breakevens and valid no-trades. If the test only includes beautiful examples, the journal will give false confidence. The goal is to know whether the setup survives ordinary market conditions.

After a sample is complete, review the results by session, day, drawdown, target, setup quality and rule adherence. The goal is not only to find the highest win rate. The goal is to find the version of the setup that a real trader can execute without breaking risk.

If the data is promising, create a separate forward-test journal before using live money. If the data is weak, do not force the setup. Record what failed and either improve one rule or abandon the idea.