Feature Request

Dolibarr has a lot of bugs IMO that could be easily discovered before releases if we had some kind of testing suite.
I suggest we make one. I can contribute tests, but I have never written tests in PHP before. I could write some in Python to test the API.

Suggested implementation

no idea, never done this before
see https://www.tutorialspoint.com/software_testing_diction

After the backtest run, we see the statistics. It is very good! Is there any simple way to see that statistics separately for long ans short trades?

This is the onboarding issue for new contributors to fastquant 😄

Please read through the references below and feel free to ask for help in the issues or slack channel!

Tutorials on the fastquant website:

https://enzoampil.github.io/fastquant-blog/

fastquant example notebooks:

https://nbviewer.jupyter.org/github/enzoampil/fastquant/tree/master/examples/

**Intro t

For intraday prices, Tiingo can provide the IEX volume if explicitly requested as
"?columns=open,high,low,close,volume" per their docs.

Unfortunately the get_dataframe doesn't expose this, when no metric_name is provided, it passes no value for the column parameter to Tiingo's APIs

                url = self._get_url(stock, frequency)
                response = self._request('GET', ur

What's your feature?
it's hard to know what the data mean

Why are you interested in it being added?

>>> print(spy.keys())
dict_keys(['margin_initial_ratio', 'rhs_tradability', 'id', 'market', 'simple_name', 'min_tick_size', 'maintenance_ratio', 'tradability', 'state', 'type', 'tradeable', 'fundamentals', 'quote', 'symbol', 'day_trade_ratio', 'name', 'tradable_chain_id', 'splits'