Functional testing tools (Watir, Selenium, Marathon Man) are integrated as gatekeeper events to the build. Integration tests with external tools and products.
在构建过程中集成功能测试工具，并将其作为构建成功的条件。对与外部工具和产品的集成进行测试。
3
Internal Gatekeeper
对内防御
Unit tests and code characteristics are implemented as gatekeeper events that will
prevent a build from completing.
在构建过程中集成单元测试和代码特征检查，并将其作为构建成功的条件。
2
Constant
频繁执行
Build velocity is maximized &＃8211; that is, build is happening with the maximum frequency. State of the build the responsibility of the team.
建立良好的项目团队构建纪律并得到团队的认同和认真执行。
尽快构建即保持最高的构建频率。整个团队对构建状态负责。
1
Repeating
重复执行
Build is repeatable and automated, but doesn‘t happen with maximum frequency
as permitted by the technology. State of the build is a responsibility of the team.
构建过程是自动化的、可重复的，但受限于技术原因不能保持最高的构建频率：整个团队对构建状态负责。
0
Repeatable
具备重复执行能力
Build process is repeatable and static, but still likely performed manually and infrequently; the build may be owned by a specific member of the team.
构建流程是可重复的，但并不活跃，往往手动触发，而且频率较低。构建由团队中某个特定的成员负责。
-1
Custom
不可重复
Build is manually performed, custom every time, and infrequently performed; it may be owned by a specific member of the team
构建必须手动执行，每次执行都需要专门做一些配置，执行频率较低，构建由团队中某个特定的成员负责。
评估指引：
-1：项目级构建频度低于一周一次，集成构建无规律
0：项目级构建频度做到一周至少两次，每周至少有一次整体集成构建
1：项目级构建频度做到每天一次，构建每天一次
2：项目级构建做到完成一块提交一次，CI工具支持每次提交出发增量构建
3：所有内部开发团队达到构建3级，基本的功能冒烟测试加入到每次构建中，用以保证内部质量
3+：自动化集成测试加入到构建中，自动化部署和验收测试保证外部质量
实践八：Testing–测试
Theme
Level
State Description
Reference Implementations
Analysts are part of test planning
分析师会参与制定测试计划
3+
Comprehensive, Integrated
全面的、集成的
Owned by QA/Dev/Analyst, complete integration with build, non-functional and
Owned by QA/Dev/Analyst, non-functional and integration testing undergo complete inspection tests. Functional testing is integrated with the build. Developers practice TDD.
Owned by QA/Dev. Functional testing is not integrated with the build and may still be a full inspection process. Non-functional and integration tests might be incrementally integrated or End of Lifecycle
测试由测试人员和Dev负责。功能测试未集成进构建过程，由完整的审查过程来保障。
非功能测试和集成测试可能是增量集成的，或者是在软件开发周期的末尾阶段执行的。
Testing is a QA problem
测试只是测试人员的事情
0
Independent, Inspection
独立的，审查
Owned by QA. Functional testing is full inspection and not integrated with the build.
Incremental non-functional and integration tests are rudimentary inspection tests, or performed only at End of Lifecycle.
Significant investment in up-front frameworks; traditional enterprise re-use program (e.g., component libraries); SOA done wrong (e.g., speculative taxonomy defined);
实践十：ConfigurationManagement–配置管理
Theme
Level
State Description
Reference Implementations
3+
Enterprise CM
企业级配置管理
可以在多个提供商提供的解决方案之间协调配置管理。
CM is coordinated across vendor supplied solutions
3
Coordinated CM
协调的配置管理
在同一个程序内协调多个项目的配置管理。
CM is coordinated across projects within the same programme
2
Automatic CM
自动化配置管理
自动化的配置管理流程意味着更少的意外。乐观锁。通过构建和测试保证CM纪律。原子提交。
The ―code fairy does not run free‖ state – automation of CM rules. Optimistic locking.
京公网安备 11010802041100号