[TIP] Testing Hierarchy

C. Titus Brown ctb at msu.edu
Mon Jul 20 11:31:45 PDT 2009


On Mon, Jul 20, 2009 at 11:24:46AM -0700, Noah Gift wrote:
-> On Mon, Jul 20, 2009 at 10:24 AM, Terry Peppers <peppers at gmail.com> wrote:
-> 
-> > Paul -
-> >
-> > That would be me and it would also be here.
-> >
-> > http://bitbucket.org/terryp/pycon_2009_tip_bof/
-> >
-> 
-> That is a good presentation.  In an earlier thread I mentioned how I was
-> frustrated at the lack of real world theory with testing.  I think this
-> presentation could go a tad further and identify not only the type of
-> testing, but the levels of testing quality vs "the real world".  The saying
-> you can have two of the three, "cheap, fast, or quality", but not all three
-> comes mind.
-> 
-> It is very easy to say all code should have 100% unit test coverage, have
-> integration tests, functional tests, etc.  What I haven't seen someone talk
-> about yet, is when that is appropriate in the real world and when it isn't,
-> and an honest assessment of the tradeoff.  I am very sold on testing code,
-> but how much depends on the situation I am in.
-> 
-> PyCon 2010 Grig and Titus?

What, you want some more uninformed opinion?  Sure thing, that's my
specialty. ;)

There are entire newsgroups, books, mailing lists, and professional
societies devoted to figuring out the tradeoff... not sure what I can
add in general.

I'll be giving a talk on this subject wrt science (where I *can* say
something...) in Toronto next Wednesday, passport gods willing.

--titus



More information about the testing-in-python mailing list