How To Read Backtest Report
A backtest report is only useful if you know what each part of the page is saying. The current report view is designed to answer four questions: did the strategy make money, under what conditions, on which trades, and with which exact saved configuration.
What this is
This article explains how to read the current backtest detail page from top to bottom.
When to use it
Use this article if:
- a backtest completed and you need to interpret the result
- you want to compare a strong and weak report correctly
- you want to understand what the report does not guarantee about live performance
Before you start
Important current product behavior:
- a backtest record can be pending , running , completed , or failed
- the page can show progress banners, failure banners, and warning banners
- the report is organized into four tabs:
- Result
- Charts
- Deals
- Settings
Step by step
Step 1: Read the top summary before opening details
At the top of the page, start with the hero stats:
- Net
- Final Balance
- Win Rate
- Max Drawdown
If the page shows warnings, read them immediately. In the current product, warnings can indicate things such as:
- TradingView signal rules ignored in runtime
- funding-rate data unavailable
- open-interest data unavailable
- all-coins caveats
Step 2: Use the Result tab to judge quality, not only profit
The Result tab gives the main performance summary. In the current UI, it includes metrics such as:
- gross PnL
- net PnL
- commission
- funding
- return
- Sharpe ratio
- profit factor
- MFE
- MAE
It also includes execution context and deal-summary style blocks that help you answer:
- which market and side were tested
- which period was covered
- how many trades were closed
- how exit reasons were distributed
Step 3: Use the Charts tab to inspect structure, not only totals
The Charts tab helps you see how the report was produced.
In the current page, it includes:
- a candle chart with trade markers
- timeframe controls
- a cumulative equity or profit view
- a focused panel for the selected trade
Use this tab to check whether the equity curve is steady, clustered, or dominated by a few isolated trades.
Step 4: Use the Deals tab to inspect individual trades
The Deals tab is where you inspect actual trades instead of only aggregates.
The current page provides:
- a deals table
- sorting by fields such as net, duration, funding, MFE, and MAE
- expandable rows with additional facts
- execution details for the selected trade
Use this tab to answer:
- which trades made or lost the most
- how long trades stayed open
- why they exited
- how much fees or funding changed the result
Step 5: Use the Settings tab to confirm what was actually tested
The Settings tab is the audit trail for the report.
It includes:
- a configuration snapshot
- run metadata
- structured settings sections for entry, grid, exit, and risk
- raw JSON views for the stored record
Always finish here before making a launch decision. A strong report on the wrong symbol, side, or market type is still the wrong report for your intended bot.
What you should see
After reading the report, you should be able to state:
- whether the backtest completed successfully
- how profitable it was after costs
- how severe the drawdown was
- what kinds of trades generated the result
- which exact configuration produced the report
Common mistakes
- looking only at net profit and ignoring drawdown, costs, and trade quality
- ignoring warning banners and treating the report as a perfect live simulation
- reading Charts without checking Deals
- launching from a report before confirming the Settings snapshot
- treating one strong trade or one strong period as proof that the whole strategy is stable
Related articles
- Run Backtest
- Why Backtest Is Required Before Launch
- Grid Settings
- Trade Journal And Export