4 ms·
One strategy for estimating bugs is to intentionally seed your code with bugs and then see how many of them the QA team find. ie, if the QA team identifies 5/10
by ksherlock 3y ago
One strategy for estimating bugs is to intentionally seed your code with bugs and then see how many of them the QA team find. ie, if the QA team identifies 5/10 intentional bugs and 20/?? true bugs you can estimate there are 40 true bugs (20 still unidentified).
Likewise, we just need to seed other star systems with intelligent life and see how many our astronomers can find.
- AlbertCory 3y agoThere's that "just" word again /s
- gls2ro 3y agoI think this could be a maybe a way to assess the efficiency of the QA team, but I am skeptic of using it as a metric about estimating the number of bugs. This is because QA is there to help with reducing the probability that an important bug will happen to a real user. But the total number of bugs a system have is a sum of bugs found by developers + bugs found by QA + bugs found by average users + bugs found by power users + bugs found at scale/big numbers. The more we move to the right of this sum the hard is to replicate conditions to find bugs and so we move from finding to probabilities and risk management.
- cafeinux 3y agoFor the moment, astronomers found 0 life forms out the 42 we seeded. Unfortunately, 0/42 is equal to 0/n where n ∈ ℕ, so we don't gained much knowledge on the matter so far.
- deleted 3y ago[deleted]