Unit Testing
I always thought Unit Testing was real easy and obvious thing to do until I met this customer who was managing a fairly large .Net team. The developers were familiar with the concept of unit testing.
However their internal research showed that they were spending lot of dollars fixing bugs which were discovered in system testing phase. Doing a further root-cause analysis revealed that they were not doing enough unit testing. This was because it was not mandated by the management and also the tools they were using for unit testing were not integrated enough to do this seamlessly.
So there performance improvement plans core requirements were
a) Unit Testing,
b) Static code Analysis,
c) Resource utilization and memory leaks.
They would also be able to put some kind of mandate by which code coverage criteria is of a higher percentage for complex programs and lower for simple programs. They also would want to have check-in rules which would only allow compiled error free code in the version control repository.
VSTS dev edition with TFS would make this place a heaven.
Comment Notification
If you would like to receive an email when updates are made to this post, please register here
Subscribe to this post's comments using
Comments
Leave a Comment
About sukrishn
I studied Physics and Production Engineering in India. I later graduated with a Masters degree in Computer Science from Unversity of Western Sydney. I started my career in late nineties and
I worked with Accenture, ThoughtWeb, Rational Software, IBM and now Microsoft.
I am not a 'regular' blogger but I plan to post a blog about things I am interested in or related to my work - Visual Studio Team System