What's good with the new version of Visual Studio .Net is that they are including stuff to be able to support XP concepts. What I dislike is the fact that, once again, microsoft isn't looking how stuff really will be used by real programmers in real projects. Nunit-Addin really rox, and it really helps the Red-Green-Refactor cycle. The only thing we're missing right now is the automatically generating of the classes you wanna test, so that everything compiles again.
So it would be
- Write specs
- Write tests based on specs
- Review whether it works, or go back to change specs
- Create empty/mockup classes so stuff compiles
- Implement classes so the lights go green.
- refactor if specs "don't work", or implementation is crap
I kind of think of myself as an extremely interested observer. I am not on the development team that built the unit testing tool in VS Team System. They have done an excellent job building the tool and I agree it does need a bit more polish but please remember we are looking at a Tech Preview. I have collaborated with the team on a number of occasions and I have been working with them providing feedback on some features as well as problems with the existing implementation. With regard to the issue of adding tests to an existing project I will be blogging some information on how to do this before the end of the week (18 June).
James I appreciate your comments. Can't wait to see what you guys come up with next.