This describes how much of the codebase is covered by the tests. Missing lines means that the tests dont ever touch those points in the code which means that any refactoring to missing lines that break the project might not be caught in testing.
2) docker compose now spins up a local mongoDB instance instead of using a real one when developing.
feel free to change the environment variables in the docker compose file to a real database if you want to test using that
included a dump of the old mongo testing database I was using yesterday for reference
1) I added testing using pytest start by running
then in a seperate terminal:
which will run the tests, and then display coverage like:
This describes how much of the codebase is covered by the tests. Missing lines means that the tests dont ever touch those points in the code which means that any refactoring to missing lines that break the project might not be caught in testing.
2) docker compose now spins up a local mongoDB instance instead of using a real one when developing.
feel free to change the
environment variablesin the docker compose file to a real database if you want to test using thatincluded a dump of the old mongo testing database I was using yesterday for reference