Matching Standard


Behind this, somewhat, catchy title lies a new version (4.1) of Testing.Commons.NUnit and no golden rule about how to discard potential dates in the digital era (would be rubbish advice anyway).

It is not a major version, but I believe it is an important one since there is a little history behind it.

On the shoulders of middle-sized giants

Quite a few years ago, I wrote about how ExpectedObjecs can be used to aid writing assertions that check just the important part of a complex object or hierarchy.
Not so long ago, I also wrote about the migration of some of my OSS projects to support .NET Standard.

I briefly mentioned about the sacrifices (not many, fortunately enough) needed to get a standard version out of the door.
In this particular case, the sacrifice for users not targeting the full .NET framework, was not being able to use MatchingConstraint because this piece of functionality relies on the aforementioned ExpectedObjects library and that library was not targeting others than the full .NET framework and, therefore, I could not depend on it for the netstandard version of my library.

Missing no more

But, since Derek worked the issue I got the needed green light to re-include such feature and painlessly release another version of the Testing.Commons.NUnit so that everyone can match objects at their fully earned will, regardless of the platform they are running into.

Match with care, folks.