為什麼我們要做Bug Bash
Why We Conduct Bug Bashes
http://blogs.msdn.com/steverowe/archive/2009/02/13/why-we-conduct-bug-bashes.aspx
什麼是Bug Bash
- A period of time where we tell all of the test developers to put down their compilers and simply play with the product.
- Bug bashes are a time when everyone on the team is asked to spend all of their time conducting exploratory testing.
運作的經驗法則
- Usually a bug bash lasts a few days.
- This particular one was 2 days long.
- We often make a competition out of it and track bug opened numbers across the team with bragging rights or even prizes for those who come out on the top of the list.
- Sometimes managers will influence the direction by assigning people end-user scenarios or features to look at.
- Other times the team is just let go and told to explore wherever they desire.
- Experience has shown me that some direction can be good.
- Assigning people to explore an area they don’t usually work on gets new eyes on the product and with new eyes come new use patterns and new bugs.
作者認為bug bash是有用的, 會抓到一些想不到的bug出現. 因為不同的人, 會有不同的想法, 因此會有不同的testing scenario出現. 或是相同的scenario, 看到原先沒有看到的問題.
但是bug bash的代價是昂貴的, 因為你必須停下手邊的工作, 全心來找product的問題. 因此會導致你手頭上, 會累積很多其他工作.
那為什麼還要做bug bash呢? 他的ROI是什麼呢? 作者認為理由有三
1. A bug bash flushes out a lot of bugs in a short period of time.
- Our most recent bug bash saw the number of bugs opened jump to 400% of the daily average.
- This is important because we frontload the finding of the bugs.
- The earlier we know about bugs, the more likely we are to be able to fix them.
- Knowing about more bugs also helps us make more informed triage decisions.
2. They are likely to find bugs on the seams.
- Test automation can only find certain kinds of bugs.
- Exploratory testing is a much better way to find issues on the seams—where functional units join up
- Sometimes these bugs are the most critical.
- We obviously don’t find all such issues through bug bashes, but we do find a lot.
3. Get a sense of the product.
- Most of the time we spend our days focused on one small part of the operating system or another.
- It’s hard to get a sense for the state of the forest while staring at individual trees.
- After spending several days conducting exploratory tests on the product, we can get a much better sense whether the overall product is doing well or if there are serious issues.
Why We Conduct Bug Bashes
http://blogs.msdn.com/steverowe/archive/2009/02/13/why-we-conduct-bug-bashes.aspx
什麼是Bug Bash
- A period of time where we tell all of the test developers to put down their compilers and simply play with the product.
- Bug bashes are a time when everyone on the team is asked to spend all of their time conducting exploratory testing.
運作的經驗法則
- Usually a bug bash lasts a few days.
- This particular one was 2 days long.
- We often make a competition out of it and track bug opened numbers across the team with bragging rights or even prizes for those who come out on the top of the list.
- Sometimes managers will influence the direction by assigning people end-user scenarios or features to look at.
- Other times the team is just let go and told to explore wherever they desire.
- Experience has shown me that some direction can be good.
- Assigning people to explore an area they don’t usually work on gets new eyes on the product and with new eyes come new use patterns and new bugs.
作者認為bug bash是有用的, 會抓到一些想不到的bug出現. 因為不同的人, 會有不同的想法, 因此會有不同的testing scenario出現. 或是相同的scenario, 看到原先沒有看到的問題.
但是bug bash的代價是昂貴的, 因為你必須停下手邊的工作, 全心來找product的問題. 因此會導致你手頭上, 會累積很多其他工作.
那為什麼還要做bug bash呢? 他的ROI是什麼呢? 作者認為理由有三
1. A bug bash flushes out a lot of bugs in a short period of time.
- Our most recent bug bash saw the number of bugs opened jump to 400% of the daily average.
- This is important because we frontload the finding of the bugs.
- The earlier we know about bugs, the more likely we are to be able to fix them.
- Knowing about more bugs also helps us make more informed triage decisions.
2. They are likely to find bugs on the seams.
- Test automation can only find certain kinds of bugs.
- Exploratory testing is a much better way to find issues on the seams—where functional units join up
- Sometimes these bugs are the most critical.
- We obviously don’t find all such issues through bug bashes, but we do find a lot.
3. Get a sense of the product.
- Most of the time we spend our days focused on one small part of the operating system or another.
- It’s hard to get a sense for the state of the forest while staring at individual trees.
- After spending several days conducting exploratory tests on the product, we can get a much better sense whether the overall product is doing well or if there are serious issues.
全站熱搜
留言列表
