ABSTRACT
The quote very effectively sums up the mind-set of why you need crowd testers testing your product and reporting issues. No doubt that you may have a very capable test team (be it internal, outsourced, or a combination of both). However, the additional test coverage that the crowd brings in due to its test expertise, domain know-how, or end user representation is of great value add, as we have seen in the previous chapters. When it comes to implementation practices in engaging with a crowd, we saw a core set of best practices in Chapter 5. However, given the importance of defect management, we decided to dedicate one chapter purely to crowdsourced testing defect management. This is an area that can often make or break a test team’s relationship with the rest of the product team and also impact product quality, either positively or negatively, making this a very important area of discussion. We will start off talking about some core problems and challenges in any defect management effort, and then move on to defect management, specifically in the crowdsourced testing space. To promote easier understanding, we will organize this chapter as a series of questions and answers, anticipating the questions you all may have as readers.
