> Can someone give me, or point me to, a really thorough and
> accurate definition of the term
>
> Regression Testing
>
> As it applies to software maintenance or QA?

"Regression testing is fundamental work done by glass box and black box
testers. The term 'regression testing' is used in two different ways. Common
to both is the idea of reusing old tests:
 - Imagine finding an error, fixing it, then repeating the test that exposed
the problem in the first place. This is a regression test. Added variations
on the initial test, to make sure that the fix works, are also considered
part of the regression test series. Under this usage, regression testing is
done to make sure that a fix does what it is supposed to do.
   Some programming groups create a set of regression tests that includes
every fixed bug ever reported by any customer. Every time the program is
changed in any way, all old fixes are retested. This reflects the
vulnerability of code fixed (which, unless they're well documented, often
don't look 'right' when you read the code) to later changes, especially
by new programmers.

 - Imagine making the same fix, and testing it, but then executing a
standard series of tests to make sure that the change didn't disturb
anything else. This too is called regression testing, but it tests the
overall integrity of the program, not the success of software fixes.
   Stub and driver programs developed during incremental testing can be the
basis of an automated regression test battery. Or you can create an
automated regression suite of black box tests using a capture/replay program
(discussed in Chapter 11, 'Automated acceptance and regression Tests')."

> Perhaps, someone can recommend some excellent book on testing
> in software development, preferable with a Computer Science
> orientation.

The source of the quote above, considered by many to be the 'bible' of
software testing: "Testing Computer Software", Second Edition. Cem Kaner,
Jack Falk, Hung Quoc Nguyen, 1999,
John Wiley & Sons, Inc., ISBN 0-471-35846-0.

Regression testing is not, as implied by some of your responses, a
"buzzword-compliant, content-free" term used by clueless managers. It is a
mandatory, fundamental component
of any serious software test program.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *