Re: April 13, 2004 - Today Microsoft released the following Security Bulletins

From: Ivan Bútora (xxx_at_xxx.xx)
Date: 04/14/04 

Date: Wed, 14 Apr 2004 03:30:59 -0400

Thanks for the explanation.

"Hugh Candlin" <no@spam.com> wrote in message news:eMnoo0eIEHA.1608@TK2MSFTNGP11.phx.gbl...

Ivan Bútora <xxx@xxx.xx> wrote in message news:e4rrIWeIEHA.3144@TK2MSFTNGP10.phx.gbl...

the security bulletins, linked to by PA Bear in his post, discuss the vulnerabilities that are fixed by the respective patches. I
believe the patches are tested if they are listed as available for the given OS. (Although what exactly regression testing means
somewhat mystifies me.)

====

Let's say I write a program to perform any of 4 functions.

It will add, subtract, multiply or divide any two numbers
entered, depending upon the option number selected [1 through 4].

I test this program, and each of the functions works as specified.

I now change the program to also calculate the average of any
two numbers entered, and make this executable as Option #5.

To test this, I enter two numbers and select Option #5.
The program dutifully displays the average of the two numbers.
I enter more combinations of numbers, and each time,
the new function works as specified.

I move my program into production, and the complaints pour in.
"Hey!!! Option #1 doesn't work".
"Nice going, Slick. Option #2 is all messed up".
"I'm getting garbage answers from Option #3".
"Yo, moron, what did you do to Option #4?".

Alas, when adding new functionality to a program,
a developer may introduce one or more bugs
which can cause one or more of the original functions
to malfunction, even while the new functionality works perfectly.

The way that you try to avoid this is to run all of the prior tests again.
In other words, you "regress" to a previous stage of development,
and run the full complement of tests, just as if you were testing
each function for the very first time, to make sure that they still work.

Relevant Pages

  • Re: April 13, 2004 - Today Microsoft released the following Security Bulletins
    ... > the security bulletins, linked to by PA Bear in his post, discuss the ... vulnerabilities that are fixed by the respective patches. ... (Although what exactly regression testing means ... > each function for the very first time, to make sure that they still work. ...
    (microsoft.public.windows.inetexplorer.ie6_outlookexpress)
  • Re: April 13, 2004 - Today Microsoft released the following Security Bulletins
    ... > the security bulletins, linked to by PA Bear in his post, discuss the ... vulnerabilities that are fixed by the respective patches. ... (Although what exactly regression testing means ... > each function for the very first time, to make sure that they still work. ...
    (microsoft.public.security)
  • Re: April 13, 2004 - Today Microsoft released the following Security Bulletins
    ... > the security bulletins, linked to by PA Bear in his post, discuss the ... vulnerabilities that are fixed by the respective patches. ... (Although what exactly regression testing means ... > each function for the very first time, to make sure that they still work. ...
    (microsoft.public.windows.inetexplorer.ie6.browser)
  • Re: April 13, 2004 - Today Microsoft released the following Security Bulletins
    ... the security bulletins, linked to by PA Bear in his post, discuss the vulnerabilities that are fixed by the respective patches. ... (Although what exactly regression testing means ... a developer may introduce one or more bugs ... each function for the very first time, to make sure that they still work. ...
    (microsoft.public.windows.inetexplorer.ie6.browser)
  • Re: April 13, 2004 - Today Microsoft released the following Security Bulletins
    ... the security bulletins, linked to by PA Bear in his post, discuss the vulnerabilities that are fixed by the respective patches. ... (Although what exactly regression testing means ... a developer may introduce one or more bugs ... each function for the very first time, to make sure that they still work. ...
    (microsoft.public.windows.inetexplorer.ie6.browser)