Quality Dashboard for Software Testing

alan barona's picture
alan barona asked on April 17, 2018 - 11:42pm | Replies (2).

I am trying to design a Quality Dashboard for software testing that can help us monitor all tickets filed for bugs, as well as other information that can help our Developmenmt Team.  I wanted to make sure we monitor the trurnaroud time in resolving bugs, as well as which area of the application are we seeing most of the bugs.  Also, I am not sure if possible, I would like to link it to the Sprint of the Dev Team since we are using an Agile approach in the development.

Hoping to get your thoughts on this.  Thank you in advance.

Alan Barona

2 Answers

Jerry Penner's picture

You can count the number of bugs open, bugs open/closed per sprint, number of open active critical bugs, average length of time open sliced by severity, priority and sprint, add a multiplier for how old each bug is, or any one of a hundred other ways.


The fact is, your customers don't care about these numbers.

Your customers want to know if the software will do what it's supposed to do. If it's a game, is the play fun? If it's a business tool, doe the program allow the client to finish their work faster with it than without it? Are your customers happy?


Customer happiness is the prime measure of quality software. There are a number of ways to measure that. One way is to ask the customers themselves. Your marketing team might even be running customer surveys right now. The feedback from these surveys should be driving development and testing.


Another useful metric (although it's not really a count of things, but a list), is a list of bugs reported by customers. Doesn't matter if they were found internally first or not. The bugs customers report are the bugs that are the most important to them. The Dev, Test, and Marketing teams need to study these lists and align their efforts with what customers report. This is the most important metric of all, because unhappy customers will flee to your competitors if their concerns are not addressed.

Kanika Vatsyayan's picture

Hey Alan,  

The idea is amazing! With all these metrics on common bugs found in the software, I would suggest you to define the basics for different types of software like LMS, ERP, eCommerce, etc. And mention the common forms of bugs that are found in each. Meanwhile you can work on some data learning features to ensure that any unique information to the system can be captured and presented to different users who need to run similar kinds of software tests.  


And of course, don’t forget to share a link or something for the same once you are done.  

I would like to see the system you create.  

StickyMinds is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.