Why using TransMock?

You might already be wondering why should one use TransMock? It is obvious that it cannot be used alone to perform the testing, but instead it should be used in conjunction with BizUnit.
In order to answer that question I would like first to draw the limitations of other BizTalk testing frameworks, which have greatly inspired the development of TransMock. The frameworks I have particularly in mind are BizMock and BizUnit.

One of the biggest limitations of BizMock has been the need for a separate configuration file that describes the relations between the receive locations and ports, orchestrations and send ports. This has proven to be very unnecessary information excess, since this very information is actually contained in the bindings file. In addition the poor documentation of how to create this file has not helped much in further popularizing this framework. It seems that its main focus has been to make a better and easier programming model for authoring automated integration tests for BizTalk. Which in itself is not bad at all, considering how fast BizTalk developers are used to drop this very important piece of the delivery process, which usually haunts them way after an integration project has been delivered.

Another limitation that is very familiar to the BizTalk developer community is related to BizUnit - while it is broadly used for testing BizTalk integrations (in fact it can be considered as the de facto standard in this niche), it lacks the ability to easily allow for defining web service mocks on the fly for web services that are consumed by BizTalk server. One has to implement such mocks with code and implement additional BizUnit test steps that would be responsible for spinning those mock instances.

TransMock targets all these challenges and limitations and goes even further - it aims to integrate nicely with existing and well adopted frameworks like BizUnit and BTDF. This way it will be much easier for the developers who have grasped this neat framework to also start using it effectively from day 1.

Another very important reason for adopting TransMock for supporting your test cycle is that mimicking any behavior or logic of an actual system would boil down to simply authoring files with different content for reflecting the various specific behaviors. This is much less time consuming and demanding effort compared to writing complex stubs for implementing such behaviors.

Last edited Oct 21, 2014 at 4:54 PM by cyberbyber, version 2