SPONSORS:






User Tag List

Likes Likes:  0
Dislikes Dislikes:  0
Page 2 of 2 FirstFirst 12
Results 11 to 18 of 18
  1. #11
    Member
    Join Date
    Nov 2012
    Posts
    130
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0
    Regression testing is the process of testing the application after bug fixed and check whether that fixed bug impact or affect any other modules in the same application.

  2. #12
    Member
    Join Date
    Feb 2016
    Posts
    131
    Post Thanks / Like
    Blog Entries
    1
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0
    Regression testing is the procedure of testing changes to PC projects to ensure that the more established programming still works with the new changes. Relapse testing is an ordinary part of the system advancement process and, in bigger organizations, is finished by code testing authorities. Test division coders create code test situations and activities that will test new units of code after they have been composed.

  3. #13
    New Member Bugraptors's Avatar
    Join Date
    Sep 2015
    Location
    United States
    Posts
    2
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0
    Regression Testing:- In this we ensure that a recent program change has not adversely affected existing features & check that the previous functions still work after the new changes are done. Some Regression testing techniques we use are: Retest all, Regression test selection, Prioritization of Test cases, etc.

  4. #14
    New Member
    Join Date
    Jul 2016
    Posts
    6
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0
    Also note that, Regression testing is conducted after a bug fix to verify that bug fix does not impact any other functionality. Also there is a no proper place in test cycle to conduct regression testing as it can be done after each bug fix. For a water fall projects regression is conducted at the end of test cycle/bug fixes. For agile /iterative mostly it is done after each bug fix.

    Mayuri

  5. #15
    New Member snehasingh90's Avatar
    Join Date
    Aug 2016
    Posts
    6
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    What is Regression Testing ?

    Hiiii,

    Regression testing is a type of application testing that confirms that application previously developed and examined still works properly after it was modified or interfaced with other application. Changes may consist of application improvements, areas, settings changes, etc. During regression testing, new application insects or regressions may be discovered. Sometimes a application package modify impact research is conducted to find out which places could be affected by the suggested changes. These places may consist of efficient and non-functional places of the system.

    The purpose of regression testing is to ensure that changes such as those described above have not presented new mistakes. One of the significant reasons for regression testing is to figure out whether a alternation in one part of the application impacts other parts of the software

  6. #16
    SQA Knight
    Join Date
    May 2006
    Location
    Playa Del Rey, California, United States
    Posts
    2,622
    Post Thanks / Like
    Mentioned
    17 Post(s)
    Tagged
    1 Thread(s)
    Total Downloaded
    0
    David Lai
    SDET / Consultant
    LinkedIn profile

  7. #17
    New Member
    Join Date
    Jul 2016
    Posts
    6
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0
    Regression Testing:
    When any changes are done to the software it is possible that other areas within the application can be affected by this change .The purpose of this testing is to identify any new bugs which is introduced accidentally by the changes in the application.

  8. #18
    Apprentice vishaldutt.testing's Avatar
    Join Date
    Jun 2016
    Posts
    10
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0
    Quote Originally Posted by ixora View Post
    First of all, I've looked for the forum for Regression testing but found none, so I have no idea where to post this. I'm very sorry for the inconvenience.


    Secondly, the questions:

    My test cycle begins with Functional test and followed with System and Integration test (SIT). Then UAT.

    Based on my test cycle above, my questions are as follows:

    1. Let say I do functional testing and discovered a bug. I then send the application to the developer to be debugged. After debugging, I run regression testing on the application. If there is no failed test case during regression testing, what should I do next? Should run all test cases for Functional testing again or go straight to SIT?

    2. My second question is almost the same as my first question, but instead; if I discovered the bug in SIT, should I perform the SIT once again after Regression testing or I go straight to UAT?

    For your info, I do manual testing. In regression testing, I only re-run the failed test cases and test cases related to them (has dependency).

    Hi ixora,

    I am a tester in a software testing company which is an ace in providing the best qa services. "Regression Testing” is one of the basic and important form of tests performed on any software/application. I can very well relate with this software testing services term and following is my take on your intelligent questions:

    Ques 1: Let say I do functional testing and discovered a bug. I then send the application to the developer to be debugged. After debugging, I run regression testing on the application. If there is no failed test case during regression testing, what should I do next? Should run all test cases for Functional testing again or go straight to SIT?
    Answer: As mentioned by you that in regression testing, you only re-run the failed test cases and test cases related to them (has dependency), then there is no need to perform the functional testing again because you have already re-tested the buggy area and validated that particular feature. You should move on to System and Integration test (SIT).

    Ques 2: My second question is almost the same as my first question, but instead; if I discovered the bug in SIT, should I perform the SIT once again after Regression testing or I go straight to UAT?
    Answer: Yes, here you should perform SIT once again after performing the regression testing because a bug in one feature/sub system could have impacted another one. So, all the features/sub-systems should be re-tested. After SIT move on to UAT(User acceptance testing).

    Thanks,
    Vishal Dutt

 

 
Page 2 of 2 FirstFirst 12

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Search Engine Optimisation provided by DragonByte SEO v2.0.36 (Pro) - vBulletin Mods & Addons Copyright © 2017 DragonByte Technologies Ltd.
Resources saved on this page: MySQL 8.33%
vBulletin Optimisation provided by vB Optimise v2.6.4 (Pro) - vBulletin Mods & Addons Copyright © 2017 DragonByte Technologies Ltd.
User Alert System provided by Advanced User Tagging v3.2.8 (Pro) - vBulletin Mods & Addons Copyright © 2017 DragonByte Technologies Ltd.
vBNominate (Lite) - vBulletin Mods & Addons Copyright © 2017 DragonByte Technologies Ltd.
Feedback Buttons provided by Advanced Post Thanks / Like (Pro) - vBulletin Mods & Addons Copyright © 2017 DragonByte Technologies Ltd.
Username Changing provided by Username Change (Free) - vBulletin Mods & Addons Copyright © 2017 DragonByte Technologies Ltd.
BetaSoft Inc.
Digital Point modules: Sphinx-based search
All times are GMT -8. The time now is 12:30 PM.

Copyright BetaSoft Inc.