<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE rss [<!ENTITY % HTMLlat1 PUBLIC "-//W3C//ENTITIES Latin 1 for XHTML//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml-lat1.ent">]>
<rss version="2.0" xml:base="http://www.kai-mai.com">
<channel>
 <title>Kai Mai&#039;s Blog - Take Back the Web - Nodes for qa</title>
 <link>http://www.kai-mai.com/tags/qa</link>
 <description>Nodes containing the tag qa</description>
 <language>en</language>
<item>
 <title>Can QAs Find Too Many Bugs?</title>
 <link>http://www.kai-mai.com/node/56</link>
 <description>&lt;p&gt;
I have been taking the responsiblity of monitoring a bug-tracking queue for a product at work.
&lt;/p&gt;
&lt;p&gt;
Sheila, the &lt;a href=&quot;http://en.wikipedia.org/wiki/Quality_Assurance&quot;&gt;QA&lt;/a&gt; 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&#039;t like seeing many bug calls. 
I&#039;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&#039;s a real bug.
&lt;/p&gt;
&lt;p class=&quot;awTags_TagLinks&quot;&gt;Tags: &lt;a href=&quot;tags/72&quot;&gt;development&lt;/a&gt; &lt;a href=&quot;tags/76&quot;&gt;qa&lt;/a&gt; &lt;/p&gt;</description>
 <category domain="http://www.technorati.com/tag">development</category>
 <category domain="http://www.technorati.com/tag">qa</category>
 <pubDate>Thu, 16 Mar 2006 19:09:44 -0800</pubDate>
</item>
</channel>
</rss>
