知识卡片
架构与业务测试边界
业务测试验证领域规则,如邮寄地址组成;架构适应度函数验证弹性、结构依赖等质量属性,原则上无需了解具体业务即可执行。是否需要领域知识是区分两者的实用线索,但并非严格二分:两类测试可能交叉,关键在验证目标。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 没有最佳实践时如何决策 · 查看原书依据
Fitness functions validate architecture characteristics, not domain criteria; unit tests are the opposite. Thus, an architect can decide whether a fitness function or unit test is needed by asking the question: “Is any domain knowledge required to execute this test?” If the answer is “yes,” then a unit/function/user acceptance test is appropriate; if “no,” then a fitness function is needed.
参考来源
- 位置:《Software Architecture: The Hard Parts》第1章《没有最佳实践时如何决策》(来源项目:book-sources;源文件:extracted/Software Architecture The Hard Parts Modern Trade-Off Analyses for Distributed Architectures (Neal Ford, Mark Richards, Pramod Sadalage etc.)/_epub-src/OEBPS/ch01.xhtml)
- 结论依据:原文的定义、比较或案例支持“业务测试验证领域规则,如邮寄地址组成;架构适应度函数验证弹性、结构依赖等质量属性,原则上无需了解具体业务即可执行”;正文据此解释其用途与适用边界。
- 原始内容:Fitness functions validate architecture characteristics, not domain criteria; unit tests are the opposite. Thus, an architect can decide whether a fitness function or unit test is needed by asking the question: “Is any domain knowledge required to execute this test?” If the answer is “yes,” then a unit/function/user acceptance test is appropriate; if “no,” then a fitness function is needed.