HP3000-L Archives

October 2001, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"rosenblatt, joseph" <[log in to unmask]>
Reply To:
rosenblatt, joseph
Date:
Thu, 18 Oct 2001 11:52:27 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (23 lines)
Regression testing is, basically, testing to see if the "new" works with the
existing environment. That is you "regress" your modifications. When you
test an existing program with a new version of the database you regress the
database not "progress" the program. Regression testing should be applied to
hardware as well as software.
As far as I can tell we have always done regression testing. By this I mean
that unless you change *everything* every time you change *anything*  then
you did regression testing, presuming you tested at all. Then why the hoopla
over regression testing. Why is an old concept given a new name?
Project Managers added this word to their lexicon in order to give them
another "bullet item" on their project plans. So now it is very chic to do
regression testing. This type of regression testing is done to "Enhance our
fulfillment opportunities in a competitive marketplace while maintaining a
cutting edge on our technological frontiers. This will blip blop blopty
blooh ... "(You get the picture.)
I hope this helps ;-^)
The opinions expressed herein are my own and not necessarily those of my
employer.
Yosef Rosenblatt

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

ATOM RSS1 RSS2