[TIP] test results tracking, etc...

C. Titus Brown ctb at msu.edu
Sun Apr 5 20:21:26 PDT 2009

On Sun, Apr 05, 2009 at 09:22:32PM -0400, Douglas Philips wrote:
-> On or about 2009 Apr 5, at 1:07 PM, Vicki Laidler indited:
-> > I gave a lightning talk at the TIP BoF on a lightweight test
-> > management & reporting system we've developed. It's deliberately
-> > designed with loose coupling among the components so that any
-> > test runner that produces a compatible report can use the database
-> > and reporting interface. We've also got a nose plugin that generates  
-> > a compatible
-> > report.
-> I actually was that BoF and while I'd like to say I remember specific  
-> LTs at this point, I don't. noob overload probably.

It was a great talk... I'm looking forward to hearing more about

-> Actually if you write up the docs and document the formats needed, I  
-> like to see that spark a discussion here. I know Titus is in favor of  
-> simplest-thing-that-could-possibly work, so I suspect that will be  
-> Pass/Fail. Personally I prefer to hard-coded valus even in simple  
-> systems. (The simplest code I know how to write is always "table- 
-> driven" and usually doesn't need to know or care about specific values.)

Sadly not everyone on this list agrees that my opinion matters above all
else, but I'm sure that pass/fail would be a good baseline ;).  As I
recall Pandokia had some interesting stuff between pass and fail like
"not loaded for resource reasons"...

C. Titus Brown, ctb at msu.edu

More information about the testing-in-python mailing list