知识卡片
可测试性困难要有人承接
单测所需的隔离层、框架与工具应提前设计并分配实现时间,复杂场景还需要开发测试环境、集成用例和快速烟测。某处无法测试或间歇失败时,应升级给架构师协作处理,而非让第一个遇到问题的开发者独自承担,也不能接受永久“不好测”例外。可测试性是团队基础能力,需要持续投资。
[[快速可靠构建保护修改意愿]]依赖这些测试基础能力,不能只要求开发者自己解决全部环境障碍。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 构建与演进系统 · 查看原书依据
Developers should be able to write unit tests easily, but sometimes writing unit tests requires specific frameworks or tools. It is important to design those layers explicitly and to allocate time for implementation, not waiting for the developer who first needs those tests to figure it out.
参考来源
- 位置:《Software Architecture and Decision-Making》第13章《Building and Evolving the Systems》(来源项目:book-sources;源文件:extracted/Software Architecture and Decision-Making Leveraging Leadership, Technology, and Product Management to Build Great Products… (Srinath Perera)/_epub-src/ch13.xhtml)
- 结论依据:摘录说明单测所需的隔离层、框架与工具应提前设计并分配实现时间,复杂场景还需要开发测试环境、集成用例和快速烟测。其余条件结合本章相邻例子与取舍说明,数字示例不作当前性能承诺。
- 原始内容:Developers should be able to write unit tests easily, but sometimes writing unit tests requires specific frameworks or tools. It is important to design those layers explicitly and to allocate time for implementation, not waiting for the developer who first needs those tests to figure it out.