MatrixSynapse/tests/storage
Richard van der Hoff 33ebee47e4
Remove redundant `get_success` calls in test code (#12346)
There are a bunch of places we call get_success on an immediate value, which is unnecessary. Let's rip them out, and remove the redundant functionality in get_success and friends.
2022-04-01 16:10:31 +01:00
..
databases
__init__.py
test__base.py
test_account_data.py
test_appservice.py
test_background_update.py
test_base.py
test_cleanup_extrems.py
test_client_ips.py
test_database.py
test_devices.py
test_directory.py
test_e2e_room_keys.py
test_end_to_end_keys.py
test_event_chain.py
test_event_federation.py
test_event_metrics.py
test_event_push_actions.py
test_events.py
test_id_generators.py Remove redundant `get_success` calls in test code (#12346) 2022-04-01 16:10:31 +01:00
test_keys.py
test_main.py
test_monthly_active_users.py
test_profile.py
test_purge.py
test_redaction.py Remove redundant `get_success` calls in test code (#12346) 2022-04-01 16:10:31 +01:00
test_registration.py
test_rollback_worker.py
test_room.py
test_room_search.py
test_roommember.py
test_state.py
test_stream.py Remove redundant `get_success` calls in test code (#12346) 2022-04-01 16:10:31 +01:00
test_transactions.py
test_txn_limit.py
test_unsafe_locale.py
test_user_directory.py