cfa3b6dcd4
* making multprocessing usage explicit and easily identifiable * fixed error messaging and made API not found reports debug information * removed acceptance tests * removed obsolete gh workflow file * fixed testcaes issue with patching * changed testcases to not check for error logs as we moved this to debug logs checks/asserts can be re-integrated asap we are able to set the debuglevel in for the single use cases Signed-off-by: Jürgen Eckel <juergen@riddleandcode.com>
Planetmint Server Unit Tests
Most of the tests in the tests/ folder are unit tests. For info about how to write and run tests, see the docs about contributing to Planetmint, especially:
- Write Code - Remember to Write Tests
- [Notes on Running a Local Dev Node with Docker Compose](https://docs.planetmint.io/en/latest/contributing/dev-setup-coding-and-contribution-process/run-node-with-docker compose.html), especially
make test - Notes on Running a Local Dev Node as Processes (and Running All Tests)
Note: There are acceptance tests in the acceptance/ folder (at the same level in the hierarchy as the tests/ folder).
Debugging test cases with VS Code
In order to debug unit tests create a virtual environment and install all necessary dependencies. VS Code should notify you that a new virtual environment is detected and ask if you want to use it as environment (more info: Getting started with Python in VS Code).
Configure the tests in VS Code by going to the Testing tab and click Confiugre Python Tests and select pytest. VS Code should now detect all test cases inside of tests. Click Debug Tests to run the tests with the debugger attached. (more info: Python testing in VS Code)
Note: pip install . will not automatically install the test dependencies. If missing install them manually.