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
{{ message }}
This repository was archived by the owner on Jun 17, 2023. It is now read-only.
Should we aim to generate a TestCase class which has separate test methods for all those assertions?
An example of where this is used is twisted.names.test.test_dns.MessageComparisonTests (https://github.com/twisted/twisted/blob/trunk/twisted/names/test/test_dns.py#L870). But it's painful to have to write a separate test method for comparison of each attribute. So I guess we need to aim to generate test methods for every combination of attribute and equality assertion.
With all that in mind, has anyone got any hints on the best way to implement this?
One wants to unit test this sort of behavior but characteristic has enough information to automatically generate these tests in most cases.
Perhaps something like
MyClassEqualityTests = make_equality_tests(MyClass)
?The text was updated successfully, but these errors were encountered: