Quality Testing

Quality is delighting customers

What should be the best answer when your QA manager ask you “Why didn’t you catch that bug!?!”

 Whenever a bug makes its way into production, the QA department is almost guaranteed to hear something along the lines of, “Why didn’t you catch that bug!?!”

 I think everyone (QA/Tester) has  face this question in his/her testing career, so what would be the best answer in this type of situation.    

Views: 711

Reply to This

Replies to This Discussion

Give the exact reason, what ever it is. escaping answer is No clear requirements or test case doesn't exist. Genuine answer is I couldn't catch is simply it slipped.

becaz of  Some changes from dev side

Due to late build ,we miss it and lack of concentration we miss tat bug. It never happens here after.

Test Cases, Test  Scenarios are designed for that scenario.

 "Any Software Application can not be 100% Bug free" .

I would vote for Nagaraju's answer. :)

However, sometimes in bad mood, I would argue that "I even did not know its existence, otherwise, you wouldn't ask me this question. However, I would learn from it now."

Any test coverage is not 100%. There are always requirements that you base your test cases on, and then there are other ad-hoc test cases that some testers run (outside of the requirements window). 

In real practical world, there are always issues in production. Instead of a QA manager asking why the defect wasnt found in lower testing regions, he/she should focus on best practices in mitigating such occurrences in production by:

a. Devising proper roll-back procedures for the code
b. Assessing the overall customer impact as a result of this issue in production
c. Forming a SWAT team to complete the development and QA testing of the issue in question (along with a minor regression test suite of the integrated components).

 

   " Bugs cant be eliminated but they can be reduced..and the reduced one may u have catched before uat.. "

Here are a couple answers... Keep in mind it depends on the bug and severity. Also if it is in ISO 9000 or SLDC makes a difference.

1. It was Fault Masked. (A issue that opened a new issue and was not regressed properly)

2. It was part of a pesticide complex. (We kept running the same test cases and it was outside of those bounds)

3. Limited Regression and Time Contraints along with Selective/Risked Based Testing

4. It was a low risk impact and it was not stated as severe for Users.

RSS

TTWT Magazine


Advertisement

Advertisement

Advertisement

Advertisement

© 2019   Created by Quality Testing.   Powered by

Badges  |  Report an Issue  |  Terms of Service