Getting Started
Create your first strategy, download candles and find your way around XTester.
A workspace for strategy development
XTester Studio combines its built-in editor with the XTester strategy tools. Help is published on the XTester website and is loaded when you open it in the app. Reading online help requires an internet connection; it does not start the calculation engine.
The interface supports English and Russian. Open the Manage gear menu and choose Configure Display Language, or find the same command in the Command Palette. Choose English, Russian, or Use System Language; this is the shared language choice for the editor and XTester panels. Changing it requires a restart, so finish running downloads and simulations first. Use Preferences: Color Theme to change the appearance. Your saved choices are kept between launches.
Clear “Show on startup” at the bottom of the welcome window to stop it opening automatically. Your choice is saved. To enable it again, open XTester Settings → Interface and select “Show the welcome window on startup”. It is enabled by default, and the welcome window can still be opened manually.
Your first backtest
- Open an existing strategy folder or run New Strategy from the Command Palette. The wizard creates a manifest and source files for the selected language; add your strategy logic before running a backtest.
- Use the XTester Data view to choose an exchange, market, and instrument. Download the history required for your test. Data downloads require network access.
- Compile the strategy, open the simulation settings, choose a covered date range, and start the backtest.
- Open the results to compare the price chart, equity, drawdown, summary metrics, and trades.
EasyTrading.pw account
XTester Studio signs in with your EasyTrading.pw account through the system browser: Sign In on the account entry at the right of the status bar, or the same command in the Command Palette. The browser opens the EasyTrading sign-in page, then returns to a local xTester · EasyTrading page.
- Studio sign-in command
That page shows Completing sign-in… while Studio exchanges the code, asks the cabinet for your user and saves the session; Sign-in complete appears only once Studio itself is signed in. A closed browser tab never means success by itself — the account entry in Studio is the source of truth.
Switch Account (the account entry, or the Command Palette) opens the account chooser of the browser while the current account keeps working. The new account replaces the old one only after the same checks as a sign-in; cancelling the chooser, closing the tab or an error on the server leaves the current account signed in. Sign Out is local: Studio forgets the session on this computer and the browser keeps its own sign-in.
Between launches Studio keeps only the refresh token, in the secure storage of the operating system (Keychain on macOS, Credential Manager on Windows, the secret service on Linux); the access token lives in memory. Windows of the same profile share one account: a switch made in one window is picked up by the others. If the session was revoked on the server, the account entry asks you to sign in again.
Commands and keyboard shortcuts
F1 opens the Command Palette. Search by action name, such as Open Help or Compile Strategy. F1 is not reassigned to a help topic.
Open Help → Keyboard Shortcuts to inspect or change bindings. On Windows and Linux the Command Palette also uses Ctrl+Shift+P; on macOS use Shift+Command+P. Context help opens the topic relevant to the current panel.
With a recognized strategy project, the default Ctrl+Shift+B binding compiles the strategy. F5 starts the simulation when no debugger is active and no run is in progress: open editors are saved, the strategy is compiled and the run begins; a paused run resumes without recompiling. Shift+F5 stops the run. F10 steps a paused simulation; when stopped, it opens Simulation settings, where you can review the conditions before pressing Start. Check Keyboard Shortcuts if another extension or a custom binding uses the same keys.
If a simulation or strategy debugging session is running or paused, Ctrl+Shift+B first asks “Stop the simulation and compile the strategy?” (while debugging, “Stop debugging and compile the strategy?”): the session is stopped and reset to the start of the period. Stop and Compile stops the session and compiles the strategy; Cancel neither compiles nor touches the session. In the XTester Build output channel, a double-click on an error line opens the file and selects that line.
Extensions
Use Help → Extensions to view installed extensions. The XTester catalog offers a curated set of recommendations; downloading or updating extensions requires a network connection.
Third-party extensions run their own code and can have separate licenses, accounts, or service requirements. Install only extensions you trust. Opening help does not install or activate the trading engine.
Related commands
Command Palette reference
Find these actions by name in the Command Palette; availability depends on the current project and operation state.
xtester.openFirstStrategyGuide