Chapter 16


1:

Describe the pesticide paradox and how bringing in new people to look at the software helps solve it.

A1:

The pesticide paradox (described in Chapter 3, "The Realities of Software Testing") is the situation that occurs if you continue to test software with the same tests, or the same people. Eventually, the software seems to build up an immunity to the tests because no new bugs are found. If you change the tests or bring in new testers, you'll find new bugs. The bugs were always there, it's just that the new approach made them visible.

2:

What are a few positives to having a beta test program for your software?

A2:

It gets lots of additional people looking at the software. It's a good way to find configuration and compatibility problems.

3:

What are a few cautions to consider with a beta test program?

A3:

A beta test is no substitute for an organized, planned, methodical test approachit's not good at general bug finding. You should know who the beta testers are in regards to their experience level, equipment, and needs to ensure that you get what you expect out of the test.

4:

If you're testing for a small software company, why would it be a good idea to outsource your configuration testing?

A4:

The expense and overhead to stock and manage a configuration testing lab is very high and would likely be prohibitive for a small company or project.



    Software Testing
    Lessons Learned in Software Testing
    ISBN: 0471081124
    EAN: 2147483647
    Year: 2005
    Pages: 233

    flylib.com © 2008-2017.
    If you may any questions please contact us: flylib@qtcs.net