Wrapped up the development for this interface today, it is nothing challenging, which brings me enough time for the testing piece.

So this is actually the first time that I did unit testing, well, I did read a lot, but yes, this is the first time I did it.

I have to say NUnit is a good tool and the MSTest is completely a garbage since it is comparatively much slower.

BizUnit is a pain initially, the earning curve is not that great deal, but to settup the test cases. I turned out to write a separate orchestration for testing purpose only. Another thing about BizUnit is, not all test steps satisfy your needs. For example I am completely a regex know nothing guy, so I have to tweak the event log checking step a bit to get it working for me. Lesson learned, if you not happy with testing steps, just change it, you can even attach to NUnit and debug the library and go from there.

I now truly understand the TDD argument, it may take time to write tests, but once you get them working for you, it is way easier, helpful and error-prone than the manual eye-ball approach.

My only wish is MS make this tool official and integrate with BizTalk natively somehow. Anyway … happy testing