One of the fundamental beliefs in Testlio has been to value the time testers spend on testing, instead of measuring them based on the number of bugs submitted.
We have gathered some thoughts why time spent on testing is important and works for Testlio clients and testers.

Motivation for testers. Testers often say that they are undervalued. But all the professional testers and developers know how important it is to have quality testing before launching new applications. Testers who are paid per hour instead of bugs submitted feel that they are valued and their work is important. They are more motivated to focus on the current application and making sure the whole app is being tested.

Testing the whole system. Developers and clients are interested that the whole system will be tested. Getting information on the common use-cases is as important as going deep into functional, performance and security testing.

Serious bugs are more important for clients and developers. Of course spelling mistakes are important as well, but a security issue makes the whole app vulnerable. Testers who know they have time want to drill deeper to find hard-core issues. The experienced testers are much more satisfied to find killer bugs in addition to some pixel alignment that is ugly to look at. Proper bug reporting always needs some time to reproduce the issues to confirm the details.

Team work, communication and sharing information among testers is important to work fluently. A team of testers is interested in finding bugs and adding additional information as a joint team. Measuring their individual time rather than bugs, they don’t need to sprint to be the first one to report.

What do you think, why time spent on testing is more important than number of reported bugs?