Coding Horror: Alpha, Beta, and Sometimes Gamma
Gold – The software is finished — and by finished, we mean there are no show-stopping, little-children-killing bugs in it. That we know of. There are probably numerous lower-prority bugs triaged into the next point release or service pack, as well.
Brilliant, just brilliant! Worth a read!
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.
In my last job (Synergi Solutions AS) we talked a bit about creating virtual machines as output of our nightly/release builds, but never got around to actually doing it. I just found a link to somebody who’s actually done it; http://tranxcoder.wordpress.com/2008/05/14/using-the-vixcom-library/