Read a Backtest result

Check the context first

Open a completed run from Backtest Center. Read the strategy and version, mode, period, initial capital, instruments and execution assumptions. This is the configuration recorded for that run. Editing the current strategy does not change the historical result.

Treat the results as a simulation of those conditions. A high return is not sufficient evidence that a strategy works reliably. Costs, sample size, risk and changes between runs matter.

Navigate the report

• Overview shows summary performance and capital or equity, drawdown and monthly returns. Portfolio results can also show weights and leverage.
• Metrics provides performance and risk detail. Tactical breakdowns can distinguish all, long and short trades; Portfolio includes allocation-oriented analysis. Read the unit and availability of each value.
• Trades in Tactical follows execution and position records. Rebalances in Portfolio shows allocation changes. Chart and table views complement each other.
• Debug shows recorded node events and eligible replay actions. See debug and replay.

A section can be absent or unavailable when that run did not produce the required data. Result tables may be paginated or bounded: read totals and truncation notices before interpreting visible rows as the whole result.

Understand the main measures

Use the metric descriptions and units in the result for the exact meaning. Missing, not applicable, insufficient data and unsupported calculations are not zero. An alert-only strategy may complete without trades; it cannot establish order execution or profitability.

Understand data availability

A retained summary can remain readable after detailed result data expires. Saved bookmarks do not stop expiry. Price candles, detailed artifacts, static node summaries and full debug replay have different requirements; one available chart does not prove all data is retained.

When a panel shows expired, pending, unavailable or a load error, follow that panel’s explanation. Retry a temporary transport error. Expired data cannot be recovered by repeatedly refreshing. An unavailable value is not evidence of a zero return or an event that never happened.

Use debug to explain a decision

Open Debug, then filter the recorded timeline by all events, errors or snapshots. Use pagination to inspect later events. A failed run’s reason and support reference help identify the problem; avoid sharing private identifiers publicly.

Full replay requires an eligible plan, debug enabled for that execution and available debug data. It opens a historical graph in read-only mode. A static overlay or summary can be useful even when full replay is unavailable.

Decide the next experiment

Write down what you changed and which outcome you want to examine. Return to the current strategy, create a checkpoint when useful, make the change and save. A new Backtest creates a separate result. Use comparison to review differences in both configuration and outcomes.