Software development, like riding a bicycle or any other methodical process, should get easier as time progresses. Brian Randell believes development actually gets harder.
Give end users one look at Office 2007, Randell argued at the beginning of his Tech Ed 2006 session, "Visual Studio 2005 Team Edition for Software Developers," and they will expect nothing less than that in their applications. That, combined with expectations of a more public process for beta software releases, puts the onus on developers to crank out applications quickly.
One pitfall of such deadline pressure is that it often causes developers to skimp on application testing. If a development team uses only one error detection method, then it can expect a success rate of no more than 75%, with an average of only 40%, said Randell, senior consultant, MCW Technologies.
"You need to have multiple tools in your tool belt to solve the problem. Unit testing is a great method, but can't be the sole method," Randell continued.
That is where Visual Studio 2005 Team System enters the picture. The product gives architects, developers and testers collaboration tools for the development life cycle. Unit testing is part of the package; so are tools for debugging, visualizing and refactoring code, Randell said. (Exactly what features are available depends on what edition of Team System an IT pro is running. Details can be found in our VSTS Learning Guide.)
Mere testing is not enough for an application because, by definition, all testing does is find errors within code, Randell said. Debugging, for example, identifies what went wrong with a string of code and how it must be fixed.
Randell also pointed out a few other testing elements of Visual Studio Team System. They include the following:
Moreover, all the data generated from testing, refactoring and the like can be published to Team Foundation Server for an entire project team to see.