Testing - Handle Bugs in Live / Production

GeekInterview.com > Interview Questions > Testing

Go To First | Previous Question | Next Question

Testing | Question 409 of 413

Handle Bugs in Live / Production

Suppose a bug has been produced in live for the piece of functionality you have carried out testing. How will you give explanation to PM/Manager?

Total Answers and Comments: 4

Last Update: November 10, 2009 Asked by: subhasri17

Sponsored Links

Best Rated Answer

—

No best answer available. Please pick the good answer available or submit your answer.

August 03, 2009 06:36:56

er.ighosh

Member Since: August 2009 Contribution: 1

RE: Handle Bugs in Live / Production

Case 1: The functionality tested is out of scope.
Solution: In the above case we can justify the issue as out of scope.

Case 2: The functionality tested is in scope and test case is not present for the same.
Solution: In the above case we can justify the issue in scope and update the testcases with timestamp and notify the manager for the same.

Case 3: The functionality tested is in scope and test case is present for the same.
Solution: In the above case we can justify the issue as a testing error(missed bug) and try to figure out what was the reason for the miss and keep track for the same so that there may not be any misses in the future**.

**Generally associates do not feel strong enough to bring up their mistakes in front of others. But if you are prompt towards your efforts in bringing up your mistakes with proper documentation(as historic data); that would certainly help in bringing up the productivity in future.

Is this answer useful? Yes | No

0 1

Overall Rating: -1

August 14, 2009 07:52:47

anuBM

Member Since: August 2009 Contribution: 1

RE: Handle Bugs in Live / Production

If the mistake is from your end accept it.

Also tell what were the loophole which could be corrected in next release.

Is this answer useful? Yes | No

August 21, 2009 08:47:57

rahulskin

Member Since: November 2007 Contribution: 39

RE: Handle Bugs in Live / Production

The tester should ensure the following.
- The functionality is already tested before releasing.
- If defects raised on the same. Regression tesing is done properly.
- Any issues with the functionality. (From Testing Development side)
- The RS documents are clear for the same and is functioning as per the same.

Is this answer useful? Yes | No

November 10, 2009 00:19:04

kurtz182

Member Since: November 2009 Contribution: 111

RE: Handle Bugs in Live / Production

The question is: Suppose a bug has been produced in live for the piece of functionality you have carried out testing. How will you give explanation to PM/Manager?

This issue can not be considered 'Out of Scope' and there must be a test case for it because it is 'a piece of functionality you have carried out testing'.

In this scenario the tester will need to research to determine whether the issue was caused by 1) a faulty test case 2) a difference between Production and Test environments or 3) by the tester's mistake or lack of follow-through. Whatever the case may be it is the tester's responsibility to isolate the problem and take steps to correct it. Once this has been accomplished then the particulars of the issue should be fully disclosed to the appropriate individuals (Project Manager Test Manager etc.).

1. Faulty Test Case:
a) Does the test case accurately map to the proper business requirement? If not then perhaps the business requirement was missed and this becomes the source of the problem.
b) Is the business requirement incorrect? If so then the requirement needs to be rewritten and new test case(s) produced from this new requirement.
c) Was the test case authored improperly. That is did the tester misunderstand the business requirement and create an improper test case? If so then the test case(s) need to be reauthored based on this newly correct understanding.

2. Difference between Production and Test Environment:
Does the defect occur only in the Production environment but not in the Test environment? If so then this must be made perfectly clear to management. The tester may need to work with other functional groups to figure out how to bring the Test environment in alignment with Production in order to prevent this issue from reoccuring.

3. Tester oversight or lack of follow through. As humans we sometimes make mistakes. There are situations when the amount of time that a test team is allowed to test becomes constricted and testers feel they must hurry to finish their test runs. In these situations testers inadvertently miss test steps or even entire test cases. And it is Murphy's Law that the overlooked test case will be the one that could have uncovered a significant defect! If this happens the tester must own up to the error and inform management. I have made my share of mistakes--we all do. It is best to admit the blunder and take personal measures to ensure it doesn't happen again. The most important aspect of ANY relationship work or otherwise is trust. And if you try to cover up your mistakes you will quickly lose the trust of your managment and cohorts. Honest is truly the best policy in any circumstance!

Is this answer useful? Yes | No

Go To Top

User Name		Remember Me?
Password

Question Bank