adelorenzo
/
stable
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Improve wording of developer docs

This commit is contained in:
Matthias 2020-12-23 15:55:46 +01:00
parent 65d91b7cbb
commit 721d0fb2a8
2 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
docs/developer.md
View File

@ -242,7 +242,8 @@ The `IProtection` parent class provides a helper method for this in `calculate_l
Most exchanges supported by CCXT should work out of the box.
To quickly test the public endpoints of an exchange, add a configuration for your exchange to `test_ccxt_compat.py` and run these tests with `pytest --longrun`.
To quickly test the public endpoints of an exchange, add a configuration for your exchange to `test_ccxt_compat.py` and run these tests with `pytest --longrun tests/exchange/test_ccxt_compat.py`.
Completing these tests successfully a good basis point (it's a requirement, actually), however these won't guarantee correct exchange functioning, as this only tests public endpoints, but no private endpoint (like generate order or similar).
### Stoploss On Exchange

4
tests/exchange/test_ccxt_compat.py
View File

@ -5,8 +5,10 @@ However, these tests should give a good idea to determine if a new exchange is
suitable to run with freqtrade.
"""
import pytest
from pathlib import Path
import pytest
from freqtrade.resolvers.exchange_resolver import ExchangeResolver
from tests.conftest import get_default_conf