Added tests section in pyintelowl

Signed-off-by: aryan <[email protected]>

docs/GreedyBear/Introduction.md

@@ -10,7 +10,7 @@ The project goal is to extract data of the attacks detected by a [TPOT](https://
 
 There are public feeds provided by The Honeynet Project in this site: greedybear.honeynet.org. [Example](https://greedybear.honeynet.org/api/feeds/log4j/all/recent.txt)
 
-To check all the available feeds, Please refer to our [usage guide](https://greedybear.readthedocs.io/en/latest/Usage.html)
+To check all the available feeds, Please refer to our [usage guide](https://intelowlproject.github.io/docs/GreedyBear/Usage/)
 
 Please do not perform too many requests to extract feeds or you will be banned.
 

docs/IntelOwl/installation.md

@@ -212,7 +212,7 @@ There are 3 options to execute the web server:
 
   Then you should call the `./start` script with the parameter `--https` to leverage the right Docker Compose file for HTTPS.
 
-  Plus, if you use [Flower](https://intelowlproject.github.io/docs/IntelOwl//advanced_configuration/#queue-customization), you should change in the `docker/flower.override.yml` the `flower_http.conf` with `flower_https.conf`.
+  Plus, if you use [Flower](https://intelowlproject.github.io/docs/IntelOwl/advanced_configuration/#queue-customization), you should change in the `docker/flower.override.yml` the `flower_http.conf` with `flower_https.conf`.
 
 - **HTTPS with Let's Encrypt**
 

docs/pyintelowl/Tests.md

@@ -0,0 +1,42 @@
+Tests
+======================================
+
+Configuration
+--------------------------------------
+
+Some tests require file samples, which can be found in the encrypted folder ``tests/test_files.zip`` (password: "infected").
+Unzip the archive in ``tests/test_files`` folder before running the tests.
+
+**Please remember that these are dangerous malware! They come encrypted and locked for a reason!
+Do NOT run them unless you are absolutely sure of what you are doing!
+They are to be used only for launching specific tests that require them** (``__send_analysis_request``)
+
+* With the following constants in ``__init__.py``, you can customize your tests:
+
+  * **MOCKING_CONNECTIONS:** Mock connections to external API to test functions without a real connection or a valid API Key.
+
+* If you prefer to use custom inputs for tests, you can change the following constants:
+
+  * **TEST_JOB_ID**
+  * **TEST_HASH**
+  * **TEST_URL**
+  * **TEST_IP**
+  * **TEST_DOMAIN**
+  * **TEST_GENERIC**
+  * **TEST_FILE**
+  * **TEST_FILE_HASH**
+
+Launch Tests
+-------------------------------------
+
+* The test requirements are specified in the ``test-requirements.txt`` file. Install them using,
+
+.. code-block:: bash
+
+    $ pip3 install -r test-requirements.txt
+
+* Launch the tests using ``tox``:
+
+.. code-block:: bash
+
+    $ tox

mkdocs.yml

@@ -26,9 +26,12 @@ nav:
       - API docs: "GreedyBear/Api-docs.md"
   - PyIntelOwl:
       - Quickstart: "pyintelowl/index.md"
-      - Modules:
-        - IntelOwlClass: "pyintelowl/IntelOwlClass.md"
-        - IntelOwlClientException: "pyintelowl/IntelOwlClientException.md"
+      - Usage:
+          - Modules:
+            - IntelOwlClass: "pyintelowl/IntelOwlClass.md"
+            - IntelOwlClientException: "pyintelowl/IntelOwlClientException.md"
+      - Development:
+          - Tests: "pyintelowl/Tests.md"
   - GoIntelOwl:
       - index: "GoIntelOwl/index.md"
   - Guides: