Comments on: 10 Reasons to Write Unit Tests http://annafilina.com/blog/10-reasons-to-write-unit-tests/ I fix stuff Thu, 19 Apr 2012 12:13:44 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Ashay http://annafilina.com/blog/10-reasons-to-write-unit-tests/comment-page-1/#comment-6601 Ashay Wed, 27 Oct 2010 15:47:31 +0000 http://annafilina.com/blog/?p=470#comment-6601 While I agree that unit tests and functional tests are required, I more of a proponent of test first programming. Not only does it force you to think thru the functionality to be coded, it also helps validate that the test will fail when it needs to and then one can also see if sufficient failure information is being captured for the inevitable triage/debug. While I agree that unit tests and functional tests are required, I more of a proponent of test first programming. Not only does it force you to think thru the functionality to be coded, it also helps validate that the test will fail when it needs to and then one can also see if sufficient failure information is being captured for the inevitable triage/debug.

]]> By: Anna http://annafilina.com/blog/10-reasons-to-write-unit-tests/comment-page-1/#comment-3651 Anna Wed, 09 Jun 2010 12:23:15 +0000 http://annafilina.com/blog/?p=470#comment-3651 I agree that functional tests are also necessary. I could not live without these. I agree that functional tests are also necessary. I could not live without these.

]]> By: Travis Calder http://annafilina.com/blog/10-reasons-to-write-unit-tests/comment-page-1/#comment-3612 Travis Calder Sat, 05 Jun 2010 01:39:53 +0000 http://annafilina.com/blog/?p=470#comment-3612 I agree that Unit Tests are very useful, and these are things that Unit Tests might help with. However, I think you are talking about Automated Testing in general, not Unit Tests. Unit Tests are intended to test the smallest units they can get a hold of. This leads to the use of mocking and stubbing. When the assumptions of one unit change, the mocks/stubs of it used elsewhere do not. The code that uses these mocks/stubs still makes out-of-date assumptions. Without other forms of testing, such as Functional Testing which tests larger integrated pieces, you actually will not catch many bugs with your test. Worse, you'll be more prone to them because you'll feel safer than you really are. I talk a little bit at my blog about what Unit Tests do and do not do: http://codequirks.com/2010/05/27/why-failing-tests-make-refactoring-safe/ More on that topic will be coming soon. I agree that Unit Tests are very useful, and these are things that Unit Tests might help with.

However, I think you are talking about Automated Testing in general, not Unit Tests.

Unit Tests are intended to test the smallest units they can get a hold of. This leads to the use of mocking and stubbing. When the assumptions of one unit change, the mocks/stubs of it used elsewhere do not. The code that uses these mocks/stubs still makes out-of-date assumptions.

Without other forms of testing, such as Functional Testing which tests larger integrated pieces, you actually will not catch many bugs with your test. Worse, you’ll be more prone to them because you’ll feel safer than you really are.

I talk a little bit at my blog about what Unit Tests do and do not do:
http://codequirks.com/2010/05/27/why-failing-tests-make-refactoring-safe/

More on that topic will be coming soon.

]]> By: Nirav Assar http://annafilina.com/blog/10-reasons-to-write-unit-tests/comment-page-1/#comment-3609 Nirav Assar Fri, 04 Jun 2010 13:14:21 +0000 http://annafilina.com/blog/?p=470#comment-3609 These are very good points made. The notion of resisting unit tests in development is also rooted in a lack of experience or acknowledgment that software if defect prone and is costly, no matter how expert the developer. I tried to lay out some point for unit testing in my post. Please see below: http://assarconsulting.blogspot.com/2009/10/perils-of-not-unit-testing.html These are very good points made. The notion of resisting unit tests in development is also rooted in a lack of experience or acknowledgment that software if defect prone and is costly, no matter how expert the developer. I tried to lay out some point for unit testing in my post. Please see below:

http://assarconsulting.blogspot.com/2009/10/perils-of-not-unit-testing.html

]]> By: Michelangelo van Dam http://annafilina.com/blog/10-reasons-to-write-unit-tests/comment-page-1/#comment-3601 Michelangelo van Dam Thu, 03 Jun 2010 14:36:02 +0000 http://annafilina.com/blog/?p=470#comment-3601 Anna, You've given me another clue bat to swing around, unfortunately some people are… *carefully choosing my words here* …finding excuses not to unit test. Maybe this simple overview will help me convince them to rethink their current opinions. Thanks. Anna,

You’ve given me another clue bat to swing around, unfortunately some people are… *carefully choosing my words here* …finding excuses not to unit test. Maybe this simple overview will help me convince them to rethink their current opinions.

Thanks.

]]> By: Anna http://annafilina.com/blog/10-reasons-to-write-unit-tests/comment-page-1/#comment-3592 Anna Thu, 03 Jun 2010 03:12:12 +0000 http://annafilina.com/blog/?p=470#comment-3592 I choose PHPUnit for my unit testing needs. The project is thouroughly documented. Here's a solid introduction by Sebastian Bergmann: http://www.slideshare.net/sebastian_bergmann/testing-php-applications-with-phpunit-3-8227 I know that his company offers trainings. He can explain good test writing better than I can. I choose PHPUnit for my unit testing needs. The project is thouroughly documented.

Here’s a solid introduction by Sebastian Bergmann: http://www.slideshare.net/sebastian_bergmann/testing-php-applications-with-phpunit-3-8227

I know that his company offers trainings. He can explain good test writing better than I can.

]]> By: pascall http://annafilina.com/blog/10-reasons-to-write-unit-tests/comment-page-1/#comment-3579 pascall Wed, 02 Jun 2010 12:07:18 +0000 http://annafilina.com/blog/?p=470#comment-3579 Very interesting but, i could be fine to explain the best way to write unit tests... or may be listing existing tools (ex: PHPUnit...), or library... or just explaining how to do it. Very interesting but, i could be fine to explain the best way to write unit tests…
or may be listing existing tools (ex: PHPUnit…), or library… or just explaining how to do it.

]]> By: Anna http://annafilina.com/blog/10-reasons-to-write-unit-tests/comment-page-1/#comment-3562 Anna Tue, 01 Jun 2010 20:02:15 +0000 http://annafilina.com/blog/?p=470#comment-3562 <a href="#comment-3538" rel="nofollow">@Jason Sweat </a> I totally agree with you. @Jason Sweat
I totally agree with you.

]]> By: Jason Sweat http://annafilina.com/blog/10-reasons-to-write-unit-tests/comment-page-1/#comment-3538 Jason Sweat Tue, 01 Jun 2010 00:28:42 +0000 http://annafilina.com/blog/?p=470#comment-3538 As a corollary to 5, you can actually code a test to demonstrate a bug, fix it, and then leave it in your test suite so you guarantee you don't ever re-introduce a bug. As a corollary to 5, you can actually code a test to demonstrate a bug, fix it, and then leave it in your test suite so you guarantee you don’t ever re-introduce a bug.

]]>