[TIP] Testing Hierarchy
noah.gift at gmail.com
Mon Jul 20 11:37:11 PDT 2009
On Mon, Jul 20, 2009 at 11:31 AM, C. Titus Brown <ctb at msu.edu> wrote:
> 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>
> -> > 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
> -> you can have two of the three, "cheap, fast, or quality", but not all
> -> comes mind.
> -> It is very easy to say all code should have 100% unit test coverage,
> -> integration tests, functional tests, etc. What I haven't seen someone
> -> about yet, is when that is appropriate in the real world and when it
> -> and an honest assessment of the tradeoff. I am very sold on testing
> -> 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. ;)
Yes. I generally find your opinions useful. I think a lot of Python
testing theory is in the "Abstinence Cures Aids" phase :)
> 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.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the testing-in-python