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

How do you know the code has met specifications?

1322


What is Dynamic Binding and Dynamic Loss?

2009


Hi, Please can one tell me how to test the usability testing, which method has to be used, how to write the report? Thanks Deepa

2011


Explain severity with example and expalin each example?

4321


What is a defect age?

1076


Can you please explain about the erp project

1806


Assume a login page, and you have written 10 cases(say for example). How will you justify that these 10 testcase suffient for the login and how do you say this is 100% satisfies the need.

2222


What is a top-down and bottom-up approach in testing?

1112


Describe Testing Decomposition?

1269


How do you scope out the size of the testing effort?

2312


What is PBX Testing & What is Test coverage?

11048


Usually customers won’t give all the requirements. How will you manage & collect all the necessary information?

1178


what is Test management fundamental?

2230


MS Paint

2061


Build with fixes has been deployed on QA environment if asked by your manager to reproduce how can you reproduce the issues? (by using the previous build) Can you access the previous build? If so ,what are the tools or how can you access?

2039