Editor

Open the intended strategy and choose Compile Strategy. Diagnostics appear in XTester Build; double-click an error to open its source line. Stop a running simulation before rebuilding, or explicitly accept the build command’s stop confirmation.

Application screenshotXTester 1.0.0-preview.1

Enlarge screenshot

1. Compiler error

Add Package and Remove Package change strategy dependencies; installing dependencies is a separate action. Check the requirements of the selected language adapter: C# has the fullest contract, while other adapters may expose only part of it.

The library can open a strategy, open it in a new window, rename, duplicate, reveal its folder, archive or restore it. Deleting and forgetting a recent entry are different actions: inspect the confirmation and path.

Portfolio folders organize members. Include, exclude and only-selected actions determine the strategies participating in a portfolio run. Review individual strategy settings before running the portfolio.

Open the strategy log to inspect execution messages. Filtering, search, clearing and autoscroll are available. Retain the error text and time before clearing a log needed for a support report.

Application screenshotXTester 1.0.0-preview.1

Enlarge screenshot

The breakpoint list can navigate to, rename or delete a breakpoint, disable all or delete all. Automatic pause at chart breakpoints belongs to simulation; stopping in source code belongs to the debugger.

Application screenshotXTester 1.0.0-preview.1

Enlarge screenshot

Stepping and pausing do not constitute a completed backtest. Compile changed code and run a new calculation before comparing results.

Add Package to Strategy… attaches a library to the current project. Supported sources include folders, Git repositories and NuGet for the appropriate scenario. Check active folder and language before confirming.

XTester packages live in xtester_packages inside the project; xtester.packages.json records their composition. A library installed somewhere on the system is not automatically part of this portable project.

Install Project Dependencies prepares declared requirements. Python and npm use project environments; downloads can require internet access. Read the installation action/error rather than repeatedly compiling while a library is missing.

Remove Package from Strategy… changes project composition. Fix imports or restore the required dependency if source still refers to a removed library, then compile.

Retain library versions and package composition when comparing runs or building a robot. Successful installation does not establish correct use or equivalent results with another version.