When is unit-testing bad?

Kyle Yancey kyle at lakeofburningfire.org
Sat Jul 5 04:45:46 CEST 2003


Puffin looks nice, although it has undergone some changes that haven't
been documented yet.

Part I
http://www-106.ibm.com/developerworks/opensource/library/os-puffin.html

Part II
http://www-106.ibm.com/developerworks/opensource/library/os-puffin2.html

On Thu, 03 Jul 2003 15:47:56 +0300, Edvard Majakari
<edvard+web at majakari.net> wrote:

>On Wed, 2 Jul 2003, ageron at HOHOHOHOvideotron.ca wrote:
>
>> threads?  A lot of projects would be better off not using them, I agree
>> with that, but some projects just can't do without them!  Web sites are
>> also horrible to automatically unit test.  In all those cases, I much
>> prefer having a human being go out and do the unit tests manually.
>
>Which reminds me: I've seen two web unit testing frameworks, one which was
>by the originial PyUT author, and the other that seemed more complete,
>though not so well documented either.
>
>I've fancied developing one myself - so I'd like to know what kind of
>things should I take into account before trying such a largish project?  I
>know that it is hard to test Web-based applications, for one thing - the
>user doesn't usually type GET parameters to the URL, while doing so could
>be the only possible way to do automated web site testing. Ideas/comments?





More information about the Python-list mailing list