知识卡片
持续测试追求即时反馈
持续测试应在写代码、完成故事之前就发生,并在每次推送后立即运行 CI 和交付验证。按夜间或周期批量运行会把多人变更混在一起,失败时难定位责任变更。区分即时测试与延后测试,可发现哪些反馈被人工审查或排期无谓阻塞;结对也是实时审查的一种。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 基础设施代码测试策略 · 查看原书依据
The CI build and the CD pipeline should run immediately every time someone pushes a change to the codebase. Running immediately on each change not only gives them feedback faster but also ensures a small scope of change for each run. If the pipeline runs
参考来源
- 位置:《Infrastructure As Code》第17章《基础设施代码测试策略》(来源项目:book-sources;源文件:extracted/Infrastructure As Code/_epub-src/OEBPS/ch17.html)
- 结论依据:原文在该段定义概念并解释相关过程或限制,支撑“持续测试应在写代码、完成故事之前就发生,并在每次推送后立即运行 CI 和交付验证”这一核心结论;正文的用途与边界据同小节后续论述整理。
- 原始内容:The CI build and the CD pipeline should run immediately every time someone pushes a change to the codebase. Running immediately on each change not only gives them feedback faster but also ensures a small scope of change for each run. If the pipeline runs