Test Model
V Software Testing Model
The "code" for the sector, R & D line is left, right is the test line.
Consistent with the advantages and disadvantages of the waterfall model.
目的：改进软件开发的效率和效果。
各个阶段：
用户需求：了解需求
需求分析与系统：了解、确定需求的范围，制定测试计划
概要设计 与 详细设计：测试人员不参与
编码：测试人员介入，编写测试用例
单元测试 和 集成测试：
做的是测试的工作，但是参与的角色，为白盒测试工程师或研发人员(传统的测试人员不参与)
（白盒测试————测试人员写代码测研发人员写的代码）
系统测试（核心）：
测试人员花费时间最长的阶段
工作：搭建环境、数据准备、测试执行、缺陷管理、测试报告输出/编写
验收测试：
测试人员不测试，此阶段的验收人员-->用户
测试人员的工作：给用户培训软件的使用，并收集用户在使用中的反馈和建议
明确的标注了测试过程中存在的不同类型的测试，
并且清楚的描述了这些测试阶段和开发过程期间各阶段的对应关系。
V模型指出，单元和集成测试应检测程序的执行是否满足软件设计的要求；
系统测试应检测系统功能、性能的 质量特性是否达到系统要求的指标；
验收测试确定软件的实现是否满足用户需要或合同的要求。
局限性:仅仅把测试作为在编码之后的一个阶段，未在需求阶段就进入测试。
Software Testing W model (double V model)
各个阶段：
用户需求：为验收测试做准备
需求分析与系统：确定需求的范围，制定测试计划，为系统测试做准备
概要设计：为集成测试做准备，测试计划进一步细化
详细设计：为单元测试准备，搭建测试用例的框架
编码：测试人员写测试用例，还要进行单元测试(不需要代码全部写完)————单元测试
集成：集成测试
实施：系统测试
交付：验收测试
W模型增加了软件各开发阶段中应同步进行的验证和确认活动。
W模型，双V模型，分别代表测试与开发过程，图表示出了测试与开发的并行关系。
W模型特点：
测试的对象不仅是程序，需求、设计等同样要测试，测试与开发是同步进行的。
W模型优点：
有利于尽早地全面的发现问题。
例如，需求分析完成后，测试人员就应该参与到对需求的验证和确认活动中，以尽早地找出缺陷所在。
同时，对需求的测试也有利于及时了解项目难度和测试风险，及早制定应对措施，
显著减少总体测试时间，加快项目进度。
局限性：
需求、设计、编码等活动被视为串行的；
测试和开发活动也保持着一种线性的前后关系，上一阶段完全结束，
才可正式开始下一个阶段工作。无法支持敏捷开发模式。
对于当前软件开发复杂多变的情况，W模型并不能解除测试管理面临着困惑。
V / W are not suitable for agility
Configuration management and software testing
What is Configuration Management
Configuration Management: Con fi guration Management
is identified by the software on different software lifecycle point of time of the configuration, and the software are identified configuration changes items for system control, to achieve integrity and traceability assurance software products the process of.
Software configuration management
Software development process will produce a large number of software products (including documentation, source code and data, etc.), and there is a relationship between these products. The same software product changes also occur, resulting in many versions. Software development teams must clearly know which products have these products which have different forms and versions. The development team must clearly know how to change the product to notify the affected group. If you can not effectively understand the software product and its changes, the development team will be difficult to assemble these software products, it is difficult to get the required software products.
The benefits of implementing software configuration management
Implementing software configuration management (SCM), at least give the project team to bring the following benefits.
(1) can be effectively managed change project documentation, code, etc.
(2) the ability to easily reproduce the historical version of a file.
(3) to re-compile a version of history, it makes maintenance easier.
(4) enables remote multi-team development, parallel development to become a reality.
(5) from the company level to see, unified configuration management process can improve the efficiency of movement of persons between the project team.
Configuration management and software testing
Testers should take the test and then compile the source code from the configuration repository, only to see the new build version of the Bug is no longer present, can the defect library Bug off.
