Skip to main content

Create a backtest config

backtest does not invent strategy parameters at runtime. It loads a config grid from Redis.

The key format is:

users:<user>:backtests:configs:<StrategyName:configName>

For example:

users:root:backtests:configs:MaStrategy:base
users:root:backtests:configs:TrendLine:base

The CLI reads the strategy name from the part before the first : in the config name. MaStrategy:base runs MaStrategy; TrendLine:base runs TrendLine.

Grid Shape​

A backtest config is a JSON object where every value is an array:

{
  "INTERVAL": ["15"],
  "MAX_LOSS_VALUE": [10],
  "MA_FAST": [21, 34],
  "MA_SLOW": [55, 89],
  "LONG": [
    {
      "enable": true,
      "direction": "LONG",
      "TP": 2,
      "SL": 1,
      "minRiskRatio": 1.2
    }
  ],
  "SHORT": [
    {
      "enable": true,
      "direction": "SHORT",
      "TP": 2,
      "SL": 1,
      "minRiskRatio": 1.2
    }
  ]
}

TradeJS expands the arrays into a test grid. If you only want one value, still wrap it in an array.

Seed With redis-cli​

After npx @tradejs/cli infra-up, Redis is normally available on 127.0.0.1:6379.

redis-cli -h 127.0.0.1 -p 6379 SET \
  'users:root:backtests:configs:MaStrategy:base' \
  '{"INTERVAL":["15"],"MAX_LOSS_VALUE":[10],"MA_FAST":[21],"MA_SLOW":[55],"LONG":[{"enable":true,"direction":"LONG","TP":2,"SL":1,"minRiskRatio":1.2}],"SHORT":[{"enable":true,"direction":"SHORT","TP":2,"SL":1,"minRiskRatio":1.2}]}'

Then run:

npx @tradejs/cli backtest --user root --config MaStrategy:base --tickers BTCUSDT --timeframe 15 --tests 1 --parallel 1

Seed With a Script​

Use a script when the config is longer or when your Redis requires auth.

import Redis from 'ioredis';

const redis = new Redis({
  host: process.env.REDIS_HOST || '127.0.0.1',
  port: Number(process.env.REDIS_PORT || 6379),
  password: process.env.REDIS_PASSWORD || undefined,
});

const key = 'users:root:backtests:configs:MaStrategy:base';
const grid = {
  INTERVAL: ['15'],
  MAX_LOSS_VALUE: [10],
  MA_FAST: [21],
  MA_SLOW: [55],
  LONG: [{ enable: true, direction: 'LONG', TP: 2, SL: 1, minRiskRatio: 1.2 }],
  SHORT: [{ enable: true, direction: 'SHORT', TP: 2, SL: 1, minRiskRatio: 1.2 }],
};

await redis.set(key, JSON.stringify(grid));
await redis.quit();

Keep a seed script like this in your own project when the config should be reproducible or reviewed in version control.

Runtime Config To Backtest Grid​

Runtime strategy configs are stored under:

users:<user>:strategies:<StrategyName>:config

The CLI has internal helpers that convert enabled runtime strategy configs into one-value backtest grids by removing runtime-only keys such as:

  • ENV
  • INTERVAL
  • MAKE_ORDERS
  • CLOSE_OPPOSITE_POSITIONS
  • BACKTEST_PRICE_MODE
  • BACKTEST_ENTRY_DELAY_BARS

For public docs, the practical path is still to seed the backtest grid directly unless you are working from an existing runtime strategy config in the app.

Common Errors​

Backtest config "<name>" not found​

The Redis key is missing for the selected user. Check both the user and config name:

redis-cli -h 127.0.0.1 -p 6379 GET 'users:root:backtests:configs:MaStrategy:base'

must include strategyName and strategyConfig grid​

The payload is not a grid object. Every top-level value must be an array.

Backtest runs a different strategy than expected​

The strategy name is parsed from the config name. Use StrategyName:label, for example TrendLine:base.

Next​