TL;DR

We gave two examples of flawed software testing measurements using bug counts and code coverage. How can we effectively measure software testing? The post is aligned with the Black Box Software Testing Foundations course (BBST) designed by Rebecca Fiedler, Cem Kaner, and James Bach.

We described how measuring testing effectiveness using code coverage and bug counts is flawed. There are alternatives for measuring software testing effectiveness. We should first break down these alternatives into crucial tasks. For each of those critical tasks, take a software tester work sample (for example, 10 work reports). Evaluate what is right and wrong in those reports and create your team scoring card. With that, you can score and rate performance effort for each critical task or a group of tasks and create a software tester profile.