Archive | Testing RSS for this section

Twin Cities Connected Systems User Group Meeting on Sep 15

It was a small, but active meeting as I gave a BizMock presentation to the Twin Cities Connected Systems User Group  on the 15th.  Thanks to all who attended and contributed with your questions and comments.  Slides from the presentation are available here.

Introduction to BizMock

A few weeks back, I mentioned that I had done some looking into BizMock as a framework for Unit Testing in BTS.  Recently, I did a basic intro to BizMock for one of my clients.  Here is the (scrubbed and updated) powerpoint presentation.  The content is based largely on what is included with BizMock documentation (sparse as it is) and sample application.  The powerpoint also misses some of the context that would normally be given during a presentation, so please feel free to comment or ask questions and I’ll do my best to answer.

Unit Testing BizTalk Solutions – BizMock

Test-Driven Development (TDD) has a strong track record in the industry and has proven to be great at allowing developers to build higher quality code  more quickly.   For us BizTalk guys, though,  TDD is often difficult because writing a test often involves deploying a full BizTalk solution.  In addition to the typical troubles in deployments, getting “real world” scenarios or effective mock-ups can be problematic as well.

I’ve spent some time researching testing solutions for BizTalk recently and discovered a neat little tool called BizMock.  BizMock ties in with Visual Studio test and gives you the ability to emulate Ports  and other BizTalk artifacts without actually deploying them.  It also allows you to mock up Messages and send them into BizTalk.  I’ve just begun to dig into BizMock, so I’ll not offer up a final opinion yet, but early on it looks promising.  The download comes with some sample code to help you get started, but other than that, it’s not very well documented.  Documentation of the artifacts schema in particular, would be most helpful, but is missing.  If you use this, prepare to get deep into code in order to figure things out.

%d bloggers like this: