Quality Central Reports
Quality Central is seeing a fair amount of activity in the past week. To give some insight into ‘whats going on’ - daily the development managers meet and review the last day of reports into Quality Central, both public and private. We go through as many reports as we can, and try to either promote or push back depending on if a report has everything we need to act on it.
In addition the QA team has been spending time reviwing QC reports for their areas. Anyone who subscribes to the daily digest of changes should be seeing this activity directly.
So far, it’s been great - when we bounce a report back as Needs More Information, the QC email notifcation lets the submitter know of a change to their report, and typically I’ve been getting a reply within 24 hours. We’re also seeing a lot of attention to detail in reports, especially from the field test. Clear descriptions including expected and actual behavior, code samples, screenshots and detailed steps. This makes everyone’s job a lot easier - from QA to reproducing it and writing an automated test, to R&D fixing it and ensuring a unit test is developed if appropriate.
The backlog of older QC reports is still huge. So far we’re making slow progress to a net gain, but at this rate it will take several years to get through all reports. So it’s time to look for more interested community members who are willing to be SysOps. Basically need people to look at the older reports in an area they care about, close out or push back the ones that cannot be reproduced, and mark as Needs Attention ones that they can reproduce and need to get fixes ASAP.
Any volunteers interested in helping out? Reply here, or contact me directly cpattinson@codegear.com (and CC chris.pattinson@gmail.com )
Hey it’s an (relatively?) easy way to fame. We publish publicly the sysop stats so you can see who has been busy…
July 18th, 2007 at 11:26 am
Hi Chris,
does this mean that you are going to fix older bugs, for *older* Delphi version, at least Turbo Delphi or BDS 2006, too?
cu,
Michael
July 18th, 2007 at 12:55 pm
Any specific bugs you had in mind?
Generally we will not fix bugs in areas that are deprecated/no longer supported/no longer have knowledge of the code base.
Everything else is prioritized, and we aim for fixing the most severe first. If several serious reports are grouped together in an area, we’d want to clean it up.
This is where QC comes in handy. We can see which areas of the product have a high number of reported/open issues and should do a general clean up:
http://qc.codegear.com/stats/project.aspx?Project=10&Area=15