RE: Agile methods (was: Another Midrange Forum Falls Over and Can't GetUp)

Buck, thanks for the expanded explanation.

This seems eerily similar to test "scripts" that I have seen
used in the past. These so-called scripts were nothing but
step-by-step documents outlining a test method and employed
by the user community to ensure that their new application
worked correctly.

Terry

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Buck
Sent: Tuesday, January 29, 2008 10:24 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Agile methods (was: Another Midrange Forum Falls
Over and Can't GetUp)

Terry wrote:

Interesting link on Agile Testing - thanks! Sounds like a great idea
but, like many other companies, we could not support this method:

"Since working increments of the software is released very often
in agile software development there is also a need to test often."

Many people misunderstand what this means. In effect, it
means that you
can have the confidence to make daily releases to production because
your test suite makes it very easy to prove you haven't
broken anything
by making the change. There's much more to it, but the general
principle is that you write a test that handles your business
problem,
then you work on the code until the test is satisfied. The
test suite
that emerges from this effort is run after every change,
verifying all
the business rules still work after the latest change.
--buck
--

Confidentiality Notice:

The preceding e-mail message (including any attachments) contains information that may be confidential, protected by applicable legal privileges, or constitute non-public information. It is intended to be conveyed only to the designated recipient(s). If you are not an intended recipient of this message, please notify the sender by replying to this message and then delete it from your system. Use, dissemination, distribution or reproduction of this message by unintended recipients is
not authorized and may be unlawful.