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

  1. AnonymousJuly 1, 2012 at 5:11 PM

    Nice information by the author really informative thanks.

    ReplyDelete
  2. AnonymousJuly 14, 2012 at 9:05 PM

    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.

    ReplyDelete
  3. AnonymousAugust 2, 2012 at 6:26 AM

    very nice information....thanks for it !!!

    ReplyDelete
  4. Quality AssuranceNovember 2, 2012 at 10:49 PM

    This is very good. also check:

    What Is Regression Testing with Example

    ReplyDelete
  5. AnonymousFebruary 12, 2013 at 7:44 PM

    Very nice...Thank you for the clear information.

    ReplyDelete
  6. AnonymousApril 10, 2013 at 2:29 PM

    thanks blogger for properly explaining regression testing with example....

    ReplyDelete
  7. sathishJune 17, 2013 at 3:17 PM

    this is very useful and nice ................thaks

    ReplyDelete
  8. NeerajJuly 16, 2013 at 12:37 PM

    Very Good,Helpful Explanation..........Thanks

    ReplyDelete
  9. AnonymousDecember 31, 2013 at 1:39 PM

    nice answers..thank you

    ReplyDelete
  10. Mr. Sunil MJanuary 12, 2014 at 11:17 PM

    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

    ReplyDelete
    Replies
    1. PRAVEENMay 15, 2014 at 12:36 PM

      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

      Delete
    2. AnonymousJune 19, 2014 at 7:39 PM

      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.

      Delete
    3. bapugoudaSeptember 23, 2014 at 3:37 PM

      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.

      Delete
  11. AnonymousFebruary 6, 2014 at 5:25 PM

    Whats the difference between regression testing and sanity testing? Both are done after bug fix is done. Then why two different terminologies?

    ReplyDelete
    Replies
    1. AnonymousSeptember 8, 2014 at 11:55 AM

      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

      Delete
  12. RamanMarch 24, 2014 at 1:15 PM

    Very good... helpful for me

    ReplyDelete
  13. AnonymousApril 3, 2014 at 12:25 PM

    cna you give examples pliz

    ReplyDelete
  14. shardul jadhavApril 17, 2014 at 12:06 PM

    please create same blogs for sql, t-sql also.

    ReplyDelete
  15. AnonymousJune 18, 2014 at 9:01 PM

    Excellent article ..... thanks

    ReplyDelete
  16. UnknownJuly 18, 2014 at 12:28 PM

    nice answer. thank u

    ReplyDelete
  17. AnonymousSeptember 17, 2014 at 1:07 PM

    any suggestion on the test cases for a website?

    ReplyDelete
  18. AnonymousOctober 16, 2014 at 12:56 PM

    good explaination

    ReplyDelete
  19. AnonymousApril 11, 2015 at 1:56 AM

    Thank you for your blog, well explained and very helpful

    ReplyDelete
  20. UnknownJune 16, 2015 at 9:20 PM

    good explanation

    ReplyDelete
  21. MatinAugust 5, 2015 at 11:33 PM

    If for modules f1 ,f2 .. F3 isv added .in regression test do check only f1 and f2?

    ReplyDelete
  22. AnonymousAugust 6, 2015 at 11:07 AM

    Thank you for your blog, well explained and very helpful

    ReplyDelete
  23. UnknownSeptember 10, 2015 at 4:26 PM

    really clear information... thank u ....

    ReplyDelete
  24. UnknownSeptember 10, 2015 at 4:26 PM

    really clear info....thank u

    ReplyDelete
  25. AnonymousNovember 28, 2015 at 3:32 PM

    Veri nice Example & defination .................

    ReplyDelete
  26. AnonymousAugust 24, 2016 at 4:51 PM

    Explained very smoothly and in detail by the author.

    ReplyDelete
  27. AnonymousMay 3, 2017 at 11:11 AM

    Nice.. helpful

    ReplyDelete

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

What Is Functional Testing Explain It with Example?

Functional testing means testing the application against business requirements. Functional testing is executed using the functional specifications given by the client or by the design specifications according to use cases given by the design team. Role of functional testing is to validating the behavior of an application. Functional testing is more important because it always verifies that your system is fixed for release. The functional tests define your working system in a useful manner. In functional testing tester has to validate the application to see that all specified requirements of the client whatever we have said in SRS or BRS have been incorporated or not. Functional testing  is always concentrating on customer requirements and whereas the Non-Functional testing is always concentrating on customer expectations. Functional and Non Functional Test Cases Functional test cases target business goals and non functional test cases target performance, resource...
29 comments
Read more