Backtest logic and execution
Learn more about how we execute trades in the backend and the principles we use to give you the most accurate information for your trades.
Last updated
Was this helpful?
Learn more about how we execute trades in the backend and the principles we use to give you the most accurate information for your trades.
Last updated
Was this helpful?
Well done! If you're reading this article then that means you've backtested at least one of your strategies. If you haven't then we'd highly recommend you test it at least once and then come back to this article for context.
We've divided the backtest into two categories depending on what your risk appetite is : 1. Risk Tolerant 2. Risk Averse
By default - The backtest runs on a simultaneous execution mechanism.
If you are more risk averse or you do not want to take risk then we recommend you to run backtest on a sequential execution basis. Sequential execution basis
Sequential execution means that a new order only opens if the existing order in the queue has been closed. This will result in less number of trades being generated in the report, however, you will get better clarity on key metrics like holding period, and drawdown. Additionally, we categorise this into Risk Averse category since the exposure at a time is limited to the Stoploss calculated by the strategy.
Simultaneous execution means that a new order opens whenever a signal is generated. Doesn't matter what the status of the previous order(s) is.
This will result in high number of trades being generated in the report, however, you will get less clarity on key metrics like holding period, and drawdown. Additionally, we categorise this into Risk Tolerant category since the exposure at a time can be maximum (100% capital allocated to the strategy/open orders).