Ron Patton软件测试习题：自动化测试、Bug Bashes、Beta Testing

以下内容大部分来自 ron-patton-software-testing
PART IV Supplementing Your Testing

Chapter 14 Automated Testing and Test Tools

1. A few benefits of using software test tools and automation.自动化测试优点

• They can speed up the amount of time it takes to run your test cases.
• They can make you more efficient by giving you more time for test planning and test case development.
• They’re accurate, precise, and relentless （持续的）.

2. What are a few drawbacks or cautions to consider when deciding to use software test tools and automation? 自动化测试缺点

• Because software can change during the product’s development, your test tools will need to change, too.
• You can fall into a trap of spending too much time designing tools and automation, neglecting actual testing.
• It’s easy to rely on automation too much. There’s no substitute for testing the software yourself.

3. What’s the difference between a tool and automation?差异

• A test tool will help you test, making it easier for you to perform a manual testing task.
• Automation is also a tool, but it will run without your intervention（介入）.

4. viewer tools vs injector tools

Both types of tools hook into the software at points not normally accessible to the average user. 两种类型的工具都在普通用户通常无法访问的位置挂接到软件中。

• Viewer tools are non-invasive 非侵入性as they allow you to see only what’s happening.
• Injector tools are invasive侵入性—they allow you not only to see what’s happening, but also to manipulate it. You can try test cases that might otherwise be difficult or impossible to perform at the normal user level. 您可以尝试在正常用户级别上可能难以执行或无法执行的测试用例。

5. True or False: An invasive tool is the best type because it operates closest to the software being tested.侵入性工具最好？

False. Being invasive or non-invasive doesn’t make a tool good or bad. The software being tested and the test case that needs to be performed will dictate the best choice of tool.

6. What’s one of the simplest, but effective, types of test automation?

Keystroke and mouse action record and playback are the simplest type of automation that can effectively find bugs.
击键和鼠标动作的记录和回放是可以最有效地发现错误的最简单的自动化类型。

7. A few features that could be added to test automation you described in question 6 to make it even more effective.

• Simple programming of steps rather than captured steps.
• The ability to pause or wait for the software to react to the actions.
• Some type of simple verification so that the macros know whether a bug has occurred.

8. What advantages do smart monkeys have over macros and dumb monkeys?

• They’re almost self-aware.
• They know the software’s state table so they know where they are and what they can do.

Chapter 15 Bug Bashes and Beta Testing

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

(描述农药悖论, 如何解决该矛盾。)

• The pesticide paradox 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? beta测试的优点

• 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?

• A beta test is no substitute for an organized, planned, methodical test approach—it’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?

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.