I've taken up again the development og BizMock and this are the new features i've incorporated 

  1. New t4 template to automate artifacts code generation
  2. New facilities to simplify the setup of the biztalk artifacts.
  3. New Project template to simplify Bizmock Test creation
  4. New sample scenarios

And this are the things i'm thinking of adding in the future:

  • UI Wizard to generate the artifacts.xml that feed the t4 template. For the moment this xml has to be edit manually.
  • Integrate BizMock with a functional test tools like FIT or story teller or custom
  • New facilities to generate dynamically at development time new artifacts, add methods or properties
  • More rich error reporting & logging.
  • Add more tests and samples for different scenarios
  • Create a visual studio guidance around BizMock that goes from planning to building to stabilizing biztalk solutions

This are the features BizMock is trying to address:

  • Isolated test environment: automated tests executing in a single machine (developer or integration server).
  • Dynamic emulation: tests can dynamically mock the messages received from external systems.
  • Unified API: all the BizTalk artifacts are tested using the same fluent interface API: orchestrations, maps, pipelines, schemas, use the same paradigm and artifacts can be reused across tests
  • Domain Driven: tests are written at a higher level of abstraction, using BizTalk domain concepts like ports, maps, orchestration. These artifacts can be tailored and encapsulated using C# object orientation. For example xpath queries, DB commands, complex validation logic are put out of sight of the developer.
  • Integrated Development Environment: integrated with VS, uses MS Test, project templates, artifacts deployment & configuration is automated, the artifacts code is auto-generated using T4 templates
  • Code Productivity: fluent Interface API with intelisense, artifact reusability across tests, artifact dynamic adjustments at runtime.
  • Extensibility: allows several points of extension by allowing the creation of new artifact types, actions, fluent interfaces, etc.
  • Completeness: The tests can exercise all the solution from the receive adapter, to the send adapters, the local databases, helper components and passing by the message box; although some artifacts like maps, pipeline components and schemas are tested in isolation from the BizTalk infrastructure.
  • Agility: allow continuous integration & Promote Test Driven Development, Domain Driven Design approaches

check it out at : http://bizmock.codeplex.com

Please, I need feedback!