Skip to main content
Track Robustness testing
53 / 57
Search the archiveLibrary
Library

2019issue C1347-52

Three gates for evaluating a trading system

A trading system can be evaluated as one procedure that jointly specifies entry, exit, and abstention. TradersWeek editorial reading: treat that evaluation as three gates. Make the full rule set testable, ask whether it still works when conditions change, and judge the procedure rather than a single fitted result.

  • Evaluate a trading system as one procedure that jointly specifies entry, exit, and abstention, not as a collection of isolated signals.
  • System optimization is useful when it makes those joint rules testable under stated market-state and execution constraints, not when it searches for a single best historical fit.
  • Robustness testing asks whether the same procedure still produces a usable signal when inputs, market conditions, or execution constraints change. Walk-forward analysis evaluates that procedure across successive in-sample and out-of-sample windows that match the system holding period.
  • Software listings, course directories, page-view rankings, and access to a large library are not independent proof that a tested procedure is robust or that a result will transfer.
Entries in this reading3 entries
Current trackRobustness testing67 readingsSystem optimization91 readingsWalk-forward analysis99 readings

A system as one procedure

A trading system can be evaluated as one procedure that jointly specifies entry, exit, and abstention rather than as a collection of isolated signals. The object under review is the full rule set, including when the system stands aside.

What system optimization is for

System optimization is useful when it is framed as making those joint rules testable under stated market-state and execution constraints. It is not useful when it is framed as searching for a single best historical fit. The constraints belong in the test. They are part of the procedure, not an afterthought.

Robustness testing under change

Robustness testing asks whether the same procedure still produces a usable signal when inputs, market conditions, or execution constraints change. The question is not whether a new rule set can be written after the change. The question is whether the procedure already under review still produces a usable signal.

Walk-forward analysis across windows

Walk-forward analysis evaluates the procedure across successive in-sample and out-of-sample windows that match the system holding period. The window length follows the holding period of the system. The object that moves from window to window is the procedure, not a single fitted result.

What listings do not prove

Advertised software and course listings in the source material are vendor or directory claims, not independent proof that a tested procedure is robust. Directory rankings based on page views or clicks are popularity measures and are not editorial ratings of system quality. Vendor listings can include resellers as well as developers, so a product name is not automatically the identity of the system author. Access to a large library of books and courses is a knowledge resource. It does not by itself establish that a particular optimization or walk-forward result will transfer.

Educational research material, not investment advice. Historical source context does not establish present-day performance.
53 of 57 in the Robustness testing track
202046-47 pp.Next on Robustness testingData construction as a mechanical system inputSplit and dividend accounting in the historic file must be known before a mechanical strategy is tested, because the same price path can be assembled in more than one coherent way.
All readings on this track · 57 readings
  1. 1986Degrees of freedom in trading system optimization
  2. 1988Walk-forward and neighborhood tests after optimization
  3. 1988Undisclosed rules block system robustness tests
  4. 1988Testing re-optimization calendars against random parameter controls
  5. 1989Binary search limits on multi-peak average grids
  6. 1989Parameter neighborhoods that survive a shift
  7. 1990Use profit mapping to keep a cycle and stop plateau
  8. 1990Why popular indicator optimization fails robustness
  9. 1991Retesting weighted indicator balances across horizons
  10. 1992Constructing forecast models with regression, walk-forward, and robustness
  11. 1992Diagnose regimes before you lock parameters
  12. 1992When stops change system timing
  13. 1993Walk-forward halt rules for forecast models
  14. 1994Walk-forward evaluation of genetic index rules
  15. 1995Input pruning as walk-forward system evaluation
  16. 1995Critiquing neural nets as incomplete trading systems
  17. 1996Rebuild the equity-path ratio before it ranks a designed system
  18. 1996Parameter grids can fit random walks
  19. 1996Walk-forward analysis belongs in the design of a mechanical trading system
  20. 1997When a holdout fails, discard the rule set
  21. 1997Test rewarded rule breaks before replacing the system
  22. 1997Walk-forward rules keep system research from rewriting live trades
  23. 1999Keep a channel-breakout to two lookbacks and test neighbor stability
  24. 1999Constant investment size in stock system evaluation
  25. 2000Forcing optimization maps mechanical system failure boundaries
  26. 2000Robust parameter selection with surface charts
  27. 2001A two-gate classroom test for a two-window momentum trend filter
  28. 2002How a two-sided continuation factor becomes a testable trend rule
  29. 2002Evaluating two-window trend intensity as a reversal rule
  30. 2003Discounting speculative bubbles in system robustness tests
  31. 2003Walk-forward evaluation of locked stochastic oscillator rules
  32. 2003Critiquing mechanical system design after extreme price regimes
  33. 2004Evaluating a two-window trend trigger
  34. 2005Grade backtested signals with holdouts and optimization plateaus
  35. 2006Reserved-sample evaluation of trading system design
  36. 2006Walk-forward critique of hindsight crossover systems
  37. 2008Condition-matched walk-forward evaluation for mechanical systems
  38. 2011Session-split evaluation of regular and overnight systems
  39. 2012Walk-forward evaluation as operator rehearsal
  40. 2013Two-window evaluation of mechanical trading systems
  41. 2013Walk-forward filter selection for repeated-median velocity
  42. 2014Walk-forward evaluation for fading-memory velocity systems
  43. 2015Test oscillator events before tuning rules
  44. 2016Walk-forward evaluation of a five-parameter parabolic stop-and-reversal
  45. 2016Walk-forward optimization without curve fitting
  46. 2017Optimization without overfitting in trend-system evaluation
  47. 2017Parameter stability is a better guide than a larger crossover grid
  48. 2018Point-in-time universes for system evaluation
  49. 2018Walk-forward robustness evaluation for optimized systems
  50. 2018Critiquing breakout systems through robustness tests
  51. 2018A critique of parameter fitting in system design
  52. 2019Noise-matched rules still need trend filters and robustness tests
  53. 2019Three gates for evaluating a trading system
  54. 2020Data construction as a mechanical system input
  55. 2020Hidden optimization in ported relative-strength systems
  56. 2020When mechanical historical tests decay after optimization
  57. 2025Add a second procedure before you retune the first
By fieldSystem design128 readingsBy year201978 readings
All 67 readings tagged Robustness testing
Also on Robustness testing5 readings
1986Degrees of freedom in trading system optimization1988Testing re-optimization calendars against random parameter controls1988Walk-forward and neighborhood tests after optimization1992Diagnose regimes before you lock parameters1993Walk-forward halt rules for forecast models