Backtest
Does Initial Capital limit the trades taken during a backtest?
No. Initial Capital is used to calculate your strategy's performance, including returns, capital growth, and other performance metrics. It does not determine whether a trade can be executed during the backtest. If the strategy generates a trade based ...
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 ...
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 ...
Why do I need to schedule an automation before running a backtest?
A backtest in FYERS Automate runs the strategy based on its defined execution schedule. The schedule tells the system when the automation should be active during the selected historical period. Without a schedule, the system cannot determine when the ...
Why does my automation need an order placement action for backtest?
Backtest in FYERS Automate is designed to simulate how an automation strategy would have placed trades using historical market data. For this reason, the workflow must include at least one order placement action. If the automation only generates ...
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 understand the Backtest Summary?
The Backtest Summary gives a detailed view of how your automation performed during the selected backtest period. It helps you review returns, trade performance, risk, and capital movement before deciding whether to refine or run the strategy. Use ...
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 ...
Why are no trades shown in my backtest results?
If your backtest shows no matching trades found, it means the automation did not generate any trades during the selected backtest period. A backtest generates trades only when the workflow conditions are triggered during the selected historical ...
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 ...
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 ...
Is there a limit to the number of backtests I can run?
Yes. You can currently run up to 5 backtests per day in FYERS Automate. The daily limit applies to every backtest you start. Once you reach the limit, you must wait until it resets before you can run another backtest. Note: A backtest counts towards ...
How do I view previous backtest results in Backtest History?
Backtest History in Automate lets you view previously run backtest results for a strategy. This is useful when you want to compare earlier results, review past configurations, or check different strategy versions created after changes. Each time you ...