Monday, May 23, 2005


ASP.NET 2.0 and VWD = Under Development

I am always curious to know about what goes into building a terribly good software, the time, the energy, the focus, the commitment, the passion…….specially something which really impresses me or something I really like.

Read this excellent post from Scott Guthrie describing how tests are run under Microsoft for any upcoming product and specifically ASP.NET 2.0 and Visual Web Developer, for example here is an excerpt from his post.

“My team uses an internally built system we affectionately call “Maddog” to handle managing and running our tests. Post Whidbey my team will be looking to transition to a VSTS one, but for right now Maddog is the one we use.


My team currently has 4 labs where we keep approximately 1,200 machines that Maddog helps coordinate and keep busy. The machines vary in size and quality – with some being custom-built towers and others being rack-mounts. Here is a picture of what one row (there are many, many, many of them) in one of labs in building 42 looks like:

The magic happens when we use Maddog to help coordinate and use all these machines. A tester can use Maddog within their office to build a query of tests to run (selecting either a sub-node of feature areas – or doing a search for tests based on some other criteria), then pick what hardware and OS version the tests should run on, pick what language they should be run under (Arabic, German, Japanese, etc), what ASP.NET and Visual Studio build should be installed on the machine, and then how many machines it should be distributed over.

Maddog will then identify free machines in the lab, automatically format and re-image them with the appropriate operating system, install the right build on them, build and deploy the tests selected onto them, and then run the tests. When the run is over the tester can examine the results within Maddog, investigate all failures, publish the results (all through the Maddog system), and then release the machines for other Maddog runs. Published test results stay in the system forever (or until we delete them) – allowing test leads and my test manager to review them and make sure everything is getting covered. All this gets done without the tester ever having to leave their office.”

Now that’s awesome, read the post for some more insights that we would probably don't know otherwise.
Comments: Post a Comment

<< Home

This page is powered by Blogger. Isn't yours?