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.
Nice information by the author really informative thanks.
ReplyDeleteNicely 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.
ReplyDeleteTo be very frank i never seen regression testing information before like that because author has explained it nicely especially regression testing example.
very nice information....thanks for it !!!
ReplyDeleteThis is very good. also check:
ReplyDeleteWhat Is Regression Testing with Example
Very nice...Thank you for the clear information.
ReplyDeletethanks blogger for properly explaining regression testing with example....
ReplyDeletethis is very useful and nice ................thaks
ReplyDeleteVery Good,Helpful Explanation..........Thanks
ReplyDeletenice answers..thank you
ReplyDeleteNice 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.
ReplyDeletethanks
sunil
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...
DeletePraveen
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.
DeleteThat 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.
DeleteWhats the difference between regression testing and sanity testing? Both are done after bug fix is done. Then why two different terminologies?
ReplyDeleteSanity Testing: Test Whether the build/application is stable for further/actual test execution to start or not.
DeleteRegression Testing: Re execution of the Selective/ high priority test cases on
modified and associated builds is called Regression testing
Very good... helpful for me
ReplyDeletecna you give examples pliz
ReplyDeleteplease create same blogs for sql, t-sql also.
ReplyDeleteExcellent article ..... thanks
ReplyDeletenice answer. thank u
ReplyDeleteany suggestion on the test cases for a website?
ReplyDeletegood explaination
ReplyDeleteThank you for your blog, well explained and very helpful
ReplyDeletegood explanation
ReplyDeleteIf for modules f1 ,f2 .. F3 isv added .in regression test do check only f1 and f2?
ReplyDeleteThank you for your blog, well explained and very helpful
ReplyDeletereally clear information... thank u ....
ReplyDeletereally clear info....thank u
ReplyDeleteVeri nice Example & defination .................
ReplyDeleteExplained very smoothly and in detail by the author.
ReplyDeleteNice.. helpful
ReplyDelete