--- title: "Unit Testing Biztalk : Two possible frameworks" url: "https://osherove.com/blog/2010/1/12/unit-testing-biztalk-two-possible-frameworks.md" canonical: "https://osherove.com/blog/2010/1/12/unit-testing-biztalk-two-possible-frameworks.html" published: "2010-01-12T14:51:55" updated: "2010-01-12T14:51:55" tags: [".NET", "Agile", "Unit Testing"] author: "Roy Osherove" description: "BizTalk is notoriously hard to test. But I just came a cross a couple of interesting solutions to do unit testing for biztalk related logic and orchestration. BizMock : “BizMock is a framework for testing BizTalk…" usage: "Licensed under CC BY 4.0 — reuse, quote and adapt with attribution (Roy Osherove, link to the original page)." license: "https://creativecommons.org/licenses/by/4.0/" --- # Unit Testing Biztalk : Two possible frameworks By Roy Osherove January 12, 2010 In [.NET](https://osherove.com/blog/category/net), [Agile](https://osherove.com/blog/category/agile), [Unit Testing](https://osherove.com/blog/category/unit-testing) **Historical article** · Originally published January 12, 2010; technical details may be outdated. BizTalk is notoriously hard to test. But I just came a cross a couple of interesting solutions to do unit testing for biztalk related logic and orchestration. 1. [BizMock](http://biztodd.blogspot.com/2009/12/what-is-bizmock.html) : > “BizMock is a framework for testing BizTalk solutions, using a Domain Driven Design (DDD) approach and fluent interface API. It has mocking capabilities, so no need to rely on dependent infraestructure like web services or DBs. The tests are writen and executed from within VS using regular Visual Studio Tests and C# code, allowing a TDD and agile development style of BizTalk solutions.” 2. [Bizmonade](http://bizmonade.matricis.com/): (I really don’t like the name) > “Bizmonade is a new project being developed to enable unit testing of BizTalk orchestrations, in isolation of other components, **without deploying the orchestrations to BizTalk** and without doing any configuration (bindings). > It allows running orchestrations directly from unit tests written in C#, using NUnit, MSTest or any another .Net testing tool. The orchestrations therefore run in complete isolation from the whole BizTalk environment, reducing the time needed to do quick tests of new orchestrations or of modifications to existing ones.” the API for BizMonade looks really interesting, but since I’m no Biztalk Guru, I don’t know if it satisfies what you’d want to test in a biztalk solution. With BizMock, the fact that one would need a “DeploymentItem” on the tests might mean that it’s an integration style test framework that’s just easier to get up and running, but not a “pure” unit testing solution. However, I’m not sure since I have not used it. Do you use these? or other solutions? Update: there’s [also BizUnit](http://www.codeplex.com/bizunit) , but god help me if I ever recommend people to use XML for making tests. [DON’T USE XML.](http://5whys.com/blog/be-productive-and-stop-using-xml.html) Please. ## More in .NET [All posts in .NET](https://osherove.com/blog/category/net) - Jan 14, 2010 ### [January at Israel .net user group: Unit Testing!](https://osherove.com/blog/2010/1/14/january-at-israel-net-user-group-unit-testing.html) - Jan 14, 2010 ### [The difference between continuous Integration tools and automated build tools](https://osherove.com/blog/2010/1/14/the-difference-between-continuous-integration-tools-and-auto.html) - Jan 11, 2010 ### [Poll: Do you use NUnit’s fluent API?](https://osherove.com/blog/2010/1/11/poll-do-you-use-nunits-fluent-api.html) - Jan 6, 2010 ### [TDD: 4 questions that will help you create the simplest thing that could possibly work](https://osherove.com/blog/2010/1/6/tdd-4-questions-that-will-help-you-create-the-simplest-thing.html) --- ## About the author **Roy Osherove**: Senior Solutions Architect at AWS working on AI for production and AI-driven development; author of The Art of Unit Testing and Elastic Leadership, with about 20 years of consulting and training on unit testing, TDD, team leadership and continuous delivery. ### Sites - [RobotPaper](https://robotpaper.ai/): This blog: AI patterns and anti-patterns, AI and coding agents, and engineering leadership. - [osherove.com](https://osherove.com): Roy's personal site. Author of The Art of Unit Testing and Elastic Leadership; consulting and training on unit testing, TDD, team leadership and continuous delivery, plus about 20 years of blog posts. - [The Art of Unit Testing](https://www.artofunittesting.com): The Art of Unit Testing, 3rd Edition (Manning): readable, maintainable, trustworthy unit tests, plus TDD workshops in C#, JavaScript, Java and Kotlin. - [5whys.com](https://www.5whys.com): Roy's writing on software team leadership: self-organizing teams, surviving chaos, learning mode and the Elastic Leadership model. - [Pipeline Driven](https://pipelinedriven.org): Continuous delivery and DevOps practices: build patterns, pipeline-friendly testing, DevOps metrics and enterprise DevOps. - [Elastic Leadership](https://www.elasticleadership.com): Elastic Leadership, Roy's framework for software team leaders (survival, learning and self-organizing modes). ### Social - X: https://x.com/royosherove - LinkedIn: https://www.linkedin.com/in/osherove/ ### Contact - Contact form: https://forms.gle/jQSx5KoXvrVA1JCK7 ### License Licensed under CC BY 4.0 — reuse, quote and adapt with attribution (Roy Osherove, link to the original page). License: https://creativecommons.org/licenses/by/4.0/