fix multibacktest example strategy import

[Geochelone666]

move the existing SmaCross strategy from the test suite to backtesting.test so the documented import works. keep its fast/slow parameters and reuse it in the tests.

replace the optimization placeholder with a small parameter grid and add a regression test that runs the complete example.

Closes #1415

checks: 82 tests passed with MPLBACKEND=Agg, including the offline example and lib/utils tests; flake8 passed. mypy reports the same two _plotting.py errors on unchanged master.

AI assistance: used Codex to prepare and test this change.

[arhancanli]

Same kind of problem a few lines down, in MultiBacktest.optimize's docstring: it imports from backtesting.plot import plot_heatmaps, but there's no backtesting.plot module (on 0.6.6 that line raises ModuleNotFoundError); plot_heatmaps lives in backtesting.lib. The example also assigns heamap and then uses heatmap. With both fixed it works as written: optimize returns one column per dataset indexed by the parameter combination, so plot_heatmaps(heatmap.mean(axis=1)) plots the cross-instrument average. Might be worth folding into this PR, with the same exec-the-docstring test.

[Geochelone666]

Good catch, thanks! Fixed both: - Changed `from backtesting.plot import plot_heatmaps` to `from backtesting.lib import plot_heatmaps` - Fixed the `heamap` -> `heatmap` typo Pushed to the PR branch.

…

On Mon, 05 Oct 2026 11:49:19 -0700, Arhan Canli ***@***.***> wrote: arhancanli left a comment (kernc/backtesting.py#1419) Same kind of problem a few lines down, in `MultiBacktest.optimize`'s docstring: it imports `from backtesting.plot import plot_heatmaps`, but there's no `backtesting.plot` module (on 0.6.6 that line raises `ModuleNotFoundError`); `plot_heatmaps` lives in `backtesting.lib`. The example also assigns `heamap` and then uses `heatmap`. With both fixed it works as written: `optimize` returns one column per dataset indexed by the parameter combination, so `plot_heatmaps(heatmap.mean(axis=1))` plots the cross-instrument average. Might be worth folding into this PR, with the same exec-the-docstring test. -- Reply to this email directly or view it on GitHub: #1419 (comment) You are receiving this because you authored the thread. Message ID: ***@***.***>