Updated Development (markdown)

Development.md

@@ -27,7 +27,7 @@ Same goes for zfs-autoverify:
 ZfsAutoverify.py v3.2-alpha1 - (c)2021 E.H.Eefting (edwin@datux.nl)
 ```
 
-## Running automated test suites
+## Automated test suites
 
 zfs-autobackup is a test driven design process, usually i start with creating the test and then writing the code.
 
@@ -35,7 +35,9 @@ The tests run against actual zfs commands and create a lot of temporary pools vi
 
 The tests also need ssh support via root@localhost, so it will create and install a sshkey if needed.
 
+Look at https://github.com/psy0rz/zfs_autobackup/actions to see the results of the actual tests that are run automaticly on each commit on github.
 
+## Running the whole suite
 
 ```console
 (backupdev) root@ws1:/home/psy/zfs_autobackup# ./tests/run_tests 
@@ -51,5 +53,18 @@ test piped exitcodes ... ok
 ...
 ```
 
+## Running one test
 
+Since running the whole suite takes long, you can run one test like this:
+
+```console
+(backupdev) root@ws1:/home/psy/zfs_autobackup# ./tests/run_test test_verify.py
+###########################################
+#### Unit testing against:
+#### Python                :3.8.10 (default, Nov 26 2021, 20:14:08)  [GCC 9.3.0]
+#### ZFS userspace         :2.1.1-0york0~20.04
+#### ZFS kernel            :2.1.1-0york0~20.04
+#############################################
+test_verify (test_verify.TestZfsEncryption) ... Preparing zfs filesystems...
+```