Tag Archives: unit testing

Announcing Isolator for Sharepoint with a free full license for bloggers – ISerializable – Roy Osherove’s Blog

We’re just now starting a huge Sharepoint project and this new edition of Isolator might be good for that project. I’ll need to try it out!

And they’re even giving it away for free! 50 licenses anyways. I’m hoping there’s one for me! For that to happen I have to include this text:

Typemock are offering their new product for unit testing SharePoint called Isolator For SharePoint, for a special introduction price. it is the only tool that allows you to unit test SharePoint without a SharePoint server. To learn more click here.

The first 50 bloggers who blog this text in their blog and tell us about it, will get a Full Isolator license, Free. for rules and info click here.

Announcing Isolator for Sharepoint with a free full license

So that’s cool! So, if I do happen to get a free license I’ll tell you all about it, right here!

for bloggers – ISerializable – Roy Osherove’s Blog

Using BizUnit with the Business Process Management Scenario

Using BizUnit with the Business Process Management Scenario

This topic will utilize one of the end-to-end scenarios provided with BizTalk Server 2006 and show how you can use the techniques described so far to perform automated functional and performance testing of the solution. This provides a realistic scenario to help determine how the tools and techniques presented in this guide can be used to incorporate testing into BizTalk Server solutions.

A thorough walk through on how to use BizUbit with a large BizTalk solution. I feel that the biggest problem with automated BizTalk testing is the endpoints. I mean, I don’t have an MSMQ, ehm, queue running on my machine… Neither does the guy next to me, but the guy behind me does. What I’m getting at here is this: For unit testing to work you have to isolate the test and for integration tests you have to run in a “as real world as possible” environment. Faking a SAP or Meridio server isn’t easy when doing integration testing… But perhaps you could just use the test environment? I need to think more on this I guess.