use global make_request() directly where we have a custom Resource
Where we want to render a request against a specific Resource, call the global make_request() function rather than the one in HomeserverTestCase, allowing us to pass in an appropriate `Site`.
Showing
- tests/app/test_frontend_proxy.py 7 additions, 6 deletionstests/app/test_frontend_proxy.py
- tests/app/test_openid_listener.py 9 additions, 8 deletionstests/app/test_openid_listener.py
- tests/http/test_additional_resource.py 7 additions, 6 deletionstests/http/test_additional_resource.py
- tests/replication/test_client_reader_shard.py 22 additions, 7 deletionstests/replication/test_client_reader_shard.py
- tests/replication/test_multi_media_repo.py 6 additions, 4 deletionstests/replication/test_multi_media_repo.py
- tests/replication/test_sharded_event_persister.py 32 additions, 10 deletionstests/replication/test_sharded_event_persister.py
- tests/rest/admin/test_admin.py 14 additions, 4 deletionstests/rest/admin/test_admin.py
- tests/rest/admin/test_media.py 10 additions, 3 deletionstests/rest/admin/test_media.py
- tests/rest/client/test_consent.py 21 additions, 7 deletionstests/rest/client/test_consent.py
- tests/rest/client/v2_alpha/test_account.py 12 additions, 2 deletionstests/rest/client/v2_alpha/test_account.py
- tests/rest/media/v1/test_media_storage.py 14 additions, 3 deletionstests/rest/media/v1/test_media_storage.py
Loading
Please register or sign in to comment