知识卡片
运维要求可被测试
性能可先测试基础网络链路;扩展测试既要确认自动增加节点,也要确认容量真的提升;可用性测试可销毁节点检查替换或优雅退化;可运维性测试可注入错误验证告警、日志和维护任务。测试应断言需求结果,而不是只确认某开关已配置。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 基础设施代码测试策略 · 查看原书依据
Automated tests can prove that scaling works correctly—for example, checking that an auto-scaled cluster adds nodes when it should. Tests can also check whether scaling gives you the outcomes that you expect. For example, perhaps adding nodes to the cluster doesn’t improve capacity, because of
参考来源
- 位置:《Infrastructure As Code》第17章《基础设施代码测试策略》(来源项目:book-sources;源文件:extracted/Infrastructure As Code/_epub-src/OEBPS/ch17.html)
- 结论依据:原文在该段定义概念并解释相关过程或限制,支撑“性能可先测试基础网络链路;扩展测试既要确认自动增加节点,也要确认容量真的提升;可用性测试可销毁节点检查替换或优雅退化;可运维性测试可注入错误验证告警、日志和维护任务”这一核心结论;正文的用途与边界据同小节后续论述整理。
- 原始内容:Automated tests can prove that scaling works correctly—for example, checking that an auto-scaled cluster adds nodes when it should. Tests can also check whether scaling gives you the outcomes that you expect. For example, perhaps adding nodes to the cluster doesn’t improve capacity, because of