Introduction
We will study this part of the theory test knowledge in. Software testing is an important software quality assurance activities, need to analyze whether the tested software products to meet product demand and is generally in the habit of application functionality, performance, compatibility, reliability, security, and other relevant theoretical basis, method . Theory test is a test event analysis products, important design criteria use cases, test is a model to guide the activities carried out smoothly.
In this section we will learn the basic test model, test common classification, a variety of test case design, study this part of the knowledge will help us to establish the basic theory test system, building the test case design, test for the future work will be of great benefit.
Test theories
of learning objectives
Master V model (emphasis)
master W (double V) model (focused) to master the software testing classification (focus)
Learning objectives
to master the waterfall model (focused)
to understand the rapid prototyping model
to understand the spiral model
First, the software development process model
In a few decades the practice of software development, people have come up a lot of software development models used to describe and represent a complex development process, such as:
Software testing and software development models are closely linked, as a tester, you should fully understand the software development model in order to pinpoint their position in which, in order to play to their value.
1.1 waterfall model
(1) is a linear model, plays an important role in all models, is a foundation for all other models
(2), each implementation phase once, software development linear order. 
Note:
Test entry point:
the testing phase in the software implementation, you must allow sufficient time after the completion of the code to testing activities. Otherwise, the test is not sufficient, a lot of problems to be exposed until late in the project.
1.1.1 瀑布模型的优缺点
优点:
(1)、开发的各个阶段比较清晰。
(2)、当前一阶段完成后，只需关注后续阶段。
缺点：
(1) 依赖于早期的需求调查，不适应需求的变化。
(2) 风险往往延至后期才显露，失去及早纠正的机会。
(3) 前面未发现的错误会传递并扩散到后面的阶段，可能导致项目失败。
1.2快速原型模型(了解)
在开发真实系统之前，构造一个原型，在该原型的基础上，逐渐完成整个系统的开发工作。
第一步是建造一个快速原型，实现用户与系统的交互，用户对原型进行评价，进一步细化待开发软件的需求。通过逐步调整原型使其满足用户的要求，开发人员可以确定用户的真正需求是什么。
第二步是在第一步的基础上开发出用户满意的软件产品。
1.2.1 快速原型模型的优缺点
优点:
(1)克服瀑布模型的缺点，更好地满足用户的需求并减少由于软件需求不明确带来的项目开发风险。
缺点:
(1)不适合大型系统的开发(适合开发小型的、灵活性高的系统)。前提要有一个展示型的产品原型，因此在一定程度上可能会限制开发人员的创新。
1.3 螺旋模型(了解)
螺旋模型将开发过程分为几个螺旋周期，每个螺旋周期大致和瀑布模型相符合，螺旋模型沿着螺旋线旋转，即在坐标的4个象限上分别表示了4个方面的活动，如图所示:
1.3.1 螺旋模型的优缺点
优点:
(1) 螺旋模型很大程度上是一种风险驱动的方法体系。
(2) 在每个阶段之前及经常发生的循环之前，都必须首先进行风险评估。
Disadvantages:
(1) spiral model requires a considerable wealth of experience and expertise in risk assessment.
(2) in the risky project development, if it is not able to promptly identify risks will inevitably result in significant losses.
(3) excessive number of iterations will increase development costs, delay submission time.