GeekInterview.com
  I am new, Sign me up!
 
GeekInterview.com  >  Interview Questions  >  Testing
Go To First  |  Previous Question  |  Next Question 
 Testing  |  Question 411 of 413    Print  
Root Cause of Bug
As a test enginner, How will you find the root cause for the bug that occured in the production or live, which has been already tested and certified.
How will you face the situation?



  
Total Answers and Comments: 4 Last Update: November 06, 2009     Asked by: digitdom 
  
 Sponsored Links

 
 Best Rated Answer
Submitted by: rahulskin
 
The following are the points you can check.
1) Study the bug.  Find the functionality where it is.
2) If the sofwtare is already tested.  Check for executed test cases and see the test result.
3) Cross check the test cases with the requirement specification.
4) Check the release on which testing and certification done.
5) Check the hardware, software compatibility.
6) Ensure that the regression testing done properly.  If any defects raised in the same functionality where the bug found.

Collect all the above mention points detail and study for the root cause for the bug that occured in the software.


Above answer was rated as good by the following members:
prathibha12003, sreevatsava, ashwini_ku
September 08, 2009 05:23:22   #1  
rahulskin Member Since: November 2007   Contribution: 39    

RE: Root Cause of Bug
The following are the points you can check.
1) Study the bug. Find the functionality where it is.
2) If the sofwtare is already tested. Check for executed test cases and see the test result.
3) Cross check the test cases with the requirement specification.
4) Check the release on which testing and certification done.
5) Check the hardware software compatibility.
6) Ensure that the regression testing done properly. If any defects raised in the same functionality where the bug found.

Collect all the above mention points detail and study for the root cause for the bug that occured in the software.

 
Is this answer useful? Yes | NoAnswer is useful 1   Answer is not useful 1Overall Rating: -N/A-    
September 08, 2009 06:16:25   #2  
mathan_vel Member Since: December 2007   Contribution: 422    

RE: Root Cause of Bug
1. Analyzed & check the loophole of the bug.
2.Execute once again the Test case with the Environment of bug arise and note down the status(test result).
3. Make a note for the reason for the bug.
4.Check the bug not impact on other areas.
5.Make that bug to Hot fix and Close as early.

 
Is this answer useful? Yes | No
September 09, 2009 01:39:21   #3  
ashishks Member Since: December 2008   Contribution: 73    

RE: Root Cause of Bug
It is a very general case in software testing that any bug is found on the production and it was not present on the testing environment. If anything happens like this then we should proceed in the following way:

1. Properly understand functional flow which is producing the bug on production.
2. Find out the differnecs between "testing environment and production environment" and its impact on the functional flow which is producing bug on production.
3. Verify functonality with the "same test data" on the production which was producing correct results on testing environment.
4. conduct a meeting and try to find out other causes which may effect the functional flow which is producing bug on production.

 
Is this answer useful? Yes | NoAnswer is useful 3   Answer is not useful 0Overall Rating: +3    
November 06, 2009 20:26:41   #4  
kurtz182 Member Since: November 2009   Contribution: 141    

RE: Root Cause of Bug

Include in ashishks' answer this fifth step:

When the reason for the problem in the production environment is known and the gap between production and test environment which causes this error is identified establish measures to bring the test environment closer to the live (production) environment in whatever manner is most feasible.


 
Is this answer useful? Yes | No


 
Go To Top


 Sponsored Links

 
About Us -  Privacy Policy -  Terms and Conditions -  Contact -  Ask Question -  Propose Category -  Site Updates 

Copyright © 2005 - 2009 GeekInterview.com. All Rights Reserved

Page copy protected against web site content infringement by Copyscape