You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the python tests are trying to connect to the MongoDB backend. AFAIK the tests don't use the backend and they shouldn't.
For faster and easier running of the tests, the MongoDB backend needs to be completely mocked.
The text was updated successfully, but these errors were encountered:
Hi @TooAngel I'm kinda curious about this one. I'm trying to understand which tests should be mocked. I looked here but it looks like the tests are already covered by those patch decorators.
Please help me understand, which tests should be mocked/altered?
Cool. I didn't look too much into it yet. I usually have a MongoDB server running on my machine. Yesterday I stopped it for reasons and recognized that the tests got stuck on the tests/test_frontend.py test already.
I would guess the issue lies in the fact that the mongo connection is already initiated in src/server.py, maybe we can mock this before the server.py is loaded.
Easiest to test, checkout the repository, run the tests without a MongoDB server listening on localhost:27017 and you should see the issue.
Currently, the python tests are trying to connect to the MongoDB backend. AFAIK the tests don't use the backend and they shouldn't.
For faster and easier running of the tests, the MongoDB backend needs to be completely mocked.
The text was updated successfully, but these errors were encountered: