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
We should reduce usage of mock objects in test_clinic.py, such as FakeClinic, FakeConvertersDict, FakeConverterFactory and FakeConverter.
Pitch
There doesn't seem to be a strong reason to use mock objects like these in test_clinic.py, since the "real" objects in clinic.py are easy and cheap to construct. Removing the mock objects from test_clinic.py will reduce the maintenance burden, as it reduces the risk that the mock objects drift apart from the real implementation, and reduces the risk that the mock objects will have subtle behaviour differences to the real implementation.
Uh oh!
There was an error while loading. Please reload this page.
Feature or enhancement
We should reduce usage of mock objects in
test_clinic.py
, such asFakeClinic
,FakeConvertersDict
,FakeConverterFactory
andFakeConverter
.Pitch
There doesn't seem to be a strong reason to use mock objects like these in
test_clinic.py
, since the "real" objects inclinic.py
are easy and cheap to construct. Removing the mock objects fromtest_clinic.py
will reduce the maintenance burden, as it reduces the risk that the mock objects drift apart from the real implementation, and reduces the risk that the mock objects will have subtle behaviour differences to the real implementation.Linked PRs
test_clinic.py
#107714The text was updated successfully, but these errors were encountered: