知识卡片

普通读书笔记卡 · 1841.h.1.a.9.a

为可测试性安排边界

理解等级:中级

可测试性不是事后补一套测试框架,而是让重要行为可以在隔离条件下观察和验证。把业务逻辑与消息基础设施混在一起会使两边都难测;拆清责任能同时改善测试与维护。难测区域通常值得检查其职责和依赖边界。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • Building Evolvable Architectures · 查看原书依据

      Many architects complain that their architecture has difficult areas to test, which isn’t surprising when testability often isn’t a priority when designing the architecture. Conversely, if architects design their architecture with testing in mind, they build easier ways to test parts of the architecture in isolation. For example, a lot of research and tools exist in the microservices ecosystem to facilitate testing, contributing to its

    参考来源

    - 位置:《Building Evolutionary Architectures Automated Software Governance, 2nd Edition》第07章《Building Evolvable Architectures》(来源项目:a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Building Evolutionary Architectures Automated Software Governance, 2nd Edition/_epub-src/OEBPS/ch07.html;段落定位:if architects design their architecture with testing in mind) - 结论依据:原文对“为可测试性安排边界”的定义或案例,支撑“可测试性不是事后补一套测试框架,而是让重要行为可以在隔离条件下观察和验证”的归纳。据其上下文,把业务逻辑与消息基础设施混在一起会使两边都难测;拆清责任能同时改善测试与维护。 - 原始内容:Many architects complain that their architecture has difficult areas to test, which isn’t surprising when testability often isn’t a priority when designing the architecture. Conversely, if architects design their architecture with testing in mind, they build easier ways to test parts of the architecture in isolation. For example, a lot of research and tools exist in the microservices ecosystem to facilitate testing, contributing to its