Integrating to the max...BizTalk Style

For testing BizTalk solutions the combination of BizUnit and the orchestration profiler are the way to go. Setting it up for a new project can be a hassle, although i appreciate it’s flexibility with the easy of adding custom BizUnit steps. I just came across a new framework that provides some usefull means of testing BizTalk artefacts, namely maps. As you might have noticed the support for testing in BizTalk 2009 / BizTalk 2010 is somewhat limited and it forces you to build your artefacts with additional code for mere testing only (the check ‘Enable Unit Test’ will generate a wrapper around the components such as the TestableMapBase in the example below)….the most you will get out of the standard map testing is a validate instance of your message: Microsoft.BizTalk.TestTools.Mapper.TestableMapBase mapTest = new MapTest.Input2Output(); mapTest.TestMap(     @"Input.xml",   Microsoft.BizTalk.TestTools.Schema.InputInstance...

BizTalk Unit testing was before the release of BizTalk 2009 not an integral part of the product. The community anticipated with awesome frameworks and tools: BizUnit Very stable framework that is a wrapper around NUnit that allows testing using BizUnit steps, complemented with additional steps ( BizUnitExtensions ) and incorperated in the ( BizTalk Software Factory ). This is the framework that suits all your needs by allowing custom BizUnit step development in .Net and uses an Xml based approach. Pipelinetesting framework Very stable framework developed by Tomas Restrepo, very nice and easy to understand. Orchestration profiler Profiler that allows for code coverage by querying the BizTalk database and generating reports on the orchestration shape coverage, allowing insight in the completeness of the test. Present day A new framework has been introduced, that is fitted for one purpose, testing maps using an approach of dynamically reading/manipulating Xml fields by XPath expressions t...