Can QAs Find Too Many Bugs?

Submitted by kai on Thu, 2006-03-16 20:09. ::

I have been taking the responsiblity of monitoring a bug-tracking queue for a product at work.

Sheila, the QA in my group, has been opening many bug tracking calls and flooded the queue. She asked me if she has opened too many bug calls (in other words, found too many bugs (BTW, most of them are not my bugs)). Apparently, some people don't like seeing many bug calls. I'd rather see QAs find as many bugs as they can and report them, rather than not trying to find them or not reporting them. Even if they are not sure whether it is a bug, a tracking call should still be opened to track it and determine whether it's a real bug.

I'd prioritize them. If we just don't have time to fix some low priority bugs for now, we should still track them. Some bugs can also be characterized as future enhancement requests.

QAs cannot find TOO many bugs if people don't inject that many bugs.

Tags: development qa

kai's blog

Post new comment



The content of this field is kept private and will not be shown publicly.


*

  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd>
  • Lines and paragraphs break automatically.
  • WikiText is converted to HTML (supported WikiText formatting will show in the long tip format).
More information about formatting options
Verify comment authorship
Captcha Image: you will need to recognize the text in it.
*
Please type in the letters/numbers that are shown in the image above.