Defect Bash - Literature Review <s> INTRODUCTION <s> Abstract Many companies regularly use beta tests as part of their product development program. Beta testing can validate the product concept, eliminate performance problems prior to market introduction, and serve as an effective sales promotion device. The risks are significant, however, in that a poorly designed test can destroy account relationship, generate inaccurate data on product performance, and stimulate negative publicity. Robert Dolan and John Matthews present guidelines for effective management of beta test programs. They develop these guidelines based on a literature review, an analysis of twenty-one beta test programs as described in secondary sources, and four in-depth field investigations with cooperating firms. <s> BIB001 </s> Defect Bash - Literature Review <s> INTRODUCTION <s> The lowly test plan is perhaps the least appreciated of all supporting (read: noncode) software development artifacts. All projects need one, but few engineers appreciate their existence. So it's important to spend no more time than is absolutely necessary in the creation, care, and feeding of the test plan. Ten minutes, to be precise. <s> BIB002
Testing is one of most important software quality practices and it aims in finding defects before the software is released. Defect bash (or bug bash) is a testing event where a group of people tries to find as many defects as possible from the software. It is widely applied in software companies (Anonymous 2, 2010; Anonymous 3, 2011;    Sagynov, 2011a, b; BIB002 . For example Microsoft used it quite often (Anonymous 2, 2010;   Sahay, 2012) .  sees defect bash as an additional testing complementing written automated and manual test cases.  listed defect bash as a technique for blackbox testing. It is used in crowd testing (Anonymous 6, 2012) and open source testing  . Although, defect bash has been around for decades BIB001 , we could not find a single research article that would have had primary focus on the defect bash, although it is often mentioned as a side note. This is in stark contrast for example with code review practice that has been the primary focus of several academic articles. In order to shed light to this popular practice, this article analyses the existing information on defect bash with the following fundamental issues:  The definition of defect bash;  The benefits and limitations of using defect bash;  The process of doing successful defect bash. This paper is a literature review of defect bash. In Section 2 we define the literature review protocol. Section 3 defines defect bash based on the literature review. Section 4 lists the benefits and limitations of defect bash. The process of defect bash is derived from the references in the section 5. Finally conclusion is given in Section 6.