> For the complete documentation index, see [llms.txt](https://guida-2.gitbook.io/guida-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guida-2.gitbook.io/guida-docs/getting-started/testing-your-strategy.md).

# Testing Your Strategy

The single biggest advantage Guida gives you is the ability to **prove a strategy before you trust it**. There are two complementary ways to do this: backtesting and paper trading. Use both.

## Backtesting: how would this have done?

Backtesting runs your strategy against **historical market data** and simulates every trade it would have made. In seconds, you get a picture of how the idea would have performed over months or years of real market conditions — including the ugly ones.

After a backtest, Guida shows you metrics like:

| Metric               | What it tells you                                                                                 |
| -------------------- | ------------------------------------------------------------------------------------------------- |
| **Total return**     | How much the strategy would have made or lost overall.                                            |
| **Win rate**         | The share of trades that ended profitably.                                                        |
| **Maximum drawdown** | The worst peak-to-trough drop along the way — your "how bad did it get?" number.                  |
| **Equity curve**     | A chart of your simulated balance over time, so you can *see* the ride, not just the destination. |

> **Read drawdown carefully.** A strategy with great returns but a stomach-churning drawdown is one most people would abandon at the worst possible moment. The best strategy is one you can actually stick with.

A backtest is a powerful sanity check — but remember, **past performance never guarantees future results.** It tells you whether an idea was sound historically, not whether it will work tomorrow.

## Paper trading: how is it doing right now?

Paper trading runs your strategy **forward, on live market prices, with simulated funds.** Nothing is risked, but everything else is real: real prices, real timing, real market behavior.

Paper trading answers the questions a backtest can't:

* Does the strategy trigger when I actually expect it to, in live conditions?
* How does it feel to watch it operate day to day?
* Does its behavior match what the backtest promised?

It's the bridge between "looked good on history" and "I'm ready to trust this with real capital." We recommend paper-trading any new strategy for a meaningful stretch of live market conditions before considering going live.

## The healthy testing workflow

1. **Backtest** to check the idea is fundamentally sound.
2. **Refine** based on what you learn — adjust thresholds, sizing, and exits.
3. **Paper-trade** the refined version on live prices.
4. **Compare** the paper results to the backtest. Do they roughly agree? Good.
5. **Only then** consider deploying it live (in a later release).

## A word on realistic expectations

Testing is about building *justified* confidence, not certainty. Markets change, and no amount of testing removes risk. What testing does is make sure you're not fooling yourself — that a strategy has a real, demonstrable rationale before you rely on it.

***

**Next:** [Going Live →](/guida-docs/getting-started/going-live.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://guida-2.gitbook.io/guida-docs/getting-started/testing-your-strategy.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.