--- title: "Getting Started" description: "An algorithm that has a proven track record can provide you with more confidence for live trading." canonical: https://www.quantconnect.com/docs/v2/local-platform/backtesting/getting-started markdown: https://www.quantconnect.com/docs/v2/local-platform/backtesting/getting-started.md language: python source: https://github.com/QuantConnect/Documentation/tree/master/02%20Local%20Platform/10%20Backtesting/01%20Getting%20Started modified: 2026-10-29 index: https://www.quantconnect.com/llms.txt --- # Getting Started [Documentation](https://www.quantconnect.com/docs/v2.md) > [Local Platform](https://www.quantconnect.com/docs/v2/local-platform.md) > Backtesting > Getting Started > Code examples are shown in Python. Append `?lang=csharp` to this URL for the C# version of this page. ## Introduction Backtesting is the process of simulating a trading algorithm on historical data. By running a backtest, you can measure how the algorithm would have performed in the past. Although past performance doesn't guarantee future results, an algorithm that has a proven track record can provide investors with more confidence when deploying to live trading than an algorithm that hasn't performed favorably in the past. If you run local backtests, you can leverage your local data and hardware. ## Run Backtests Local Platform provides multiple [deployment targets](https://www.quantconnect.com/docs/v2/local-platform/key-concepts/deployment-targets.md) to enable you to run backtests on-premises and in the cloud. To run a backtest, [open a project](https://www.quantconnect.com/docs/v2/cloud-platform/projects/getting-started.md#02-View-All-Projects) and then click the ![](https://cdn.quantconnect.com/i/tu/local-platform-backtest-icon.png) / ![](https://cdn.quantconnect.com/i/tu/cloud-platform-backtest-icon.png) **Backtest** icon. If the project successfully builds, "Received backtest backtestName request" displays. If the backtest successfully launches, the IDE displays the [backtest results page](https://www.quantconnect.com/docs/v2/cloud-platform/backtesting/results.md) in a new tab. If the backtest fails to launch due to coding errors, the new tab displays the error. As the backtest executes, you can close Local Platform and Docker Desktop without interfering with the backtest. Just don't quit Docker Desktop. ## View All Backtests Follow these steps to view all of the backtests of a project: 1. [Open the project](https://www.quantconnect.com/docs/v2/local-platform/projects/getting-started.md#04-Open-Projects) that contains the backtests you want to view. 2. In the top-right corner of the IDE, click the ![](https://cdn.quantconnect.com/i/tu/local-platform-backtest-results-icon.png) / ![](https://cdn.quantconnect.com/i/tu/cloud-platform-backtest-results-icon.png) **Backtest Results** icon. A table containing all of the backtest results for the project is displayed. If there is a **play** icon to the left of the name, it's a [backtest result](https://www.quantconnect.com/docs/v2/local-platform/backtesting/results.md). If there is a **fast-forward** icon next to the name, it's an [optimization result](https://www.quantconnect.com/docs/v2/local-platform/optimization/results.md). The Platform column displays the [deployment target](m/docs/v2/local-platform/key-concepts/deployment-targets) of the backtest. ![All backtest table view](https://cdn.quantconnect.com/i/tu/local-platform-view-all-backtests.png) 3. (Optional) In the top-right corner, select the **Show** field and then select one of the options from the drop-down menu to filter the table by backtest or optimization results. 4. (Optional) In the bottom-right corner, click the **Hide Error** check box to remove backtest and optimization results from the table that had a runtime error. 5. (Optional) Use the pagination tools at the bottom to change the page. 6. (Optional) Click a column name to sort the table by that column. 7. Click a row in the table to open the results page of that backtest or optimization. ## Rename Backtests We give an arbitrary name (for example, "Smooth Apricot Chicken") to your backtest result files, but you can follow these steps to rename them: 1. Open the [backtest history](https://www.quantconnect.com/docs/v2/local-platform/backtesting/getting-started.md#03-View-All-Backtests) of the project. 2. Hover over the backtest you want to rename and then click the **pencil** icon that appears. ![Rename backtest navigation](https://cdn.quantconnect.com/i/tu/rename-backtest-result.png) 3. Enter the new backtest name and then click **OK**. To programmatically set the backtest name, call the `set_name` method. ```python self.set_name("Backtest Name") ``` For more information, see [Set Name and Tags](https://www.quantconnect.com/docs/v2/writing-algorithms/initialization.md#97-Set-Name-and-Tags). ## Results The backtest results page and the `backtests` directory in your project show your algorithm's performance. Review the results to see how your algorithm has performed during the backtest and to investigate how you might improve your algorithm before live trading. For more information about backtest results, see [Results](https://www.quantconnect.com/docs/v2/local-platform/backtesting/results.md). ## Algorithm Lab Backtests For information about cloud backtests through the Algorithm Lab, see [Getting Started](https://www.quantconnect.com/docs/v2/cloud-platform/backtesting/getting-started.md). ## Get Backtest Id To get the backtest Id, see the first line of the [log file](https://www.quantconnect.com/docs/v2/local-platform/backtesting/results.md#13-Logs). An example local backtest Id is 1710698424. An example cloud backtest Id is 8b16cec0c44f75188d82f9eadb310e17.