There is an unsaved comment in progress. You will lose your changes if you continue. Are you sure you want to reopen the work item?
As per comment on roadmap page:
+1 for contract verifiers. I needed to test all implementers of IEquatable<T> the other day, and ended up getting partial coverage via LINQing over reflection to pull out the types implementing it, then writing tests to verify each in a loop. This was so that I could get coverage for the R#-generated equality-members implementations. I'm left feeling a little dirty, as I've written tests that will not necessarily fail if I subsequently add members to the types that should participate in the calculations without regenerating the equality members... So perhaps a better thing would be if xunit.assert could be persuaded to use a custom equality method when comparing instances of types that don't implement IEquatable<TItself> such that it uses the same implementation as ReSharper would generate but using reflection to pull out the public properties to participate....? Wild idea. TypeResolvers.codeplex.com may assist here...?