Unit testing and Design by Contract
单元测试和契约式设计
Using AOP for transparent Design by contract.
用AOP进行透明的契约式设计。
Design by Contract, or defensive programming.
契约式设计或防御性编程。
Could you give an overview of Design by Contract?
你可以概括描述一下契约式设计吗？
See the section Design by contract for details on this.
有关这一点的详细信息，请参阅按合同设计一节。
Questions: on Design By Contract Inheritance Issue...?
问题：对设计合同的继承问题…？
Bertrand Meyer introduced the concept of Design by Contract.
BertrandMeyer介绍了契约式设计的概念。
Bill Venners: Could you give an overview of Design by Contract?
你可以概括描述一下契约式设计吗？
You don't really need Contract4J to write Design by Contract tests.
编写契约式设计测试，实际上可以不需要Contract4J。
Design by contract is a tool for finding and fixing logic bugs in code.
契约式设计是一种发现和修复代码中逻辑错误的工具。
This is, of course, where the techniques of Design by Contract come in.
当然，这就是契约式设计技术所包含的内容了。
Code Contracts is the.net implementation of the Design by Contract concept.
代码契约(Code Contracts)是“契约式设计”的。NET实现。
He then goes into Design by Contract principles, and requirements management.
接着谈到契约式设计(Design by Contract)原则和需求管理。
AspectJ home page: Learn more about using aspects for Design by Contract testing.
AspectJ主页：了解使用方面进行契约式设计测试的更多内容。
Design by contract is an important approach to design for testability of software.
合约式设计是一种重要的软件易测试性设计方法。
Design by contract also makes explicit the contract definition that is more implicit in unit tests.
契约式设计也做了显式的合约定义，而在单元测试中这些更隐式。
Design by Contract has some advantages over unit testing, but the two methods are complementary.
契约式设计比起单元测试有些优势，但是这两种方法是互补的。
Another approach is design by Contract, a proven technique for clarifying component design details.
另一种方法是契约式设计，这是阐明组件设计细节的一项切实可行的技术。
Note that Design by Contract tests can be turned off in production deployments to remove their overhead.
注意，在生产部署时可以关闭契约式设计测试，以消除它们的开销。
The idea of the design by contract is introduced and applied into the analysis of the business component.
介绍了契约式设计的思想，并在业务构件的分析中引入了契约式设计，从而构造出可信的业务构件。
Static verification and design by contract relay on theorems that are mostly based on deterministic approach.
静态验证和契约式设计理论大部分属于确定性理论的范畴。
A Design by Contract tool like Contract4J is most helpful in situations where unit testing is sparse or difficult.
像Contract4J这样的契约式设计工具在单元测试比较分散或比较困难的时候最有帮助。
Design by contract avoids extra code and improves performance, as long as all clients of a class abide by the contract.
契约式设计避免了额外的编码并提高了性能，只要所有的客户都遵守契约。
As previously noted, it is true that unit testing and Design by Contract accomplish similar objectives by different means.
正如前面提到过的，单元测试和契约式设计用不同的方式实现类似的目标。
Now that you understand the necessary infrastructure for implementing Design by Contract with AOP, you can put it to work.
理解了用AOP实现契约式设计的必要基础设施后，就可以让它工作了。
Therefore, strictly speaking, it may appear that Design by Contract isn't an appropriate candidate for an AOP approach at all.
所以，严格来说，契约式设计看起来可能根本不是AOP 技术的备选方案。
Significant patterns include design by contract, well-defined interfaces, composability, predictable behavior, and component testing.
重要模式包括契约式设计、定义良好的接口、可组合性、可预测的行为和组件测试。
Design by Contract, or programming by Contract, is not a new concept in programming, many languages already having such implementations.
契约式设计(或“契约式编程”)并不是编程领域的新概念，许多语言中已经有类似的实现了。
Find out what happens when you combine defensive programming, design by contract, and an easy-to-use generic validation framework called OVal.
尝试为应用程序整合进防御性编程、契约式设计和一种叫做OVal的易用的通用验证框架。
For your internal needs, you want to use Design by Contract since you have control over the developers in your organization that will use the classes.
为了你的内部需要，你要使用契约式设计进而来使用类，因为你已经在你的组织中控制开发人员。
应用推荐