[prev in list] [next in list] [prev in thread] [next in thread] 

List:       nyphp-talk
Subject:    [nyphp-talk] unit testing, was Survey: Development environment....
From:       David Mintz <vtbludgeon () gmail ! com>
Date:       2009-05-06 13:37:56
Message-ID: 721f1cc50905060637l4afeb0e4hab0835985fa7932d () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


I get the impression that most developers report that they do automated
testing or they are trying to learn. Only a minority seem to be answering
flat-out no.

imho one of the major differences between a polished professional and a
hobbyist is responsible testing. That's why I still kick myself, as sort of
an eternal wannabe whose day-job description has zero to do with IT, but who
aspires nevertheless to write code that can be judged competent by any
standard:  I still haven't gotten the hang of unit testing, though I have
made some attempts to get religion and vow to keep trying.

It seems that I am not alone. So the question is, why is it hard for some to
adopt the practice? One thing that occurs to me is that maybe it isn't
really that easy to write good tests. We've all seen examples of how to test
a function that returns the sum of x + y -- thanks a lot. It's a little
harder to create simulated http environments complete with cookies and
sessions -- though people (e.g., the ZF team) have done wonderful things to
make it easier -- and forsee all the use cases in a complex app. Evidence
for the proposition that it's hard to write an exhaustive set of tests is
that you have products like the Zend Framework which is unit-tested to death
before release, and then the next release brags that 171 bugs were fixed.

-- 
David Mintz
http://davidmintz.org/

The subtle source is clear and bright
The tributary streams flow through the darkness

[Attachment #5 (text/html)]

I get the impression that most developers report that they do automated testing or \
they are trying to learn. Only a minority seem to be answering flat-out \
no.<br><br>imho one of the major differences between a polished professional and a \
hobbyist is responsible testing. That&#39;s why I still kick myself, as sort of an \
eternal wannabe whose day-job description has zero to do with IT, but who aspires \
nevertheless to write code that can be judged competent by any standard:  I still \
haven&#39;t gotten the hang of unit testing, though I have made some attempts to get \
religion and vow to keep trying. <br> <br>It seems that I am not alone. So the \
question is, why is it hard for some to adopt the practice? One thing that occurs to \
me is that maybe it isn&#39;t really that easy to write good tests. We&#39;ve all \
seen examples of how to test a function that returns the sum of x + y -- thanks a \
lot. It&#39;s a little harder to create simulated http environments complete with \
cookies and sessions -- though people (e.g., the ZF team) have done wonderful things \
to make it easier -- and forsee all the use cases in a complex app. Evidence for the \
proposition that it&#39;s hard to write an exhaustive set of tests is that you have \
products like the Zend Framework which is unit-tested to death before release, and \
then the next release brags that 171 bugs were fixed. <br> <br>-- <br>David \
Mintz<br><a href="http://davidmintz.org/">http://davidmintz.org/</a><br><br>The \
subtle source is clear and bright<br>The tributary streams flow through the \
darkness<br>



_______________________________________________
New York PHP User Group Community Talk Mailing List
http://lists.nyphp.org/mailman/listinfo/talk

http://www.nyphp.org/show_participation.php

[prev in list] [next in list] [prev in thread] [next in thread]