<"write a test that handles your business problem">: Do you create a
program for that or it is just a list of test steps that QA must perform
manually?
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Buck
Sent: Tuesday, January 29, 2008 9: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
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.