Include the strategy.py and config.json used for each backtesting result.

[Guscccc]

Describe the enhancement

I think it would be nice to include the strategy and config that's used for each backtest in the backtesting archive file for reproducibility. or to offer a command line option that does it when using freqtrade backtesting.

[xmatthias]

Please get used to filling out the issue template (also if you THINK it's not relevant for your case). Those who frequently omit the template may have their issues closed without comment.
We're asking some very basic questions - by deleting the issue template, you're explicitly choosing not to answer our questions.

Filling out the template helps reduce our workload, and we greatly appreciate that.

---

i'm not entirely sure i see the point of this if i'm honest.

It'll bloat backtest results for sure - but what for exactly?
it's quite common to run 100ds of backtests with small, iterative changes
so we'd do a copy of the strategy, strategy parameters, config - and maybe the whole strategy directory (who knows what was imported from "next door") - but with what end-goal exactly (what are we trying to accomplish by bloating results)?

to have FULL reproducibility, we'd need to save the data directory as well (i could be missing some data at the end on one pair (for whatever reason) - and then download the missing parts - which would change results, too) - but then it really becomes ridiculous, really

[mexxBf]

I believe implementing this approach would be highly beneficial. Otherwise, reproducing previous outcomes becomes a challenging task. In instances where I modify my strategies and later struggle to recall the specific changes, it hinders my ability to replicate past results. This is particularly true in scenarios involving hundreds of alterations. An even more effective solution would be to create a comprehensive overview, presenting the results in a list. A good place would be the list of the past backtests.

[stash86]

Or you can just practice a good way of archiving files. Keep copies of old versions after several updates. Or use different class names after several updates. There are plenty of ways to do that.

As noted above, saving files used in backtest gonna eats your hard disk space faster than you can imagine.