Comments on: When Unit Testing Doesn’t Work http://blog.brodzinski.com/2009/04/when-unit-testing-doesnt-work.html Dealing with software projects in real life Thu, 29 Jul 2010 10:46:22 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Cloud Computing http://blog.brodzinski.com/2009/04/when-unit-testing-doesnt-work.html#comment-2248 Cloud Computing Sat, 31 Oct 2009 06:52:23 +0000 http://blog.brodzinski.com/2009/04/when-unit-testing-doesn%e2%80%99t-work.html#comment-2248 Nice to see a detailed article on Testing, now days many companies prefer to have tester in their own premises so that they can do the testing process along with development process. I have bookmarked your blogging site :) Nice to see a detailed article on Testing, now days many companies prefer to have tester in their own premises so that they can do the testing process along with development process. I have bookmarked your blogging site :)

]]> By: Software Development Company http://blog.brodzinski.com/2009/04/when-unit-testing-doesnt-work.html#comment-2247 Software Development Company Wed, 03 Jun 2009 11:01:41 +0000 http://blog.brodzinski.com/2009/04/when-unit-testing-doesn%e2%80%99t-work.html#comment-2247 Nice explanation... your points are correct to some extent, but still various companies prefer to have unit testing their development cycle... Nice explanation… your points are correct to some extent, but still various companies prefer to have unit testing their development cycle…

]]> By: Vukoje http://blog.brodzinski.com/2009/04/when-unit-testing-doesnt-work.html#comment-2246 Vukoje Mon, 20 Apr 2009 18:19:00 +0000 http://blog.brodzinski.com/2009/04/when-unit-testing-doesn%e2%80%99t-work.html#comment-2246 Excellent reminder to keep focus tests quality. Unit tests introduce completely new challenges, that will introduce great problems if not considered in project early phases. Excellent reminder to keep focus tests quality. Unit tests introduce completely new challenges, that will introduce great problems if not considered in project early phases.

]]> By: Pawel Brodzinski http://blog.brodzinski.com/2009/04/when-unit-testing-doesnt-work.html#comment-2245 Pawel Brodzinski Mon, 20 Apr 2009 07:16:00 +0000 http://blog.brodzinski.com/2009/04/when-unit-testing-doesn%e2%80%99t-work.html#comment-2245 Radenko,<br /><br />Actually if you bring <a HREF="http://www.joelonsoftware.com/items/2009/01/31.html" REL="nofollow">discussion between Jeff and Joel</a> I linked to then they actually answered this question:<br /><br />"<i>Like, you don't want to have an Employee class, because it's got his name which might get changed if he gets married, and it has his salary, which might get changed if he gets a raise. Those have to be two separate classes, because they get changed under different circumstances. And you wind up with millions of tiny little classes, like the EmployeeSalary class</i>"<br /><br />My approach is pretty aligned. I don't think single responsibility principle should be applied very conservatively. Of course we can discuss this issue but that's not my point.<br /><br />My point is vast majority of software isn't written in accordance to single responsibility principle. That doesn't mean you shouldn't use unit testing there. What more, there are people out there (including me) who wouldn't follow SRP blindly but they'd use unit testing. Radenko,

Actually if you bring discussion between Jeff and Joel I linked to then they actually answered this question:

“Like, you don’t want to have an Employee class, because it’s got his name which might get changed if he gets married, and it has his salary, which might get changed if he gets a raise. Those have to be two separate classes, because they get changed under different circumstances. And you wind up with millions of tiny little classes, like the EmployeeSalary class“

My approach is pretty aligned. I don’t think single responsibility principle should be applied very conservatively. Of course we can discuss this issue but that’s not my point.

My point is vast majority of software isn’t written in accordance to single responsibility principle. That doesn’t mean you shouldn’t use unit testing there. What more, there are people out there (including me) who wouldn’t follow SRP blindly but they’d use unit testing.

]]> By: Radenko Zec http://blog.brodzinski.com/2009/04/when-unit-testing-doesnt-work.html#comment-2244 Radenko Zec Sun, 19 Apr 2009 10:24:00 +0000 http://blog.brodzinski.com/2009/04/when-unit-testing-doesn%e2%80%99t-work.html#comment-2244 If one little change in your code is resulted in 10% tests to be crashed you are not working your software based on SOLID or Single responsibility principle? If one little change in your code is resulted in 10% tests to be crashed you are not working your software based on SOLID or Single responsibility principle?

]]> By: johnfmoore http://blog.brodzinski.com/2009/04/when-unit-testing-doesnt-work.html#comment-2243 johnfmoore Thu, 16 Apr 2009 22:07:00 +0000 http://blog.brodzinski.com/2009/04/when-unit-testing-doesn%e2%80%99t-work.html#comment-2243 Good post Pawel. Unit tests are only useful if written correctly, executed with every build, and maintained. I was reading another post on unit testing, the excuses people use for not writing them:<br /><br />http://bit.ly/Acmd<br /><br />which is worth a review.<br /><br />Feel free to also check out my older post on the topic at:<br /><br />http://bit.ly/tgLYO<br /><br />John Good post Pawel. Unit tests are only useful if written correctly, executed with every build, and maintained. I was reading another post on unit testing, the excuses people use for not writing them:

http://bit.ly/Acmd

which is worth a review.

Feel free to also check out my older post on the topic at:

http://bit.ly/tgLYO

John

]]>