|As a company, we have committed ourselves to using TFS as a core component of our development environment. At the moment, any automated testing we do is done on the build server and is substantially at a unit test level. I perceive the need to expand this into system testing and therefore deploying onto multiple machines (client, web server, database). To this end, I have started looking at Microsoft Lab Management.
It looks like it has potential, but all the demos I see seem to show a simple build of a single module, deploy and test. Whereas in my company we have multiple teams deploying multiple modules having dependencies between them.
As an example, say a change to a service requires a database change as well. I can get the build of the service to kick off the Lab Management deployment, and I understand that I can add a database deployment script to the Lab Management build but it does not really seemed joined up especially as we start to see Visual Studio SQL Projects that will have their own builds. This is a simple example whereas in real life we may have multiple services and databases that need to be aligned for a complete system deployment.
I suspect I am asking too much of the Lab Management product. Any comments on how you use Lab Management?
All round good guy.