The document discusses bugs measurement and metrics in software testing. It defines metrics as a distance function that assigns numbers to anything to enable measurement. The document outlines why metrics are important for testers to provide information and support easier decision making. It discusses potential issues with metrics like time waste and wrong conclusions if not implemented properly. The document provides examples of common bug metrics and recommends automating metric collection and regular publishing to address issues.
12. Why it's important
• tester's job is info support for the project
• more and diverse info -> better conclusions ->
easier decisions
13. Why it's important
• tester's job is info support for the project
• more and diverse info -> better conclusions ->
easier decisions
• metrics are facts, operate with facts, not blah-
blah-blah
14. Why it's important
• tester's job is info support for the project
• more and diverse info -> better conclusions ->
easier decisions
• metrics are facts, operate with facts, not blah-
blah-blah
• example: “big” manager
15. Why it's important
• tester's job is info support for the project
• more and diverse info -> better conclusions ->
easier decisions
• metrics are facts, operate with facts, not blah-
blah-blah
• example: “big” manager
• NOTE: don't judge too quickly!
35. “Easy way”
1. choose correct metrics for you
2. ensure everybody gets what they mean
3. automate them
4. be prepared for change requests
5. use regularly
6. publish online
36. Example: my metrics
• No classic test cases & project is not big
– Bug metrics only
• Custom bugtracker
– No access to DB
• 2 metrics - weekly
– Open bugs: Trend in time
– Open bugs: By modules