DevelopmentTrading strategy portfolios in XTester: shared capital, risk and the new Studio
Why strategies need to be tested on a shared balance. A look at risk allocation, a programmable orchestrator and the development of XTester Studio.
Blog
The XTester dev log
The XTester dev log — notes on features, releases and decisions under the hood.
Development
DevelopmentXTester Studio built on Code - OSS and XTester Engine
XTester Studio will combine the Code - OSS development environment with the existing C#/.NET XTester Engine. The editor, workspace, Git and terminal will come from Code - OSS. Data handling, simulation, execution and statistics will be carried over from the current version of XTester. We are targeting October 1, 2026 for the first public milestone.
Backtesting theoryWalk-Forward and Out-of-Sample Testing: Where a Strategy Loses Stability
How to design sequential OOS tests, avoid future leakage and find the window where a strategy stops behaving consistently.
DevelopmentPorting Pine Script to XTester: How to Verify Behavior
Why compiling C# does not prove the same strategy behavior: timing, orders, sizing, HTF data, and trade-level checks after a TradingView port.
DevelopmentXTester 0.0.88: porting strategies from other platforms to XTester
XTester 0.0.88 can read an external strategy, create a separate C# project, and report what changed during the port.
DevelopmentXTester MCP: How an AI Agent Works with a Local Backtester
How MCP connects an AI agent to a local XTester environment for projects, compilation, historical data, backtests and inspectable results.