[TIP] A quick guide to testing (for the khmer project)

[Marcin Tustin]

This encodes the code first, write tests afterward approach to development. It's bad because it's *hard*. It's hard to come up with good test cases post hoc, because there's a lot of analysis to do (which is made easier when you write the code, because you're already thinking of those things), and because code not written to be tested is more difficult to test. TDD solves these problems by merging the development and testing activities into one step.

-----Original Message-----
From: testing-in-python-bounces at lists.idyll.org [mailto:testing-in-python-bounces at lists.idyll.org] On Behalf Of C. Titus Brown
Sent: Wednesday, July 23, 2014 10:12 AM
To: tip at lists.idyll.org
Subject: [TIP] A quick guide to testing (for the khmer project)

http://khmer.readthedocs.org/en/docs-hackathon/dev/a-quick-guide-to-testing.html

comments, thoughts?
_______________________________________________
testing-in-python mailing list
testing-in-python at lists.idyll.org
http://lists.idyll.org/listinfo/testing-in-python