Choose a backtesting platform by evidence, not feature count

Start with the strategy runtime and market data

Confirm that the platform runs the required language or visual strategy format and supplies the necessary symbols, history, sessions, and bar or tick resolution. A backtesting website designed for single-chart strategies is not automatically a portfolio engine, options-chain simulator, or broker-specific EA tester.

Audit the execution and accounting model

Check order timing, intrabar assumptions, bid and ask handling, partial fills, commission, slippage, margin, currency conversion, corporate actions, futures rolls, and overlapping positions. Only the subset relevant to the strategy must be sophisticated, but every relevant assumption must be visible and reproducible.

• Match the engine to the asset and order types.
• Save all data, cost, sizing, and fill settings.
• Inspect individual trades and the equity path.

Decide whether you need optimization or deeper analysis

A core backtesting tool may run one strategy well but lack parameter automation or independent report analysis. Add those layers only after the baseline is correct. Optimization should expose all tested combinations, and analysis should preserve the source trade data and disclose what it cannot verify.