MyAlgoGuru Help
Education Glossary Open the app
Help/Reference/Research & Analytics

Strategy Validation

An out-of-sample robustness check before you deploy: does the strategy hold up on data it wasn’t tuned on?

Where you will find this

Strategy validation.

Purpose

Validation splits the period into in-sample and out-of-sample halves, backtests each, and compares them — plus a configuration-completeness check. The outcome tells you whether the strategy is robust enough to deploy.

The Strategy Validation module evaluates whether a trading strategy maintains consistent performance beyond the conditions used during optimisation.

It provides structured validation techniques to assess the robustness, stability and reliability of trading strategies before deployment to live trading.

The module serves as the final research validation stage prior to production deployment.

Objectives

The module will:

  • Validate optimised trading strategies.
  • Assess strategy robustness.
  • Measure strategy stability across different market conditions.
  • Detect overfitting.
  • Preserve validation history.
  • Support comparison of validation results.
  • Provide validation outcomes for deployment decisions.

Functional Scope

The module includes:

  1. Validation Definition
  2. Validation Configuration
  3. Validation Dataset Selection
  4. Validation Execution
  5. Validation Method Management
  6. Robustness Assessment
  7. Validation Results
  8. Validation History
  9. Validation Audit

Validation Model

A validation represents the evaluation of a trading strategy using one or more independent validation methodologies.

Validation is performed after strategy optimisation.

Validation activities remains independent of live trading.

Strategy Selection

Each validation will reference:

  • One Strategy
  • One Approved Strategy Version
  • One Optimisation Result (where applicable)

Validation does not modify the underlying strategy.

Validation Dataset

Validation will use historical market data that is appropriate for the selected validation methodology.

Dataset selection may include:

  • Instrument
  • Exchange
  • Timeframe
  • Date Range

Historical datasets remains unchanged during validation.

Validation Methods

The platform will support multiple validation methodologies.

Typical methods include:

  • Walk-Forward Testing
  • Out-of-Sample Testing
  • Rolling Window Validation
  • Robustness Testing
  • Sensitivity Analysis

The design remains extensible for additional validation techniques.

Validation Configuration

Each validation will maintain its execution configuration.

Typical configuration includes:

  • Strategy Version
  • Validation Method
  • Historical Dataset
  • Validation Period
  • Performance Criteria
  • Acceptance Criteria

Validation Execution

The platform will execute validation activities according to the selected methodology.

Each validation execution is independent.

Execution does not modify historical market data or optimisation results.

Robustness Assessment

The platform will evaluate strategy robustness.

Typical assessment areas include:

  • Performance Stability
  • Risk Stability
  • Trade Consistency
  • Parameter Sensitivity
  • Market Condition Adaptability

The assessment framework remains extensible.

Validation Results

Each completed validation will produce:

  • Validation Summary
  • Performance Metrics
  • Risk Metrics
  • Robustness Assessment
  • Validation Outcome

Validation results remains available for future analysis.

Validation Outcome

Each validation will produce an overall business outcome.

Typical outcomes include:

  • Passed
  • Passed with Observations
  • Failed

Validation outcomes will support deployment decisions.

Validation History

Historical validation activities is preserved.

History includes:

  • Strategy Version
  • Validation Method
  • Validation Configuration
  • Historical Dataset
  • Validation Outcome
  • Execution Timestamp

Historical records remains immutable.

Business Rules

  • Every validation will reference one approved strategy version.
  • Validation does not modify strategy logic.
  • Validation does not modify optimisation results.
  • Validation will never interact with live trading.
  • Historical market data remains unchanged.
  • Validation results is reproducible.
  • Historical validation records will never be deleted.

Audit Requirements

The platform will maintain an audit trail for validation activities.

Audit events includes:

  • Validation Creation
  • Configuration Changes
  • Validation Execution
  • Result Generation
  • Validation Outcome
  • Historical Archive

Audit records remains immutable.

Out of Scope

The following are outside the scope of this module:

  • Live Trading
  • Order Execution
  • Broker Connectivity
  • Strategy Editing
  • Parameter Optimisation
  • Portfolio Management

These responsibilities belong to their respective business modules.