Price Action Trading Strategies: Breakout, Retest, or Reversal?

Define structure before choosing an entry

Terms such as strong rejection or clean breakout are incomplete trading rules. Specify the reference price, the permitted distance from it, and the bar that confirms the event. One testable structure definition is the highest high of the 20 completed bars before a setup begins. Freeze that value during the setup so the target does not move with each new candle. This is a design choice for the example, not a universal definition of resistance.

• Reference: use only completed bars available before the setup; exclude the signal bar from the lookback.
• Timing: evaluate the three example rules on closed, standard OHLC candles.
• Scope: fix the symbol, timeframe, session, tick size, and data feed before comparing results.
• Swing alternative: a pivot requiring right-side bars is usable only after those bars confirm it. A marker drawn on an earlier swing does not make the level available earlier.

Three objective price action rules

For this illustrative experiment, resistance is frozen at 100 and the prior close is below it. Evaluate each rule separately. Permit only one entry signal per rule in this episode. The retest tolerance and three-bar window are declared assumptions, not recommended settings for every instrument.

The same candles produce three different signals

All prices below are hypothetical, not market data or backtest results. The frozen resistance is 100. Bar A crosses it intrabar but fails the close rule. B confirms a breakout; D later qualifies as a retest. E closes back below resistance, and F confirms the short reversal by closing below E low of 99.2. Read these as signal events, not filled trades or a profitable sequence.

• Breakout exposure starts earlier. A continuation without a pullback can leave the retest rule without any entry.
• Retest confirmation does not prevent failure: D qualifies, then E closes below resistance.
• The reversal requires an extra bar. A quick drop and recovery after E could invalidate that confirmation rule.
• A strategy that allows only one open position may skip later signals. Do not combine the three independent tests into one performance claim.

A signal is not an execution price

TradingView documents that, with default strategy calculation behavior, an order created after a bar closes can first fill on the next available tick, normally the next bar open. In the table, the breakout signal at B would therefore differ from an assumed fill at B close. The example intentionally omits a bar after F, so it supplies no short-entry fill or subsequent outcome. Historical OHLC also cannot reveal every intrabar price path; fills depend on the emulator settings and available detail.

• For an illustrative exit test, use a protective stop one tick below the long signal bar low or above the short signal bar high.
• Set a target two times the entry-to-stop distance from the actual entry, and a time exit after six completed bars in the position if neither price exit occurs. These are test assumptions, not an optimal reward-to-risk claim.
• Define position size and a maximum risk budget before testing. A gap through a stop can exceed the planned loss.
• Record commission, spread treatment, slippage, order timing, and stop/target fill assumptions for each run.

Confirmation delays and false breaks remain

Using price directly does not remove all delay. A close-based breakout waits for the candle to finish; the retest adds another condition; a confirmed swing waits for later bars. TradingView also explains that live high, low, and close values can change before the candle closes. A signal based on those unfinished values can disappear. Waiting for a close addresses that particular issue, but does not guarantee that a strategy is free of every form of repainting.

• Check when a level was confirmed, not just where its label appears on a historical chart.
• Keep higher-timeframe inputs confirmed if you add them, and review their data-request behavior separately.
• Keep a missed-trade category: a setup that expires is different from a trade that enters and loses.

Compare the rules without selecting only favorable examples

The six-bar example proves only that the rule definitions differ. To evaluate a price action trading strategy, run all three versions on the same symbol, session, timeframe, date range, position-sizing method, and cost assumptions. Keep a later period untouched while defining the rules, then test it without retuning. Report the full trade distribution, including unsuccessful breakouts and retests, rather than collecting attractive chart patterns.

• Record signal count, filled trades, expired setups, average net trade, drawdown, holding time, and losing streaks.
• Save the rule version and input settings alongside the trade export so results can be reproduced.
• Separate ranging periods, sustained moves, and gap-heavy sessions to see where a rule fails.
• Change the lookback or retest tolerance over a small predeclared range. A result that depends on one exact setting needs further investigation.

Turn the definitions into a reviewable strategy

Pine Script AI Coding Agent can draft a strategy from the reference-level, entry, expiry, and exit rules. Check the generated logic against the six-bar sequence before evaluating performance. Visual Pine Script Editor provides conditions and strategy controls for supported configurations; a sequence that remembers a breakout and counts subsequent bars needs an explicit state definition. Backtest Deep Report can analyze exported TradingView trades and export an Excel workbook. Keep the source CSV and failed-trade examples with that report; it does not prove that the original signal logic was correct.