Missing important bug

If i miss a important bug and i realise it very late then what will i do?

Questions by soniya2484

Showing Answers 1 - 13 of 13 Answers

when your approach towards the testing task is really systematic there is no question of missing important bug araises. still i would prefer to answer your question.

If you really come to know that you have missed an important bug while reporting them, Then you should react according to your cadre, i.e. if you are a team member of  a testing team then you should report the same to your Team Leader and he should take the necessary action for reporting that bug.

OR if your work environment permits you to report it to the concerned person then you should Log that bug and should check forthe same in the relevant build

Missing is common nature. its also realistic in the Software Testing. Lets come to the Missind Important bug.

If the bug missed in Final Release, communicate the bug to the right people ( TL, Developer, Manager) and ask them to fix it! and deliver

If the bug missed in any Consecutive Built, let it fix them in the next release and note down the bug status as "Defered"

If the missed bug doesnot cause any impact to the application, note it down and let them to fix in next release. if its delivered means, let it be fix in maintanance stage.

I too agree with the above answer, there is always a chance to miss the issues, it may be major or minor. The reason may be the impact of new changes, etc.

So the solution may be we've to escalate the issue first to our lead then we can decided what to do, i can escalate in a smarter way like " Found below issue while doing regression testing as it may be due to new changes ..." as my project is always having change requests.


Usually, when we perform system testing in conjunction with Business requirements, there is no scope of missing an important bug, but its human tendency to overlook sometimes, which may result in missing an important bug. Well coming to the point, if you have missed it,

1. Check it in the old version, whether the same issue was occurring in the earlier version also.

If it is not happening in the earlier version, then if you have found it in the regression environment (which is close to production environment), then check it in the QA environment, so that you can be sure whether it is a build issue or failure in functionality.

3. Analyse, what will be the result, if the product goes with this issue, i mean is it show stopper or can it wait for next release.

4. With all these things approach your direct manager an discuss the issue diplomatically and then follow manager's instructions


  Was this answer useful?  Yes


Mising important bugs may leads to high business loss but if done by mistake then the ultimate solution is to find the root cause from where the bug arised for e.g in leave application project in leave report if tne no. of leaves approved are 10 where as leaves allotted are 5 it means thre bug arised from leaves allotted page,thus it states that instead of locking the bug which was missed out ,you have to lock the bug against root cause of missed out bug that will automatically recover the missed out bugs

Hope i answer ur Question.


  Was this answer useful?  Yes

Missing Important Bug:

1) First of all tester's role is to perform testing with user's perspective.
2) Analyses the requirement and test all possible ways to eliminate impact to the application or system. That is why we write test cases. And test cases should have all possible scenarios that needs to be tested.
3) Still if something very important is missed out. We just need to understand in what phase we are in. For eg: SIT, UAT, Dress
rehearsal. And inform your immediate supervisor/project team and respective team, so that testing of such defect could be performed immediately.
4) or if we are out of control where the project has been moved to production, then we have just got to address this as project risk immediately to the higher level.

  Was this answer useful?  Yes

A missed or 'latent' defect should be immediately reported to the Test Lead who will communicate this oversight to potentially concerned stakeholders.  Then file a defect report attaching the appropriate Priority and Severity. 

Afterward, examine the nature of the defect and try to figure out why it was missed.  Were the requirements unclear or did you simply misinterpret them?  Did you miss a requirement altogether?  Did you author your test case(s) incorrectly?  Was time for test execution constricted and you were simply in a hurry to get through your test pass?  No matter the reason, try as best you can to learn from your experience and ensure the reasons for missing this defect will not happen again.  Of course, this is often easier said than done.

Every bug you founf is important. If you found it at the end of release cycle then also inform it/log it. Let the BA decide what to do with it. If it is critical/major then it should be fixed. If it is normal/minor/corner case then can be deffered to next relase.

Datta Deshmukh

  Was this answer useful?  Yes


  • Aug 11th, 2010

First check whether the bug existed in your scope or not, if it is in your scope, check whether you have covered the senario in testcase document, if not, prepare a Root Cause Analysis Report and send to the team lead.

  Was this answer useful?  Yes

Give your answer:

If you think the above answer is not correct, Please select a reason and add your answer below.


Related Answered Questions


Related Open Questions