News Feeds

Overview

BizUnit is a test framework that is intended to test integration solutions. Although primarily used for testing Biztalk solutions, BizUnit has a number of libraries addressing different products not just BizTalk.

BizUnit takes a black box approach to testing the Biztalk solution and it is based on "externally observable behavior". For instance, if you are testing an orchestration that picks up data from a database and writes to a file, then with BizUnit you would write a step that loaded the data into the database, checked the folder for the file and optionally validated its contents. Steps can be authored in XML or in a strong typed manner using the new object model (in v3.0). The main workspace explains how BizUnit works in detail.

This project, BizUnitExtensions is a community "Contrib" project providing test step libraries to enhance the reach of BizUnit. Please note that Extensions is not a fork of the core BizUnit code base anymore although it did originally start life as such. All the Extension steps are contained in separate assemblies (and the namespace is BizUnit.Extensions.<TargetProduct>). These assemblies depend on main BizUnit assembly as well as any other third party product they address (such as EntLib).You can simply drop the extensions assemblies into your runtime folders and use them.

This project is currently owned and contributed to by Santosh Benjamin and Gar Mac Críosta. Our colleagues have also contributed steps and suggestions. We welcome more participation and contributions. If you have any questions or would like to contribute, do get in touch via this workspace.

Current Release

25-May-2009
The first beta release of Extensions v3.0 is ready. This release now incorporates the object model throughout. The main Extensions steps and the BizTalk steps have been tested out and should be quite stable. The Oracle and EntLib steps are next on the agenda (in that order). Bram Veldhoen has also contributed some steps for Pipeline Testing (linking in with Tomas Restrepo's library) and those steps will be included in Beta-2. The namespaces and assembly names have been given a complete overhaul so any existing test cases will have to be updated to reflect these. There is an article linked below describing the changes in more detail.

Current TestStep Libraries

This is the current set of libraries. The Roadmap page should give an idea of the other libraries we are considering. Please refer to the Documentation page for a complete set of steps in each library.
  • BizUnit.Extensions - General Steps such as DotNetObjectInvokerEx, SoapHttpRequestResponseEx, XmlPokeStep etc.
  • BizUnit.Extensions.BizTalk - Application ConductorStep, MapExecutingStep etc.
  • BizUnit.Extensions.EntLib - EntLib based DBQueryStep, DatabaseDeleteStep etc
  • BizUnit.Extensions.Oracle - OracleDBQueryStep.

Target BizTalk Version(s): BizUnitExtensions 3.x (and BizUnit 3.x) target BizTalk Server 2006 and upwards. The BizTalk steps make use of the ApplicationName and so they cannot be used with BizTalk 2004. Old releases of both projects would be able to support BizTalk 2004, however features such as the object model (strong typed usage), bug fixes etc will not be available. Additionally, there have been changes to code structure, namespaces, partitioniong of steps into different assemblies etc which will not be available in older versions. If you want to use it with BizTalk 2004, then you will need to modify the source to ignore the Biztalk application name and adjust the code accordingly.

Workspace Contents

1. FAQ : Frequently asked questions about this project
2. Documentation : What's In the box and how do I use it?
3. Roadmap : whats cooking and where are we going?

Blog Posts & Articles

1. Overview of v3 Beta-1


Last edited Jun 3 at 8:45 AM by santoshbenjamin, version 38

 

Want to leave feedback?
Please use Discussions or Reviews instead.

Updating...
© 2006-2009 Microsoft | About CodePlex | Privacy Statement | Terms of Use | Code of Conduct | Version 2009.6.1.15196