What is Backtest in FYERS Automate?
Backtest in FYERS Automate helps you test an automation strategy using historical market data before running it live. It shows how the strategy would have performed in the past based on your selected time period, capital, slippage, and order placement logic.
Backtest is available on FYERS Web and the FYERS App. It supports Equity Cash, Equity Derivatives (F&O), and MCX Commodities.
Backtest overview
A backtest runs your Automate strategy on historical data and generates performance results for the selected period. You can use it to review whether your strategy would have generated trades, profits, losses, drawdowns, or other performance outcomes.
| Section | Purpose |
|---|---|
| Summary | Shows key performance metrics such as returns, trades, profit factor, volatility, and Max Drawdown. |
| Performance Chart | Shows Capital Deployed and Drawdown over the selected period. |
| Backtest Calendar | Shows period-wise P&L, total trades, positive trades, and negative trades. |
| Trades | Shows individual backtested trades. |
| Net View | Shows results after brokerage, taxes, and other charges. |
| Gross View | Shows results before brokerage, taxes, and other charges. |
| Export Tradebook | Downloads the backtested trades as a CSV file. |
Requirements and settings
To run a backtest, the automation workflow must include an order placement action. If the workflow only generates alerts and does not place orders, a backtest cannot be run.
The automation must also be scheduled before running a backtest. Without a schedule, the backtest option cannot be used.
During backtest configuration, you need to enter:
| Field | Meaning |
|---|---|
| Time Period | Historical date range used for the backtest. |
| Initial Capital (₹) | Starting capital used for the backtest. |
| Slippage (%) | Expected difference between the intended and executed price. |
Slippage can be edited while running the backtest. It can also be modified after the results are generated to view adjusted results.
What if...
| Scenario | Solution |
|---|---|
| The workflow only sends alerts | Backtest cannot be run. |
| No schedule is set | Backtest cannot be run. |
| Slippage is changed after results are generated | Results are recalculated based on the updated slippage. |
| Net View is selected | Results include brokerage, taxes, and other charges. |
| Gross View is selected | Results exclude brokerage, taxes, and other charges. |
| Tradebook is exported | Backtested trades are downloaded as a CSV file. |
Backtest results are based on historical data and selected assumptions. They do not guarantee future performance. Live results may differ due to market conditions, liquidity, execution price, charges, and other real-time factors.
Related Articles
How do I run a backtest in FYERS Automate?
You can run a backtest from the Automate workflow after the strategy is ready for testing. The backtest uses your selected date range, capital, and slippage value to simulate how the strategy would have performed using historical data. Use this ...How are orders and prices matched in FYERS Automate Backtest?
Backtest on FYERS Automate simulates order execution using historical market data. The orders in a backtest are considered as market orders, and the execution price for the market order is taken as the 1-minute candle close price. This helps the ...How do I export the backtest tradebook?
The Export option in FYERS Automate lets you download the trades generated during a completed backtest. The file is exported in CSV format, so you can open it in a spreadsheet tool for detailed review. Use this option when you want to analyze ...How do I edit Backtest Configuration after results are generated?
After a backtest result is generated in FYERS Automate, you can modify only the slippage (%) value from the existing result. The result updates based on the revised slippage. For any other change, such as the time period or strategy workflow, you ...Why do backtest results differ from live strategy performance?
Backtest results in FYERS Automate are based on historical market data and the inputs selected during the test, such as date range, initial capital, and slippage. Live strategy performance may differ because real orders are affected by current market ...