Make backtest more visible and user friendly from the UI about frequi HOT 2 CLOSED

Backtesting will be available when freqtrade is started in webserver mode - as the documentation also describes.

It's pointless (and confusing) to show it in any other mode - as it would suggest functionality that simply is not working 90% of the time (assuming you'll be looking at a live bot most of the time) - so you have a button you see all the time - but cannot click - for no good reason other than "i'm too lazy to read the docs".

backtesting will show the errors that appear in the UI via popup - in the case of no data:

It's clearly saying "there's no data".
Where it's looking for the data is not necessarily user_data/data/<exchange> (the default, but not guaranteed to be there) - but could also be a different location depending on config / cli arguments - so the message says what it should - while not providing missleading / potentially wrong information.

As you're correctly pointing out - reading the documentation does help - so that's what i'll recommend you to do.
Please read the documentation - we recommend to at least fly over the docs from top to bottom at least once - to get to know what functionality freqtrade offers and what the limitations are.

regarding data download mode:
That's something that's not implemented in a few minutes minutes - and the benefit of it is pretty small (you need a cli anyway - why provide it via UI?).

While it's something i'd like to have at some point - it's clearly not something i think has any priority - as it actually provides no benefit to the user (you'll make 0$ more - which is how i aim to judge which features should get priority most of the time).

from frequi.

@xmatthias Thanks for taking the time to write such a detailed reply, describing your thinking. I appreciate it, and I understand where you are coming from. 🙏

from frequi.