EZ

Eduzan

Learning Hub

Eduzan
Eduzan / 09 Portfolio Management

PORT 6 – Backtesting and Simulation

Worked examples are fully visible. Check-yourself items are study aids you can reveal one at a time.

Portfolio managers constantly propose new ideas: a valuation screen, a momentum overlay, a factor combination built for diversification. Before any of them reach client capital, the manager needs evidence that the idea has merit. This reading develops four complementary techniques for building that evidence. Backtesting asks how a strategy would have performed had it been run over a historical period. Historical scenario analysis narrows that question to specific historical episodes, such as a recession or a stretch of unusually high volatility. Simulation steps outside history altogether and explores how a strategy would behave in a hypothetical environment chosen by the analyst, which matters because history is only one realised path out of many that could have occurred. Sensitivity analysis, usually paired with simulation, tests how much the conclusions change when a key modelling assumption is varied.

These techniques have become far more accessible than they once were. A CFA Institute survey of close to 250 analysts, portfolio managers and private wealth managers found that half had run a backtest on an investment strategy within the previous twelve months. Wider access to the software has not reduced the importance of understanding what these tools assume, where they mislead, and how to read their output. If anything the stakes are higher, because a manager can now produce an impressive-looking backtest without having thought through any of that.

Backtesting rests on an implicit assumption: that the future will resemble history at least somewhat. Because that assumption is imperfect, a strategy that performs poorly in a backtest could still deliver excess returns going forward, and a strategy that performs well in a backtest could still fail to do so later. In practice, however, few investment committees will approve a strategy that cannot clear a backtest, so backtesting functions as close to a screening hurdle regardless of how carefully the theoretical caveats are worded. It suits quantitative and systematic strategies most naturally, because their rules translate directly into a historical simulation, but fundamental managers use it too, commonly to check whether a valuation or quality criterion would have added value before building it into a stock screen.

Three steps, always in sequence

Every backtest proceeds through the same three stages, regardless of how simple or elaborate the underlying strategy is: strategy design, historical investment simulation, and analysis of the backtesting output.

Figure 1: The three stages of a backtest
Strategy design Historical investment simulation Analysis of backtest output
Every backtest, however elaborate, decomposes into these three stages: set the rules, run the rules through history, then read the output.

Strategy design and its key parameters

Strategy design begins with an investment hypothesis: a trading rule, a security selection criterion, or a portfolio construction method believed to earn superior risk-adjusted absolute return or excess return against a benchmark. That hypothesis must then be translated into rules precise enough to run through history, which requires the analyst to fix several parameters.

The investment universe is the full set of securities eligible for the strategy. Academic researchers commonly combine the Compustat/Worldscope and CRSP databases, but practitioners more often use the constituents of well-known broad market indexes, such as the Russell 3000 for the United States, the S&P/TSX Composite for Canada, MSCI China A for mainland China, and the S&P Global Broad Market Index for other markets.

The return definition matters once the universe crosses borders. A global strategy has to settle on a currency convention: either translate every return into one reference currency, typically the manager’s home currency, or leave returns denominated locally. The choice usually tracks whether the manager hedges currency exposure; a manager who does not hedge tends to backtest in single-currency terms so that the reported results already embed the currency risk the strategy will actually carry.

The rebalancing frequency is most often monthly, though higher and lower frequencies both appear in practice. Rebalancing more often raises transaction costs, and daily or higher-frequency data introduces its own distortions: bid–offer spreads, trading that is not synchronised across time zones, and gaps from holidays that differ by country. Because many apparent market anomalies disappear once realistic transaction costs are applied, an analyst presenting backtest output should always state plainly whether costs are included.

The start and end date pulls in two directions. A longer history gives more statistical confidence, but financial data are not stationary, so a long-run average can obscure how a strategy behaved in specific regimes. The standard remedy is to supplement a long backtest with historical scenario analysis of shorter, discrete regimes, covered later in this reading.

Example 1 · Worked

Sarah Koh is building a value strategy for SWF Fund’s investment committee. The goal is superior risk-adjusted absolute return, and the hypothesis is that cheaper stocks outperform more expensive ones. Koh operationalises “cheap” using trailing earnings yield rather than the price-to-earnings ratio, because P/E cannot be computed or sensibly interpreted when earnings per share is zero or negative, whereas earnings yield can be computed whenever price and EPS data exist.

Koh’s key parameters
PORT 6 – Backtesting and Simulation — table 1
ParameterSpecification
Investment universeRussell 3000 (US) and S&P Europe BMI, total returns hedged to USD
Start and end dateJanuary 1986 to May 2019
Rebalancing frequencyMonthly, including transaction costs; returns reported on a 12-month moving average basis
1. What should concern the investment committee most about this design?
Solution. The 1986–2019 window spans multiple recessions, several currency regime changes, and a wide range of interest rate environments, so the underlying data are non-stationary. The long-run average return could easily mask very different behaviour in different sub-periods, which is exactly why the results should be supplemented with historical scenario analysis rather than accepted on the strength of the full-period average alone. The design makes no directional bet on the dollar against the euro, since returns are hedged back to USD, and earnings yield is computable for essentially any stock with positive EPS, so neither of those is the live concern.
2. If Koh switched rebalancing from monthly to weekly, what would happen to transaction costs, and why?
Solution. Transaction costs would rise. Rebalancing frequency governs how often the portfolio is refreshed to reflect updated earnings yields across the universe, and more frequent refreshes require more trading. Moving in the other direction, from monthly to quarterly, would lower transaction costs for the same reason, since fewer changes in a stock’s ranking would trigger a trade.
3. Suppose Koh instead tested this strategy over a single two-year window. What would be lost?
Solution. A short window is likely to sit entirely inside one business cycle, inflation regime and interest rate environment, so the result describes only how the strategy performed under those specific conditions. It is not automatically true that a short window covers multiple macroeconomic regimes; regimes typically last several years, so the more realistic risk with a short backtest is the opposite, an overly narrow slice of experience presented as if it were general.
End of lesson.