documenting the janky tests logs situation

This commit is contained in:
forest 2021-07-27 14:49:10 -05:00 committed by 3wc
parent 8c10f71f58
commit 16ff1b5b26

View File

@ -6,7 +6,9 @@ To run tests:
1. create a Postgres database called `capsulflask_test` 1. create a Postgres database called `capsulflask_test`
- e.g.: `docker exec -it 98e1ddfbbffb createdb -U postgres -O postgres capsulflask_test` - e.g.: `docker exec -it 98e1ddfbbffb createdb -U postgres -O postgres capsulflask_test`
- (`98e1ddfbbffb` is the docker container ID of the postgres container) - (`98e1ddfbbffb` is the docker container ID of the postgres container)
2. run `python3 -m unittest` 2. run `python3 -m unittest && cat unittest-log-output.log && rm unittest-log-output.log`
**NOTE** that right now we can't figure out how to get the tests to properly output the log messages that happened when they failed, (or passed), so for now we have hacked it to write to a file.
### Architecture ### Architecture