Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Bug reports by developer is a horrible metric. As a QA Lead I have argued against this time and time again. Bugs <strong>will</strong> happen. How they are dealt with when they do is more meaningful.</p> <p>A better metric is what the developer's bug reopen rate is. In other words, when QA logs a bug, which is then fixed, is the bug fixed correctly, or is there something that was missed, causing QA to reopen the bug?</p> <p>The more often this happens, it is a clue that the developer may not be paying real attention to the problem. This is assuming, of course, that the bug was intelligently logged in the first place, preferably with steps to reproduce, the actual outcome, the expected outcome, and why. Screen shots help, too. </p> <p>Obviously, this is just one metric on which to report. Other possibilities are</p> <ul> <li>Does the developer meet promised deadlines?</li> <li>Responsiveness to client concerns.</li> <li>Accuracy of any required documentation.</li> </ul> <p>and probably others.</p> <p><strong>Edit:</strong> I have done both development and QA and was lucky enough during my development time not to have bug counts used against me in reviews. I argue against it at my current company in my current role because it is an unreliable metric IMO. We used reopen rate as a compromise to make upper management (read "pointy-haired" dev director) happy that they have something to report on. I am not a manager and don't actually generate any reports myself (in case that's the cause of some downvotes).</p>
    singulars
    1. This table or related slice is empty.
    1. POCode Quality
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USssakl
    1. USssakl
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO+1. I'm leery of quality metrics in general, but I have to admit, this is a good one -- *if* it can be tracked accurately. (That's a big "if", but it doesn't invalidate the concept.)
      singulars
      1. PO
      1. USDan Breslau
    2. CO@Dan - We track this metric using reports from HP Quality Center. We keep a lot of history on status change and developer fields. Those without such a product may have a harder time generating accurate metrics.
      singulars
      1. PO
      1. USssakl
    3. COThere is still the problem of differentiating between coders who have to develop something very complex with those who have a simple task.
      singulars
      1. PO
      1. USAnders K.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload