What is the diff between retest bug and regression bug?
- 6 Answers
- 10539 Views
- HCL, Kekran Mekran, SK Infotech, I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / gurpreet
When a bug is fixed by the developer it is again retested by the tester to verify if it is fixed, this is known as retest bug whereas a bug which occurs in some module as a result of modifications in some other module of the system is regression bug.
| Is This Answer Correct ? | 24 Yes | 0 No |
Regression bug – Changes in existing code that change the
behavior of the application so it does not meet a
specification that was previously met.
Bug-Its simple fault or any defect.
| Is This Answer Correct ? | 7 Yes | 0 No |
Answer / nilanjan saha
When in the testing process Tester report a bug, after that
it get assigned to a specified developer. After fixation of
that bug it again comes for retesting to that the bug
really get fixed or not. It is also called as Confirmation
testing.
Due to fixation of that specific bug it might affect some
adverse effect to other modules then those newly generated
bugs are termed as regression Bugs. Regression testing is
generally Automated.
| Is This Answer Correct ? | 4 Yes | 0 No |
Answer / mbalakiran
Retesting:when a defect is fixed by the developer, after that to verify that defect or test the defect again and again with different type of input data is known as retesting.
Regression Testing:If any changes done on the existing build this test is conducted on modified build because of this changes will effect on changed functionality and unchanged functionality.
| Is This Answer Correct ? | 4 Yes | 0 No |
Answer / chhabrachhagan
Retesting:- Retesting is a confirmation testing which ensures that bug has been fixed or not.we perform same test steps to find out bug is fixed or not.
Regression:- Regression test ensures that unchanged area of the application will not be affected by bug fixation.our core functionality should be same.
| Is This Answer Correct ? | 0 Yes | 0 No |
Retesting :- "Rexecution of fail testing".
Retesting is running the previously failed test cases again on the new software to verify whether the defects posted earlier are fixed or not.
In simple word, Retesting is testing a specific bug after it was fixed.
Regression Testing :- "Rexecution of pass testing".
In three cases we needs to do regression testing-
(i) After Bug Fix
(ii) After enhancement or new feature added
(iii) Environment change
| Is This Answer Correct ? | 0 Yes | 0 No |
What Is iterative testing? Explain with example.pls thanking u in advance
on what basis low,medium,high,critical will be assigned to a bug.give m examples
Which Server Stats are essentially monitored during a Perf test of a Web Application?
what comes first test strategy or test plan
what is the template of ur co,when requirements are not clear,suppose Business Analyst is not there to whom to meet.what is the role of tester in req or design phase
what is cookies. how do we test the cookies
I have one doubt in regression testing, Example if we have five modules such as 1,2,3,4,5. If we made change in 3 module only and also 3 module will interact with only 1 and 5 module. For this case we will conduct testing in all module (or) only 1 and 5 module?? Answer soon firends
What is difference between QTP 9.2 and QTP 8.0 ?
Have u ever done testing related to a database,give examples to support u r answer.
Write notes on apparel testing equipments.
0 Answers Mahatma Gandhi University,
what are the advantages of waterfall model over V-model??
A server configuration is controlled from a single web page with multiple options: ● 20 drop-down menus, with 3-4 options each. ● 5 check-boxes. ● 1 multi-select menu, with 5 options. ● 1 template selection, with 6 options: A, B, C, D, E, F. ○ When options A, B, C, D are selected, all options (#1-#3) above are available. ○ When options E, F are selected, only 10 out of 20 drop-down menus have an effect. ● Besides item #4, developers input is that all options are independent, I.e., not impacting each other. What is the required number of test configurations required in order to test the server configuration and release in good quality: a) Assuming first release. b) Assuming regression tests for release with new features not impacted by the above options. Test configuration is a complete set of options that were selected to be tested in one complete server configuration scenario. I.e, a test configuration is set of 17 or 27 specific options tested together.
Automation Testing 
