Overview
This page explains how we use back-testing as part of the Guardian TradeBot development process.
The purpose of our analysis is not to present a fixed trading configuration or suggest that one strategy will remain unchanged indefinitely. Markets change, execution conditions change, and individual signal sets can perform differently across different periods. For that reason, our strategy selection process is evidence-based and adaptable.
Rather than relying on emotion, instinct, or a single preferred setup, we analyse signal performance, compare results across different conditions, and refine the system based on measurable outcomes.
Why back-testing matters
Even the best signals are only useful when paired with disciplined risk management, because no signal is right every time, and one badly managed trade can undo a long run of correct decisions.
Back-testing allows us to replay historical signal alerts and assess how those alerts would have performed under defined trade-management rules.
This helps us understand:
- how often signals produced useful trade opportunities
- how trades behaved after entry
- how fees affected the final result
- how drawdown developed over time
- whether performance was consistent or dependent on a small number of outlier trades
- whether a signal set remained useful across different market conditions
Back-testing does not guarantee future results. Its value is that it provides a structured way to test ideas before relying on them in live trading.
Trade outcome analysis, not just indicator testing
Our analysis is designed to assess trade outcomes, not just indicator signals.
Each batch of alerts can be processed as if it were a managed trade. The report can account for entry, exit logic, fees, target behaviour, trailing-stop behaviour, stop handling, time limits, and overall performance over the selected assessment window.
This gives a more realistic picture than simply asking whether price moved up or down after a signal.
Why slippage matters
Slippage is an important part of realistic strategy testing.
A back-test may show that price reached a target, but live execution can differ depending on liquidity, volatility, spread, exchange conditions, and how quickly price is moving at the time of entry or exit.
This is especially important for fast-moving signals. A strategy that looks strong on paper may become less attractive if the real entry price is consistently worse than the theoretical entry price.
For that reason, our analysis does not focus only on maximum theoretical returns. We look for strategies that remain practical after fees, execution differences, and conservative assumptions are considered.
Conservative interpretation
We treat back-testing as a decision tool, not a promise.
A strong report is useful because it shows that a strategy has passed a structured review. It does not mean the same result will repeat in the future.
The aim is to identify signal sets that have shown favourable behaviour, acceptable drawdown, and enough consistency to justify further testing or live deployment.
Example report
The linked report is an example of the type of internal analysis we produce.
It should not be read as the current live configuration, and it may not reflect the most recent strategy, fee assumptions, signal selection, or risk settings. It is included to show the structure of the analysis and the type of information reviewed when assessing strategy performance.
How to read the report
The report is designed to show both individual trade outcomes and wider strategy behaviour.
Key areas include:
- Batch Analysis Results — shows how each alert batch would have played out as a managed trade.
- Cumulative Target Summary — shows how often different target levels were reached.
- Potential Profit — estimates the weighted result after fees and execution assumptions.
- Overall Summary Statistics — summarises aggregate trade performance.
- Daily and Compounded Profit Curves — show how performance developed over time.
- Risk-Adjusted Metrics — assess consistency, volatility, expectancy, and drawdown.
- Drawdown Analysis — shows the depth and behaviour of losing periods.
- Period Performance Summary — highlights daily, weekly, and monthly performance patterns.
Strategy selection
Strategy selection is not static.
If a signal set performs well under current conditions, it may be used more heavily. If performance weakens, it can be reduced, removed, or replaced. This flexibility is central to the development process.
The goal is not to force one configuration to work forever. The goal is to keep testing, comparing, and improving based on evidence.
Important note on interpretation
Back-testing is not a guarantee of future returns.
The purpose of this page is to show that Guardian TradeBot is developed through structured analysis, conservative interpretation, and ongoing review. Performance data is used to guide decisions, but live trading always carries risk, and past performance is not a reliable indicator of future results.