This lesson talks about bad metrics for measurement and where they can lead. Note this is also the last lesson of the Foundation course.
Learning Objective
Understand why there is pressure on testers to keep bug counts low, the use of surrogate measures in assessing tester effectiveness, and the importance of developing trustworthy quantitative measures in test management.
Core Topics and Takeaways
-
Consequences of bad metrics on the project
-
The more you rely on old tests the fewer bugs you will find
Learning Highlights
Bug count and code coverage are complementary metrics in software testing. Code coverage measures the percentage of code exercised by the tests, while bug count indicates the number of defects found. By analyzing both metrics together, teams can gain a better understanding of the quality and effectiveness of their testing efforts. For example, a high code coverage with a low bug count may indicate thorough testing, while a low code coverage with a high bug count may signal inadequate testing.
You have completed the Black Box Testing section of the course. Now you can move on to more Pricefx specific content. Good luck!