Quality is delighting customers
Regression testing :
when the tester come's to conformation that the big is fixed, then he starts Regression testing on that modified build. in this testing, the tester test's or checks whether the modified build is showing any impact on other application or not.. means whether new application or functionality is effecting other application or not.the tester checks after fixation of bug,we got any side effects in application or not... why because , during the bug fixing some parts of coding may be changed or functionality mat be manipulated.. in this case the old test cases will up-dated or completely re-written according to new feauter of application where bug fixed area.....
Normally regression will be done , If any changes in the old implementatin,. if any changes in the new requirement If any functionality bug is fixing It would be better , if you can do once the new build is getting released for testing server. and also .. depends on the bug severity there are three types of regression,. unit regression, regional regression, full regression.
if any mistake pls correct me .. thank u every body
Regression is done in two situations
1) If software has been changed ( because of fixes or Adding extra functionality or deleting existing functionality )
2) If the Environment changes still we will do regression..
Retesting:- ( also called Confirmation testing : ):- when testing is done to confirm that the bug which we reported earlier has been fixed in new build is called retesting .... but Regression testing means :- testing to ensure that the fixes has not introduced new bugs to be appear... !
Example:-- You execute 5 test case in which 2 test cases failed ...
Now in new build ( After fixes ) You will execute 2 test cases which failed earlier in Retesting to ensure that the defect has really been fixed....
but You will execute 3 test cases which passed earlier ( in 1st test run ) to ensure that the test cases which were passed has not been affected because of Bug fixes...
on the whole :--- Retesting after bug fixes to ensure that bug really got fixed ..
but Regression will be done to find out the side effect of the changes....
Now My 2nd point :---- Suppose the S/W has not been changed but the Environment has been changed (like a S/W was developed to work with XP but The Client wants that S/W to work with Windows 7 too ) in that case too Regression will be done...!
QT Team .
Regression testing is done when any code modification is done to the existing software application. Or, any new module is added to the existing application. When any of the above is done, then testers will test the whole application to see if the software is working as it is desired even after the new changes.
According to me, we'll do regression testing when,
1.After defect is fixed
2.Any new functionality is added
4.Sudden fall in defect density
Correct me If I'm wrong!!!
any design/code changes without requirement changes.
Can you give one example of this????
if you do any change in Software then you go for regression testing.
As per quality assurance services regression testing is performed to make sure that any code changes in the software does not impact the existing functionality of the software/product. This testing verifies that the software/product works exactly fine, as it was previously, with the newly added feature or any change in the existing functionality or any bug fix/fixes are done.
From above we came to conclude that the regression testing needs to be done after:
1. a new feature/functionality introduced in the existing software/product
2. any change in the existing functionality
3. any bug fix/fixes are pushed in the code
First of all, we need to understand what is Regression Testing. It is an activity performed to ensure the different functionalities of the system are still working as expected and the new functionalities added did not break any of the existing ones.
Secondly, you generally write automated tests or do manual testing to perform the above mentioned testing. Regression testing can be performed in various phases of the SDLC, it all depends on the context. I have done it after end of the sprints, before a release, also have had daily regression tests running on a daily basis.
Hopefully this gives an idea on when to do regression testing.