Skip to main content

Lab Management in Visual Studio 2010 Released

In my experience, there's a lot of animosity and poor communication between Development and QA. It's not that they don't appreciate one another so much as they never seem to stay on the same page.

QA: "What's the status on defect #4874?"
Dev: "Done."
QA: "Done?"
Dev: "Yeah, I fixed that Tuesday."
QA: "Err, ok. Well where is it? I mean where can I verify it?"
Dev: "No clue. I committed it Tuesday. It passed unit tests and built successfully."
QA: "Alright. I'll track it down."

Invariably, QA speaks with the build manager (if there is one) to find the build in which that defect was repaired. After discovering the correct build, now QA needs an environment stood up to house that build. But wait, the UAT environment is currently testing the next release. It can't be disturbed for another week.

At this point, the QA person's blood pressure heads for unsafe levels and the browsing begins. But it doesn't have to be this way...

Lab Management in Visual Studio 2010 along with TFS solves many of these pains. Here's what the above scenario might look like with Lab Management:

QA doesn't inquire to the Dev about #4874 because it's already marked Resolved and back in QA's list of Defect Work Items. It's associated with a Continuous Integration Team Build instance which is marked with a Build Quality of Ready for UAT (meaning all unit tests passed and the build compiled successfully). Behind the scenes, as part of the build, Lab Management spun up a virtual web server, application server and database server. Team Build deployed the solution to this virtual environment and even sent an email to the build manager and the QA person (they chose to be alerted) saying this environment was ready for testing. This shop is currently testing four pending releases along with a production hotfix that's going out later today--all at the same time in completely separate environments.

Best of all, it's an amazing value. If you made/make the investment in Visual Studio 2010 Ultimate, you get Lab Management for free. Yes, that's right: free. That said, you will need some not insignificant hardware to serve as a host for these virtual servers...but you have that already, right?


It seems like a very good web site but my English is not good. But, I like this web site very much.

By the way, Thanks for the this information.

Popular posts from this blog

Get Your Team Foundation Server Hate On!

[Google ranking skyrockets... ;-)] I'm a big fan of TFS/VSTS. However, there are a good pocket of folks who take issue with the way TFS handles or implements a certain feature. Well this is your chance to vent! I'm planning a presentation around the "Top 10 TFS/VSTS Hates and How to Alleviate Them"...or something along those lines. But I need your help. Post a comment below detailing your dislike. If it's legitimate, I'll highlight it in the presentation and [hopefully] provide an alternative, resolution, or work-around. Thanks in advance! Update 7/19/2008: Version Control and Microsoft

Rollback a Ooops in TFS with TFPT Rollback

Rhut roe, Raggie. You just checked in a merge operation affecting 100's of files in TFS against the wrong branch. Ooops. Well, you can simply roll it back, right? Select the folder in Source Control Explorer and...hey, where's the Rollback? Rollback isn't supported in TFS natively. However, it is supported within the Power Tools leveraging the command-line TFPT.exe utility. It's fairly straightforward to revert back to a previous version--with one caveot. First, download and install the Team Foundation Power Tools 2008 on your workstation. Before proceeding, let's create a workspace dedicated to the rollback. To "true up" the workspace, the rollback operation will peform a Get Latest for every file in your current workspace. This can consume hours (and many GB) with a broad workspace mapping. To work around this, I create a temporary workspace targeted at just the area of source I need to roll back. So let's drill down on our scenario... I'm worki

Installing the .Net Framework 3.0 SP1 on Windows 2003 Server

I'm building an [automated] build server requiring the .Net 2.0 and 3.0 runtime. Unfortunately, at my client, they leverage a proxy server. The standard .Net 3.0 SP1 framework redist is really just a bootstrapper. Logged in as a local admin on the box, I didn't have the opportunity to authenticate the installation EXE with my domain credentials. So, the install kept timing out. Finally, I found this helpful post from Aaron Ruckman on how to download the very elusive, full framework package. It's here , BTW (x86). I finally get the full installation EXE downloaded to a fileshare, re-run the install and wham--" XPSEPSC: XPS must be installed..." Excuse you? This isn't an XPS's a VM. I found a few MSDN posts here and here outlining the problem. I'm still not clear on what XPSEPSC does (Google yielded little) but you can download it here (x86) . After installing XPSEPSC, the framework installed without issue. Update : Somewhat related, there i