From 721d0fb2a8c4b5c3f582436c05cfa1ff1086475a Mon Sep 17 00:00:00 2001 From: Matthias Date: Wed, 23 Dec 2020 15:55:46 +0100 Subject: [PATCH] Improve wording of developer docs --- docs/developer.md | 3 ++- tests/exchange/test_ccxt_compat.py | 4 +++- 2 files changed, 5 insertions(+), 2 deletions(-) diff --git a/docs/developer.md b/docs/developer.md index 6440dba82..de489a348 100644 --- a/docs/developer.md +++ b/docs/developer.md @@ -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 diff --git a/tests/exchange/test_ccxt_compat.py b/tests/exchange/test_ccxt_compat.py index 6d495582b..8db56685a 100644 --- a/tests/exchange/test_ccxt_compat.py +++ b/tests/exchange/test_ccxt_compat.py @@ -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