In this video bug counting is discussed and where it can lead. It also shows some ideas how important are also other activities on the project and what can happen if people know about which numbers are measured.
In this video you will learn about:
Bug counting, surrogate measurement often becoming a focal point in testing. The quest for numerical validation can lead testers to prioritize easily quantifiable aspects, potentially neglecting crucial facets of software evaluation. Predictable problems arise when testers fixate solely on measurable activities, redirecting attention from holistic testing approaches. Not all bugs should be tallied alike; seriousness varies. Relying solely on numbers can skew perception, emphasizing quantity over severity. Testing isn't just about accumulating bug statistics; it's about ensuring robust software. Bug counts can inadvertently influence resource allocation, overshadowing nuanced assessments.
| Widget Connector | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Discussed terminology:
Surrogate measurement
Why do we count bugs and where it can lead
Predictable problems - like testers are focused just on activities connected with measurement
Measurement can drive people to focus on some activities and ignore others
Why bugs should not be always counted the same way - how serious bugs can be?
We are not testing just because of nice numbers of bugs
What bug counts can sometimes affect
...