Question

The caption may sound a little weird. Allow me to elaborate using an example.

The Object.Equals function usually requires that a.Equals(a) returns true. Unless you’re doing something twisted in your code, every class should adhere to this rule.

So we could write a generic unittest that checks all available classes to comply. (We might exclude classes explicitly marked by some attribute.)

And instead of just using Equals, we’re also checking for correct behavior of all implementations of, say, IComparer and whatever standard interface you can imagine.

Now, my question is: Does this exist already? If not, why would it be a bad idea?

Answer 1

I’m not aware of the existence of such a thing, but it sounds like a fine idea.

This is on the border of a convetion-based test and static code analysis – you could just as well imagine such a rule written as a custom Code Analysis rule, but it’s probably easier to write it as a unit test.

In our latest project, we have some convention-based tests that simply loop through all types in a given assembly and verifies that it conforms to some convention that we have. One could definitely imagine doing the same with e.g. the Equals method.