返回主题:构建来源与软件供应链安全

此卡片不在当前主题的阅读序列中,可返回主题继续阅读。

知识卡片

普通读书笔记卡 · 517.g.2.a.4

测试范围从风险出发

理解等级:中级

基础设施测试要覆盖代码能否应用、资源是否正确、工作负载行为,以及安全、合规、来源、性能、扩展、可用性和运维能力。按变更引入的具体风险设计可重复验证,而非只套单元测试与界面测试清单。交叉功能要求属于开发工作本身,也能在离线、资源级和全系统多层验证。

这张卡片看不懂?

已有反馈 · 0 / 10 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • 基础设施代码测试策略 · 查看原书依据

      Quality assurance is about managing the risks of applying code to your system. Will the code break when applied? Does it create the right infrastructure? Does the infrastructure work the way it should? Does it meet operational criteria for performance, reliability, and security? Does it

    参考来源

    - 位置:《Infrastructure As Code》第17章《基础设施代码测试策略》(来源项目:book-sources;源文件:extracted/Infrastructure As Code/_epub-src/OEBPS/ch17.html) - 结论依据:原文在该段定义概念并解释相关过程或限制,支撑“基础设施测试要覆盖代码能否应用、资源是否正确、工作负载行为,以及安全、合规、来源、性能、扩展、可用性和运维能力”这一核心结论;正文的用途与边界据同小节后续论述整理。 - 原始内容:Quality assurance is about managing the risks of applying code to your system. Will the code break when applied? Does it create the right infrastructure? Does the infrastructure work the way it should? Does it meet operational criteria for performance, reliability, and security? Does it