Skip to main content

Backtesting

Backtesting runs your complete strategy - signals plus the trade they execute against historical market data, so you can evaluate performance before risking anything.

Plan requirement

Backtesting is included on both Signal Plans: 5 backtests a week (resets every Monday) on the 1 Month plan, unlimited on the 6 Month plan. See Pricing & Plans.

Signals say when - a trade says what​

Your signal defines when to enter and exit. To backtest, you must also define what gets traded when the signal fires: which legs (options/futures), how many lots, and any risk settings. This trade definition uses AlgoTest's standard Strategy Builder (the same one used for time-based strategies - you may see it referred to as a "920 strategy" elsewhere; it's just a trade configuration).

warning

The 920/AlgoTrade page itself is for time-based strategies. For signal strategies, you only use the Strategy Builder to define the trade - you never need to activate anything from the 920 page. See the FAQ.

Your weekly quota​

The backtest entry point shows "X of 5 Signals backtests left this week" plus the day it resets (Monday), if you're on the 1 Month plan. On the 6 Month plan it shows unlimited.

  • A backtest consumes 1 credit only when it completes successfully - a failed or errored run doesn't cost you anything.
  • Re-running the same strategy (even unchanged) consumes another credit - there are no free re-runs.
  • Because a Signals backtest runs against a connected 920 strategy, each run also uses 1 credit from your separate 920 free-backtest pool (25/week). These two counters are shown separately in the app so a Signals backtest never looks like it ate into your 920 credits, and vice versa - see Pricing & Plans for how the two pools work.
  • Running out for the week? You'll see a clear "0 of 5 left" state with two options: wait for the Monday reset, or upgrade to the 6 Month plan for unlimited backtesting immediately.
Watchlist strategies

A watchlist backtest uses one backtest per underlying from each pool, so a 5-stock watchlist uses 5 Signals backtests and 5 920 backtests. On the 1 Month Plan, a watchlist with more underlyings than your remaining weekly Signals backtests can't be backtested.

Run a backtest​

  1. On your signal, click Backtest Result (use Maximize for full screen).

    Backtest tab

  2. Click Connect Now, then either pick an existing strategy from your account or click Create Strategy.

    Connect a strategy

  3. If creating new, configure the trade in the Strategy Builder:

    • Index and Timings — index
    • Leg Builder — segment, expiry, lots, position (buy/sell), option type, strike criteria; click Add Leg for each leg
    • Optional risk settings — Target Profit, Stop Loss, Simple Momentum, and overall-strategy settings (Overall SL/Target, Lock Profit, Trail SL)

    Click Save and Continue.

    Strategy builder with leg configuration

  4. Select the Backtest Period and click BackTest.

    Selecting backtest period

Reading the results​

Year-wise Returns - performance per year: consistency check across different market regimes.

Year-wise returns

Max Drawdown - the largest peak to trough decline: the worst losing stretch you'd have sat through.

Max drawdown

Strategy Stats - total P&L, number of trades, win rate, average profit/loss, risk-reward ratio, and winning/losing streaks.

Strategy stats overview

Full Report - daywise trade logs, downloadable as CSV, sortable by P&L or day.

Downloadable full report

What to look for​

MetricQuestion it answers
Win rate + avg win/lossDoes the edge come from many small wins or few large ones?
Max drawdownCould you psychologically and financially survive the worst stretch?
Year-wise returnsDoes it work across market regimes, or only in one lucky year?
Number of tradesEnough trades to be statistically meaningful (not 5)?

Save the strategy​

Satisfied? Click Save Strategy, name it, and save. It will appear in Saved Signals, ready to deploy.

Save strategy dialog

Backtest ≠ guaranteed live results

Backtests don't capture slippage, order fills, and execution latency the way live markets do. Always forward test before going live. See why results can differ.