In QA organizations today, a tester must have technical know-how, good communication skills, and attention to detail. We know that a tester’s main responsibility is to test the software that developers develop to ensure that the product meets the quality standards expected of today’s applications. But apart from that, it’s difficult to measure what exactly makes a good tester. QA managers and their team members are constantly under pressure to test faster and more efficiently, and deliver software with fewer defects. The role and importance of QA in today’s R&D teams is evolving from simply finding defects to protecting the corporate image. As a result, your testers have to be more productive and more efficient, and change their mindset to think about quality over quantity. It’s not just about finding bugs; it’s about continuing to measure and improve, and finding the right bugs to make the end-user experience better. In this lecture I will share with you some of the key performance indicators (KPIs) that we use to measure our own testing efforts: Percentage of high/critical, escaped defects, Time to test, Defect resolution time, Percentage of rejected defects and what we’ve learned from each of them, and how our team improved its efficiency and productivity as a result.

1. Testing your
Software Testers
@bendet_ori

2. ABOUT
ME
6y in HPE Software
in various
managerialQA
rolesToday– Inbound PM
for a new cloud offering

3. Largest Pharm.
Customer in Europe
Critical Defect in
Diaper

4. Academia vs Industry (=the Real World)
Academia Industry

5. The Real World…
We still have testers!
And we love them!

8. So why
Test your Testers?

10. Continues
Risk-based Testing

11. The Metrics
that don’t
matter
Total # of defects
• How many defects does your application currently
have that are open
• The quantity of defects is no longer as relevant as
once was
Direct coverage
• Test coverage of a feature (manual/automated)
• ”Done is done”
Unit testing coverage
• % of code covered by unit tests
• The majority of defects are detected during
integration testing and end-to-end testing

12. The Metrics
that Really
matter
% of escaped defects
• Escaped defects are those that are missed by the
tester and found by the end user
• Ensures that you’re focusing on the most
defects and areas that are important to the end
Time to Test
• Getting from ‘in-testing’ to ‘done’
• Measuring the efficiency of the tester and
how slowly or quickly they are completing tasks.
Defect resolution time
• Time it takes a defect to be fixed and verified
• The majority of defects are detected during
integration testing and end-to-end testing

13. Quality Beats
Quantity

15. Q&A
15