From a85602eb9c68f5bb36cbb2e2aae2c61ad2518bc1 Mon Sep 17 00:00:00 2001
From: Joe Schr <8218910+TheJoeSchr@users.noreply.github.com>
Date: Tue, 22 Nov 2022 11:41:28 +0100
Subject: [PATCH] add "how to run tests"

---
 docs/developer.md | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/docs/developer.md b/docs/developer.md
index b4961ac77..94923b035 100644
--- a/docs/developer.md
+++ b/docs/developer.md
@@ -49,6 +49,13 @@ For more information about the [Remote container extension](https://code.visuals
 New code should be covered by basic unittests. Depending on the complexity of the feature, Reviewers may request more in-depth unittests.
 If necessary, the Freqtrade team can assist and give guidance with writing good tests (however please don't expect anyone to write the tests for you).
 
+#### How to run tests
+
+Use `py.test` in root folder to run all available testcases and confirm your local environment is setup correctly
+
+!!! Note "develop branch"
+    This assumes that you have `stable` branch checked out. Other branches may be work in progress with tests not working yet.
+
 #### Checking log content in tests
 
 Freqtrade uses 2 main methods to check log content in tests, `log_has()` and `log_has_re()` (to check using regex, in case of dynamic log-messages).