Comments on: Introducing the Expected Objects Library

By: Anonymous

Anonymous — Sun, 07 Aug 2011 22:49:00 +0000

Derek, Thanks SO MUCH for creating this tool. I and my entire development team uses Expected Objects every day in creating a new virtual terminal and payment processing solution (fairly large project). It has been ideal in so many ways. We have found that our test count has decreased drastically thereby making our test suite drastically more maintainable. ExpectedObjects RULE!

By: Anonymous

Anonymous — Tue, 12 Jul 2011 23:52:00 +0000

Yes, that’s what the “Comparing Partial Objects” example demonstrates. Writing assertions for each field is fine if the domain your validating is an API (e.g. “The service response should have these fields”), but they tend to lead to obscure tests when modeling business concerns (e.g. “When the customer does X, the system should do Y”).

By: fschwiet

fschwiet — Thu, 07 Jul 2011 00:01:00 +0000

Interesting… I wonder if you’ve used this in such a way that the test only needs to define the fields on the object that the test cares about? In this case I would probably just use per-field assertions, but curious.

By: Derek Greer

Derek Greer — Wed, 29 Jun 2011 15:08:00 +0000

Expected Objects does a recursive comparison, so while these strategies might not make sense for the top level object, they are necessary for comparing composed types.

By: Robert Simmons

Robert Simmons — Wed, 29 Jun 2011 14:58:00 +0000

Hehe, I wrote something similar (although not as in-depth as what you’ve done, since we didn’t need it) for our in-house testing about a year ago. I wasn’t a fan of overriding Equals everywhere either.

By: Kevin Gurton

Kevin Gurton — Wed, 29 Jun 2011 10:54:00 +0000

I’m not sure that the EqualsOverrideComparisonStrategy should be used by default. If you’re overriding Equals, and want to use that for your test, why not just use Assert.AreEqual(expected, actual)?

By: The Morning Brew - Chris Alcock » The Morning Brew #883

The Morning Brew - Chris Alcock » The Morning Brew #883 — Wed, 29 Jun 2011 07:45:04 +0000

[...] Introducing the Expected Objects Library – Derek Greer follows on from his recent post on the Expected Objects pattern with the sharing of a library of code, the Expected Objects Library, which makes the implementation of the expected objects easy. Derek outlines the use of the library in this post, and highlights how it can be obtained via NuGet for Binary or GitHub for source. [...]