# Why Strategy Versioning Matters In Walk-Forward Tests Slug: why-strategy-versioning-matters-in-walk-forward-tests. Canonical: https://tradingtune.com/blog/why-strategy-versioning-matters-in-walk-forward-tests ## Summary Explains how code or input changes can make fold comparisons hard to interpret. ## Key facts - A fold comparison is only valid when every fold ran the same code against the same inputs. - Tag the code and the exact input set with a version before the first fold runs, and keep that tag frozen until the batch is done. - A silent change to a rule or to an input default can look like a market effect when it is only a version change. - Log the version beside each fold result as soon as the fold finishes, and compare only folds that share a version tag. ## Outline - What Strategy Versioning Means For Walk-Forward Tests (#what-strategy-versioning-means-for-walk-forward-tests) - Setting Up A Sweep You Can Actually Track Over Time (#setting-up-a-sweep-you-can-actually-track-over-time) - What Changes When You Move Through A Parameter Range (#what-changes-when-you-move-through-a-parameter-range) - A Look At One Versioned Sweep (#a-look-at-one-versioned-sweep) - When An Untracked Code Change Fooled A Fold Comparison (#when-an-untracked-code-change-fooled-a-fold-comparison) - How I Version Strategies Before Running The Next Sweep (#how-i-version-strategies-before-running-the-next-sweep) - The One Habit That Keeps Fold Comparisons Honest (#the-one-habit-that-keeps-fold-comparisons-honest) - Sources (#sources) ## Code snippets - Anchor: #pine-snippet-1