Remaining nimble in the face of evolution

[Jason Orendorff]

jim.vickroy wrote:
> Now a reality check occurs and the requirement evolves such that the
> archival behavior is to be optional.
> 
> What is the "best" strategy to handle these types of evolution.

One excellent strategy you can employ *now* to ensure that unforeseen
future changes go smoothly is to write a complete test suite,
use it, and keep it up-to-date.

When it comes time to make an incompatible change, you then know
*exactly* what existing behavior you're breaking.  So you can try out
different strategies when you get there, rather than trying to guess
now what problems you'll face in the future.

  The seminal article "Test Infected" explains why.
  http://members.pingnet.ch/gamma/junit.htm

  The documentation of the standard unittest module tells how.
  http://www.python.org/doc/current/lib/module-unittest.html

## Jason Orendorff    http://www.jorendorff.com/