Code correctness, and testing strategies

Ben Finney bignose+hates-spam at benfinney.id.au
Sat May 24 21:46:00 EDT 2008


"D'Arcy J.M. Cain" <darcy at druid.net> writes:

> Yes! One of the biggest advantages to unit testing is that you never
> ever deliver the same bug to the client twice.

More specifically, this is a benefit of putting all unit tests into an
automated test suite, and running that test suite all the time during
development so it's immediately clear when any of them fails due to a
code change.

It's not enough to *have* the unit tests, nor is it enough to only run
them at certain times. They need to run after every change, so the
feedback is immediate and local to the change that was made.

(good sigmonster, have a cookie)

-- 
 \            "Program testing can be a very effective way to show the |
  `\        presence of bugs, but is hopelessly inadequate for showing |
_o__)                              their absence."  -- Edsger Dijkstra |
Ben Finney



More information about the Python-list mailing list