Why we say that we are regressing the bug
According to some definitions :
When a bug is fixed, the tester regress the bug to make sure if it is fixed and if it doesn't make an effect on other modules.
Now, if the above definition is right, then it means that against each and every bug, we have to test the whole application. In other words, we are testing the application as well.
So what is it that we say that we are regressing the bug and not testing the application.
Re: Why we say that we are regressing the bug
The selective retesting of a software system that has been modified to ensure that any bugs have been fixed and that no other previously working functions have failed as a result of the reparations and that newly added features have not created problems with previous versions of the software. Also referred to as verification testing, regression testing is initiated after a programmer has attempted to fix a recognized problem or has added source code to a program that may have inadvertently introduced errors. It is a quality control measure to ensure that the newly modified code still complies with its specified requirements and that unmodified code has not been affected by the maintenance activity.
Re: Why we say that we are regressing the bug
[QUOTE=mabobine;15696]According to some definitions :
When a bug is fixed, the tester regress the bug to make sure if it is fixed and if it doesn't make an effect on other modules.
Now, if the above definition is right, then it means that against each and every bug, we have to test the whole application. In other words, we are testing the application as well.
So what is it that we say that we are regressing the bug and not testing the application.[/QUOTE]
Regressing tell about re execution of a test case which was fail in initial execution.
Whereas application testing covers all.Regression is also application testing, but this term differentiates the test cases.:)