Skip to main content

Regression Testing with Example and Strategies

Regression Testing is done to ensure that fixed bug does not affect the remaining functionality of the modules and also the functionality of the same module.

In short you can say regression testing is always done to verify that modified code does not break the existing functionality of the application and works within the requirements of the system.

Regression Testing Example 

For Example there are three Modules in the Project named Admin Module, Personal Information, and Employment Module and suppose bug occurs in the Admin Module like on Admin Module existing User is not able to login with valid login credentials so this is the bug. 

Now Testing team sends the above - mentioned Bug to the Development team to fix it and when development team fixes the Bug and hand over to Testing team than testing team checks that fixed bug does not affect the remaining functionality of the other modules (Admin, PI, Employment) and also the functionality of the same module (Admin) so this is known as the process of regression testing done by Software Testers.

Regression Testing and its Strategies?

Regression testing is achieved after the bug fixed, means testing the operation whether the fixed defect is affecting remaining functionality of the application or not. Usually in regression testing bug fixed module is tested. During regression testing tester always check the entire system whether the fixed bug make any adverse affect in the existing system or not.

There are mostly two strategies to regression testing, 1) to run all tests and 2) always run a subset of tests based on a test case prioritisation technique.

When will we do Regression Testing?

Regression testing is the re-testing of features to make safe that features working earlier are still working fine as desired.

It is executed when any new build comes to QA, which has bug fixes in it or during releasing cycles (Alpha, Beta or GA) to always originate the endurance of product.

Conclusion:

At last in simple terms we conclude that regression testing will be conducted after any bug fixed or any functionality changed.
Labels:

Comments

Anonymous said…
Nice information by the author really informative thanks.
July 1, 2012 at 5:11 PM
Anonymous said…
Nicely explained by the author keep it up with more on software testing its really nice, this blog is good to see because all the information is unique and also good for interview point of view.

To be very frank i never seen regression testing information before like that because author has explained it nicely especially regression testing example.
July 14, 2012 at 9:05 PM
Anonymous said…
very nice information....thanks for it !!!
August 2, 2012 at 6:26 AM
Anonymous said…
Very nice...Thank you for the clear information.
February 12, 2013 at 7:44 PM
Anonymous said…
thanks blogger for properly explaining regression testing with example....
April 10, 2013 at 2:29 PM
sathish said…
this is very useful and nice ................thaks
June 17, 2013 at 3:17 PM
Neeraj said…
Very Good,Helpful Explanation..........Thanks
July 16, 2013 at 12:37 PM
Anonymous said…
nice answers..thank you
December 31, 2013 at 1:39 PM
Mr. Sunil M said…
Nice answer but one confusion will come ,How will we know in regression testing that the problem occurring is exactly due to fixing the particulate bug.
thanks
sunil
January 12, 2014 at 11:17 PM
Anonymous said…
Whats the difference between regression testing and sanity testing? Both are done after bug fix is done. Then why two different terminologies?
February 6, 2014 at 5:25 PM
Raman said…
Very good... helpful for me
March 24, 2014 at 1:15 PM
Anonymous said…
cna you give examples pliz
April 3, 2014 at 12:25 PM
shardul jadhav said…
please create same blogs for sql, t-sql also.
April 17, 2014 at 12:06 PM
PRAVEEN said…
Consider that every module works fine except one which needs a fix, and when the bug is fixed and sent for testing and when the testing team finds a new bug then obviously we can say that a new problem has araised 'coz of a new fix...
Praveen
May 15, 2014 at 12:36 PM
Anonymous said…
Excellent article ..... thanks
June 18, 2014 at 9:01 PM
Anonymous said…
My comment would be, if the one bug fix is done ans a retest of the system is done with exisiting and/or sub tests, then the bug "should" be the only reason that an error/bug is found on a system test.
June 19, 2014 at 7:39 PM
Unknown said…
nice answer. thank u
July 18, 2014 at 12:28 PM
Anonymous said…
Sanity Testing: Test Whether the build/application is stable for further/actual test execution to start or not.

Regression Testing: Re execution of the Selective/ high priority test cases on
modified and associated builds is called Regression testing
September 8, 2014 at 11:55 AM
Anonymous said…
any suggestion on the test cases for a website?
September 17, 2014 at 1:07 PM
bapugouda said…
That is because before the bug got detected in that particular module that module was working fine right, So once the bug get fixed and if u find any new issues in that module it becomes obvious that the problem was because of the fix.
September 23, 2014 at 3:37 PM
Anonymous said…
good explaination
October 16, 2014 at 12:56 PM
Anonymous said…
Thank you for your blog, well explained and very helpful
April 11, 2015 at 1:56 AM
Unknown said…
good explanation
June 16, 2015 at 9:20 PM
Matin said…
If for modules f1 ,f2 .. F3 isv added .in regression test do check only f1 and f2?
August 5, 2015 at 11:33 PM
Anonymous said…
Thank you for your blog, well explained and very helpful
August 6, 2015 at 11:07 AM
Unknown said…
really clear information... thank u ....
September 10, 2015 at 4:26 PM
Unknown said…
really clear info....thank u
September 10, 2015 at 4:26 PM
Anonymous said…
Veri nice Example & defination .................
November 28, 2015 at 3:32 PM
Anonymous said…
Explained very smoothly and in detail by the author.
August 24, 2016 at 4:51 PM
Anonymous said…
Nice.. helpful
May 3, 2017 at 11:11 AM

Post a Comment

Popular posts from this blog

Difference Between Verification And Validation With Example?

Verification and Validation example is also given just below to this table.                Verification               Validation 1. Verification is a static practice of verifying documents, design, code and program. 1. Validation is a dynamic mechanism of validating and testing the actual product. 2. It does not involve executing the code. 2. It always involves executing the code. 3. It is human based checking of documents and files. 3. It is computer based execution of program. 4.  Verification uses methods like inspections, reviews, walkthroughs, and Desk-checking etc. 4.  Validation uses methods like black box (functional)  testing, gray box testing, and white box (structural) testing etc. 5.  Verification  is to check whether the softwar...
66 comments
Read more

Endurance Testing with Example, Meaning and Definition

Endurance Testing is a type of Performance Testing which is usually used to determine how much a system can sustain the continuous expected load. During the period of Endurance Testing memory utilization is always monitored to detect any potential leaks. In short we can say that judging/studying the memory leak of a server under the period of stability is known as Endurance Testing . Due to its judgment and study on memory leak that is the reason why Endurance Testing is also known by the name Soak Testing . As you know in Endurance Testing memory utilization is monitored so it very important for us to know about memory leak means what it is all about. When memory allocated to objects are not being freed by the system/application than definitely the memory leak occurs. Endurance Testing Example – Real Time Below is given the real time example of Endurance Testing and hope after seen these real time example your knowledge on Endurance Testing should definitely b...
Post a Comment
Read more