Golgappa.net | Golgappa.org | BagIndia.net | BodyIndia.Com | CabIndia.net | CarsBikes.net | CarsBikes.org | CashIndia.net | ConsumerIndia.net | CookingIndia.net | DataIndia.net | DealIndia.net | EmailIndia.net | FirstTablet.com | FirstTourist.com | ForsaleIndia.net | IndiaBody.Com | IndiaCab.net | IndiaCash.net | IndiaModel.net | KidForum.net | OfficeIndia.net | PaysIndia.com | RestaurantIndia.net | RestaurantsIndia.net | SaleForum.net | SellForum.net | SoldIndia.com | StarIndia.net | TomatoCab.com | TomatoCabs.com | TownIndia.com
Interested to Buy Any Domain ? << Click Here >> for more details...

difference between regression testing and re testing?

Answer Posted / lakshmanaraj bg

Regression Test:

Regression testing attempts to verify that modifications have not caused unintended adverse side effects in the unchanged software (regression faults) and that the modified system still meets its requirements.

Re-test:

Whenever a fault is detected and fixed then the software should be re-tested to ensure that the original fault has been successfully removed.

Re-testing and Regression Testing:

It is imperative that when a fault is fixed it is re-tested to ensure the fault has indeed been correctly fixed.

There are many tools used in a test environment today that allow a priority to be assigned to a fault when it is initially logged.

We can use this priority again when it comes to verifying a fix for a fault,particularly when it comes to deciding how much time to take over verifying the fix.

For example if you are verifying that a has been fixed in a help file, it would probably have been raised as a low
priority fault.

So you can quickly come to the conclusion that it would probably only take a few minutes to actually verify the fault has been fixed.

If, however a high priority fault was initially raised that wiped all of the customers stored data, then you would want to make sure that sufficient time was allocated to make absolutely sure that the fault was fixed.

It is important that consideration of the possible consequences of the fault not being fixed properly is considered during verification.

Another important factor when it comes to testing is when there is suspicion that the modified software could affect other areas of software functionality.

For example, if there was an original fault of a field on a user input form not accepting data.

Then not only should you focus on re-testing that field, you should also consider checking that other functionality on the form has not been adversely affected.

This is called Regression Testing.

For example; there may be a sub-total box that may use the data in the field in question for its calculation.

That is just one example; the main point is not to focus specifically on the fixed item, but to also consider the effects on related areas.

If you had a complete Test Specification for a software
product, you may decide to completely re-run all of the test cases, but often sufficient time is not available to do this.

So what you can do is cherry-pick relevant test cases that cover all of the main features of the software with a view to prove existing functionality has not been adversely affected.

This would effectively form a Regression Test.

Regression test cases are often combined to form a Regression Test suite.

This can then be ran against any software that has undergone modification with an aim of providing confidence in the
overall state of the software.

Common practice is to automate Regression Tests.

To assist you on what to additionally look for when re-testing, it is always a good idea to communicate
with the Developer who created the fix.

They are in a good position to tell you how the fix has been
implemented, and it is much easier to test something when you have an understanding of what changes have been made.

Is This Answer Correct ?    0 Yes 0 No



Post New Answer       View All Answers


Please Help Members By Posting Answers For Below Questions

in transfer funds module, how you come to know that amount has been transferred successfully or not....explain in detail

1549


what are the tests u did in entire project? when it did in the project? (means at the release build to end of project) plz explain clearly

2092


what is diffrence between dynamic black box testing and dynamic white box testing

1953


Explain the manual testing process?

1177


Do we have any certifications for ETL Testing ?

2179


what is quality Factor

2434


Is Anyone attended the manual testing interview with capgemini in recent past. please let me know the type of questions they can ask. Thanks

3298


What does entry and exit criteria mean in a project?

1099


Is quality control similar to quality assurance?

1031


Explain Single View Testing ?

1370


types of reviews?Advantages of reviews? Diff between process and procedure? diff b/w verification and validation? diff b/w cmm,cmmi? exp tqm,gqm,iso,ieee? Roles and responsibilities of tester? Ricks,types of ricks? what r Quality factors?

2187


How to do Performance Testing manually for a Flash Application?

2363


What is XML Testing? Do we have any tools to test the XML? Please let me know.

2070


Our software designers use UML for modeling applications. Based on their use cases, we would like to plan a test strategy. Do you agree with this approach or would this mean more effort for the testers.

2101


hi all I have an overall experience of 12 years working in an EDP setup(worked in a manufacturing setup in a German MNC). On my request, I was relieved from my duties in Sep 06 for maternity reasons. However I would like to pursue a career in a software organization as a manual tester. I obtained my proficiency certificate in Software Testing from STAG SOFTWARE LIMITED 2 months ago i.e in May and would now like to continue working in this field. However I am unable to find a job until now. If anybody knows of a opening at bangalore, kindly let me know.

1966