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
SimonBohnenQC: We're currently not testing against live quetz, right? This would probably be something nice to have.
SimonBohnenQC: It looks to me like the mocked tests are also not reflecting the actual responses given by quetz. Consider the /api/channels/{channel_name}/members route. The mocked tests use the following json scheme:
(You can find it in the Swagger docs when launching quetz)
JanJaguschQC: I had the same thought today when reviewing your PR. I like the idea. Testing against an actual Quetz instance shouldn't be too complicated, either.
The text was updated successfully, but these errors were encountered:
By SimonBohnenQC, copied from other repo.
SimonBohnenQC: We're currently not testing against live quetz, right? This would probably be something nice to have.
SimonBohnenQC: It looks to me like the mocked tests are also not reflecting the actual responses given by
quetz
. Consider the/api/channels/{channel_name}/members
route. The mocked tests use the following json scheme:quetz-client/tests/conftest.py
Lines 113 to 115 in 2765d57
Whereas actual
quetz
specifies the following scheme:(You can find it in the Swagger docs when launching quetz)
JanJaguschQC: I had the same thought today when reviewing your PR. I like the idea. Testing against an actual Quetz instance shouldn't be too complicated, either.
The text was updated successfully, but these errors were encountered: