Backtests are the main validation gate in SteadyEdge. They let you queue a historical run, review the result, and decide whether a bot configuration is strong enough to keep refining or prepare for live use.

What this is

This overview explains what the Backtests And Analytics section covers, how runs move through the system, and where to open result details.

When to use it

Use this page if:

you want to validate a bot before live use
you need to understand where backtest runs appear after launch
you are trying to distinguish historical validation from live analytics

Before you start

To run a backtest in the current product, you need:

a verified email address
a saved bot or an existing bot you can backtest
a plan that allows the selected period
remaining daily backtest quota if your plan is capped

Step by step

Step 1: Launch a run from a bot

SteadyEdge runs backtests from a bot context, not from an empty analytics page.

The most common entry points are:

Run Backtest on a bot row in the dashboard
Run Backtest in the editor for an existing saved bot

Step 2: Choose a valid period

The current product offers period-based selections such as 1, 3, 6, or 12 months. Some flows also allow custom start and end dates. Your plan determines which ranges are available.

Step 3: Watch the run lifecycle

New runs move through the normal lifecycle:

pending
running
completed
failed

While running, the detail page can also show progress stages such as syncing, loading candles, running, computing metrics, and saving.

Step 4: Open the result page

After the run starts, the platform links you to the backtest detail page. The Backtests workspace also keeps searchable history with filters for bot, status, date range, and sort order.

Step 5: Keep backtests separate from live analytics

Backtest history lives in Backtests. Live and operational analytics live in Metrics, especially in the Metrics and Trade Log tabs. Use both, but do not treat them as the same thing.

What you should see

You should be able to identify:

run status
tested period
bot used
gross and net PnL
total trades
result detail page for completed runs

Common mistakes

assuming a completed save automatically creates a backtest
confusing live analytics with historical backtest output
selecting a period your plan does not allow
assuming a pending run is broken when it is only queued