知识卡片
测试速度也是设计问题
基础设施测试慢,常由组件过大、依赖链长及真实平台准备时间造成。可拆小部署单元、隔离依赖、先离线后在线,并用模拟器与测试替身尽早验证。若大量时间花在修测试而非产品,或多项测试总一同失败,应检查测试设计并简化,而非只增加机器。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 基础设施代码测试策略 · 查看原书依据
Divide infrastructure into more tractable pieces Including testability as a factor in designing a system’s structure is useful, as it’s one of the key ways to make the system easy to maintain, extend, and evolve. Making pieces smaller is one tactic, as smaller pieces are
参考来源
- 位置:《Infrastructure As Code》第17章《基础设施代码测试策略》(来源项目:book-sources;源文件:extracted/Infrastructure As Code/_epub-src/OEBPS/ch17.html)
- 结论依据:原文在该段定义概念并解释相关过程或限制,支撑“基础设施测试慢,常由组件过大、依赖链长及真实平台准备时间造成”这一核心结论;正文的用途与边界据同小节后续论述整理。
- 原始内容:Divide infrastructure into more tractable pieces Including testability as a factor in designing a system’s structure is useful, as it’s one of the key ways to make the system easy to maintain, extend, and evolve. Making pieces smaller is one tactic, as smaller pieces are