Testing Types - 读书笔记

看到 Wikipedia 上面有一篇对于软件测试的综述，挺有总结性，做下读书笔记。

Wikipedia 的这篇文章，可以通过下面的 URL 访问:
http://en.wikipedia.org/wiki/Software_testing

Testing Types: 测试的类型分布在各个测试的级别当中，常用的有 18 种：

1 Installation testing
2 Compatibility testing
3 Smoke and sanity testing
4 Regression testing
5 Acceptance testing
6 Alpha testing
7 Beta testing
8 Functional vs non-functional testing
9 Destructive testing
10 Software performance testing
11 Usability testing
12 Accessibility testing
13 Security testing
14 Internationalization and localization
15 Development testing
16 A/B testing
17 Concurrent testing
18 Conformance testing or type testing

截取几个 testing type 做个自我了解：

Alpha testing
Alpha testing is simulated or actual operational testing by potential users/customers or an independent test team at the developers’ site. Alpha testing is often employed for off-the-shelf software as a form of internal acceptance testing, before the software goes to beta testing.

Beta testing
Beta testing comes after alpha testing and can be considered a form of external user acceptance testing. Versions of the software, known as beta versions, are released to a limited audience outside of the programming team known as beta testers. The software is released to groups of people so that further testing can ensure the product has few faults or bugs. Beta versions can be made available to the open public to increase the feedback field to a maximal number of future users and to deliver value earlier, for an extended or even infinite period of time (perpetual beta).

Functional vs non-functional testing
Functional testing refers to activities that verify a specific action or function of the code. These are usually found in the code requirements documentation, although some development methodologies work from use cases or user stories. Functional tests tend to answer the question of “can the user do this” or “does this particular feature work.”

Non-functional testing refers to aspects of the software that may not be related to a specific function or user action, such as scalability or other performance, behavior under certain constraints, or security. Testing will determine the breaking point, the point at which extremes of scalability or performance leads to unstable execution. Non-functional requirements tend to be those that reflect the quality of the product, particularly in the context of the suitability perspective of its users.

A/B testing
A/B testing is basically a comparison of two outputs, generally when only one variable has changed: run a test, change one thing, run the test again, compare the results. This is more useful with more small-scale situations, but very useful in fine-tuning any program. With more complex projects, multivariant testing can be done.
(比如我们用到的订单输入测试，对订单的数量做调整等）