Home • Forums • Mozilla QA Community • Project-Discussion • Quality Metrics :: Phase II

Quality Metrics :: Phase II

Need help from programmer QA engineers to create Metrics dashboard 2.0

Project Owner: mnandigamaMozQA Badge


Project Details

There have been efforts in place to generate a group of useful frequently asked metrics  on the Mozilla Code and Bugs workflow. This effort is culminating into a dashboard which tries to answer questions like the following.
For Developers the points of interest are

  • How many bugs have been RESOLVED by a developer in the last 6 months
  • How many bugs , a developer has looked at in the last 30 days and made a comment
  • How many pending reviews are there on the name of a developer as a reviewer grouped by product

For Testers the points of interest are

  • How many bugs have been filed by an engineers in the last 6 months
  • How many bugs have been looked at by an engineer and have been commented by the engineer.

For the project work flow managers

  • How many approved blocker bugs are there on a given day
  • How many nominated blocker bugs are there on a given day
  • What is the nominated vs approved blocker bugs trend over time
  • How many blocker bugs have pending reviews and who are the assigned reviewers

For special projects and short term projects

  • What are the incoming and outgoing bugs trends
  • Who are the contributors to filing or fixing bugs in the project

 
etc., etc.,
So, a dashboard that provides quick answers to these questions has been developed and hosted at  http://people.mozilla.com/~mnandigama/dashboard.html
This dashboard is designed in a simple way and has a set of predetermined queries that run in a cron job once every day and the pages are updated once a day.
How ever, the sweet spot for the project to be is to have an interactive and ondemand dashboard which does not strictly require a full blown BI OLAP infrastructure.
To this extent we are planning to build the dashboard 2.0 which uses the newly minted RESTful  API
 
Frameworks to use:

  • PERL Catalyst OR
  • PHP template engine like smarty

Under the hood:

  • Bugzilla RESTFUL API infrastructure
  • MXR/Hg infrastucture that has the check-in logs information
  • Back end data base from one of MySQL,Sqlite,PostgreSQL

Graphing engine:

How you can help...

I am looking for volunteers who would like to work with us in this effort to build an open source infrastructure.

If you are familiar with PHP template engines or PERL Catalyst MVC and have bandwidth to contribute, you are the right fit for us.

 

Please work with the community in acheiving this great feet.

 

The project design specifications would be posted on this site very soon.