Strategy wizard
Choose how to start: create a strategy from scratch, convert existing code or open a saved strategy.
Strategy wizard
Command Palette → XTester: New Strategy….
- Create from scratch starts a new strategy: choose a name and language and create its files.
- Transfer existing code loads an existing strategy and guides you through conversion.
- Open a saved strategy lets you choose an existing strategy on this computer.
- Create a new strategy from scratch.
- Transfer existing code from another platform.
- Open an already saved strategy.
On the first screen, choose one of three ways to begin. The wizard opens the next step for that choice.
Portfolio
The strategy library lists the strategies under the chosen root. The root is set by its own command and kept in settings, so the list survives a restart.
- Portfolio and strategy files.
- Source of the selected strategy.
A strategy can be opened, opened in a new window, renamed, duplicated, deleted, and revealed in the file manager. The recent list keeps at most ten entries, newest first.
Choose the Right Starting Path
Create from Scratch starts a new strategy or a project into which you can paste a complete checked C# example. It creates a project folder; instrument and calculation period are chosen later in Simulation.
Import Existing Code is the conversion route for logic from another platform. It differs from opening an existing XTester folder. Converted output still needs compilation and historical validation.
Open Saved Strategy opens an existing project folder with its strategy manifest. A standalone robot application, installation archive and folder project are different outputs; an unrelated EXE is not a strategy source file.
The wizard obtains its language list from your build’s engine. Use a template for an offered language: renaming the tutorial C# file to Python or Pine does not convert it. Some languages/libraries need tools and dependencies prepared first; missing tools differ from a strategy-logic error.
Check the Created or Opened Project
After the wizard, check active strategy name, folder and language. Open the entry file, save edits and compile. Presence in the library does not establish successful compilation.
- Check the active project and entry file.
- Save source and compile.
- Select data and historical run conditions.
- Compare log and result with the code’s intended behavior.
Then choose history and simulation conditions. The verified first example explains its expected log and zero trades. To distribute your own standalone application, use Own Launcher (White Label)….
Related commands
Command Palette reference
Find these actions by name in the Command Palette; availability depends on the current project and operation state.
xtester.createStrategyProjectxtester.strategyWizardxtester.strategyWizard.creatextester.strategyWizard.open