BizTalk Map test framework

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.InputInstanceType.Xml,
     "Output.xml",  Microsoft.BizTalk.TestTools.Schema.OutputInstanceType.XML);

This can be overcome by using a mapping helper component (e.g .from Michael Stephenson) that does a Binary or Xml validation of the result, nevertheless you don’t want to write this on your own.

MapTestingHelper.ValidateMapOutput("Output.xml", “Output.xml");

I’ve tried out the BizTalk map test framework and it allows you to write your testcases using Xpath on fields that you dynamically want to fill with dummy values and predicted outcomes.

Let’s say you want to test a value mapping that returns different results based on the input you can simply write a method that does this validation in just a few lines:

MapTestCases collection = new MapTestCases(
"/*[local-name()='Input']/*[local-name()='InputValue']",
"/*[local-name()='Output']/*[local-name()='ValueOut']"               );

            collection.AddTestCase(
                new string[] { "TEST" }, new string[] { "TRUE" }
                );

            collection.AddTestCase(
                new string[] { "AAH" }, new string[] { "FAL3SE" }
                );
            base.ExecuteMapTest(collection);
            return;

 

I think i like it….check it out here: BizTalk map test framework

Comments

Post a Comment

Popular posts from this blog

Azure implementation guidelines

In My post ‘ Service Bus Management ’ I pointed out a way of implementing a DTAP strategy for managing the Service Bus environment. There’s now a great post available from Microsoft which goes into more detail about other aspects of managing the Azure subscriptions and other artefacts which is quite useful when setting up your Azure environments. Follow this link to the ‘Azure Implementation Guidelines’ HTH, Sander
Read more

UK Connected Systems User Group – BizTalk Services questions

This Wednesday I’m attending the CSUG – The Hybrid Organisation (sold out!). During my evaluation of several Integration products (BizTalk / BizTalk Services / Neuron ESB / MuleESB) I had some concerns/questions on BizTalk Services. My goal is to get answers on the following scenario a) I receive a HTTP Post with an Xml Body payload b) This contains a signature which i need to validate c) Transform the Xml body payload to another Xml message d) Perform a HTTP Post with the new Xml message to an external HTTP url and sign the message e) Route the response back, similar to the aforementioned steps, where an error needs to be mapped to a dedicated error response Challenges I'm wondering how to cope with some of the following challenges in this scenario, and would like to know resource information available which addresses some of these challenges; Validating / Signing of messages A requirement is to validate the incoming message by inspecting an signature in the message
Read more

Setting up a build server with the BizTalk Deployment Framework

Image
This chapter describes the steps to a TFS Build Server to set up BizTalk deployment with the following functionality: • Build solution • Perform unit testing Using BizUnit • Create Deployment Packages Using BDTF • Deploy to Server Using R packages created in previous step • Create documentation BizTalkDocumenter For this the following steps are required: • Installation Components (30 min) • Configuring a build account (30 min) • Setting up the build service (30 min) • Scrum template installation (30 min) • Share for the build output directory (10 min) • Adjustments Build Template for use BTDF (30 min) • Design of build definitions (60 min) • Setting BTDF (60 min) • Use BTDF • Build execution / scheduling UPDATE (21-06-2013) - When using sharedassemblies, the following URL is a big help http://mohamedradwan.wordpress.com/2013/01/31/set-custom-assemblies-path-for-host-build-service-on-the-cloud/ - For viewing the basic instructions a video is available on the following blog http:
Read more