pydocstyle linter typo and test doc addition

Author: sagarlf

docs/python/docstrings.md

@@ -157,7 +157,7 @@ to check that your docstrings render correctly
 
 ### Checking Docstring coverage
 
-- Use [pycodestyle](https://pycodestyle.pycqa.org/en/latest/) for linting your code against docstrings. When using `flake8`, [this](https://gitlab.com/pycqa/flake8-docstrings) plugin can be used.
+- Use [pydocstyle](https://pydocstyle.pycqa.org/en/latest/) for linting your code against docstrings. When using `flake8`, [this](https://gitlab.com/pycqa/flake8-docstrings) plugin can be used.
 - [interrogate](https://interrogate.readthedocs.io/en/latest/) (example below) is **recommended** to use for docstring coverage in the code.
 
 

docs/python/testing.md

@@ -4,7 +4,7 @@ title: Testing in python
 sidebar_label: Testing
 ---
 
-### Test is integral part of sofware quality and should not be missed.
+#### Test is integral part of sofware quality and should not be missed.
 
 
 
@@ -19,3 +19,7 @@ sidebar_label: Testing
 * `jsonschema` and `genson` like tool can be used for JSON validity.
 * Always confirm the `schema` when testing Web API response data.
 * Passing tests for `merge` should be priority for all projects.
+* Tests should always cover:
+    + **Unit**: for you code units. Please use `mock` for external dependency and side effects.
+    + **Functional**: You program functionality.
+    + **Integration**: Your whole program integration.