Testing in the Backtester

A build saved in the Lab is ready to test in the Backtester, The Proving Ground. There's no export step: the Backtester reads your Lab library directly.

From the Lab

• On Your indicators, the flask button on a row (Test in The Proving Ground).
• Backtest on an indicator in the Saved panel.
• Backtest in the workspace, once the indicator is saved.

Each opens the Backtester in a new tab, signed in as you. A Backtest this indicator box asks where to Start the replay at, set to about a month back to start with. It “Runs live on NQ with a $100,000 practice account.” Press Start backtest and the session opens with your indicator on the chart. You can change the rest later from the session menu.

From the Backtester

In the Backtester's indicator picker, My builds lists the indicators in your Lab library. Press Add. Protected builds run privately, so their code never reaches your browser. If the tab is empty, it says “Your Lab library is empty — build one in the Indicator Lab, save it, then add it here.” Build in the picker opens the Lab in a new tab.

The picker's Community tab has members' published indicators. Adding someone else's uses the same daily allowance as forking in the Lab; see Community and publishing.

Keeping it current

The Backtester keeps the version you added. If you revise an Own code build in the Lab afterwards, the indicator gets an update ↑ chip (“A newer version exists in the Lab — click to update”). Click it to switch. It never updates by itself.

For everything else about indicators in the Backtester, see Indicators in the Backtester.