创业管理（李雪）part 4.pptVIP

Test Sharing One common approach is to simply swap test responsibilities with another tester for a few hours or a few days. Think of it as You run my tests and Ill run yours. A fun way to share the testing tasks is to schedule a bug bash. A bug bash is a period of time (usually a couple hours) in which the entire test team stops their normally assigned testing tasks to participate in the bash. In a bug bash, a specific area of the software is selected and all the testers concentrate their testing on that one area or set of features. A bug bash could determine if the bugs have been missed by normal testing or if its just well written code. Its a good idea to get your product support team helping you test the product early in the design cycle to help identify and fix usability bugs. Beta Testing Beta testing is the term used to describe the external testing process in which the software is sent out to a select group of potential customers who use it in a real-world environment. Beta testing usually occurs toward the end of the product development cycle and ideally should just be a validation that the software is ready to release to real customers. Beta Testing There are several things to think about when planning for or relying on a beta test: Who are the beta testers? Similarly, how will you know if the beta testers even use the software? Beta tests can be a good way to find compatibility and configuration bugs. Usability testing is another area that beta testing can contribute to if the participants are well chosen a good mix of experienced and inexperienced users. Besides configuration, compatibility, and usability, beta tests are surprisingly poor ways to find bugs. A beta test program can take up a lot of a testers time. Outsourcing Your Testing Configuration and compatibility testing are typically good choices for outsourcing. Localization testing is another example that often lends itself to outsourcing. The success, or failure, of the outsourci