Bug Tracking - missing important bug

GeekInterview.com > Interview Questions > Testing > Bug Tracking

Go To First | Previous Question | Next Question

Bug Tracking | Question 89 of 94

missing important bug

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

Total Answers and Comments: 9

Last Update: May 18, 2009 Asked by: soniya2484

Sponsored Links

Best Rated Answer

—

Submitted by: surendra_kumar

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

Above answer was rated as good by the following members:
birlangiKumar

June 10, 2008 22:42:50

surendra_kumar

Member Since: November 2006 Contribution: 12

RE: missing important bug

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

Is this answer useful? Yes | No

1 0

Overall Rating: +1

June 18, 2008 00:35:20

mathan_vel

Member Since: December 2007 Contribution: 413

RE: missing important bug

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.

Is this answer useful? Yes | No

0 1

Overall Rating: -1

July 23, 2008 13:52:37

good_job

Member Since: July 2008 Contribution: 4

RE: missing important bug

Notify the test lead. And also track this bug as High Priority Bug.

Is this answer useful? Yes | No

August 28, 2008 01:17:31

srinivasulub1981

Member Since: December 2005 Contribution: 377

RE: missing important bug

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.

Srinivas

Is this answer useful? Yes | No

August 28, 2008 19:28:54

Sushma Mosali

Member Since: June 2007 Contribution: 269

RE: missing important bug

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.

2.
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

Thanks
Sushma

Is this answer useful? Yes | No

November 10, 2008 03:06:20

manoj.raut123456

Member Since: November 2008 Contribution: 2

RE: missing important bug

Soniya

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.

Regards
Manoj

Is this answer useful? Yes | No

November 25, 2008 02:52:55

preethi.gollamandala

Member Since: September 2008 Contribution: 88

RE: missing important bug

Its a tester responsibilty to keep track the application concentrately for all the possibile defects.So dont think about that..
Any way the solution for that just keep as a Major defect.

Is this answer useful? Yes | No

March 11, 2009 02:58:23

sangeethaarjun

Member Since: March 2009 Contribution: 5

RE: missing important bug

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.

Is this answer useful? Yes | No

May 18, 2009 07:55:40

mathan_vel

Member Since: December 2007 Contribution: 413

RE: missing important bug

This kind of Bug is called Latend Bug. This bug should be reported as early and mentioned the Severity.

Is this answer useful? Yes | No

Go To Top

User Name		Remember Me?
Password

Question Bank