Still looking for a sponsor Max Paulousky is looking for a Silverlight/.Net job in the Commonwealth

Share to Facebook Tweet this! Share to MySpace Share to Google Share to Live   Share via AddThis

To Remember: Why to Use or Not to Use Unit Testing

Developers should (not) use unit testing. Some arguments for future interviews:

Pros:

  • Of course, tests help to keep an application in consistent state;
  • Developers should avoid using static classes, because they cannot be mocked and tested;
  • Developers should test classes with a lot of dependencies on other objects or classes. Using containers like Unity, Castle Windsor etc is very helpful because it decouples components of applications, simplifies design etc. 

All these facts helps to create awesome architecture.

Contras:

  • I do not remember who has said but unit testing increases duration of the development stage by 30%. I agree;
  • In some time after starting using testing, developers rely on tests more and more and they may miss important bugs.

Any other ideas?

This work is licensed under a Creative Commons Attribution By license.
Comments have been closed on this topic.