Collaborative: Exploiting Component Contracts for Static Analysis and Testing

协作：利用组件契约进行静态分析和测试

• 批准号: 0306286
• 负责人: Matthew Flatt
• 金额: $ 16万
• 依托单位: University of Utah
• 依托单位国家: 美国
• 项目类别: Standard Grant
• 财政年份: 2003
• 资助国家: 美国
• 起止时间: 2003-07-01 至 2005-06-30
• 项目状态: 已结题
• 来源: https://www.nsf.gov/awardsearch/showAward?AWD_ID=0306286&HistoricalAwards=false
• 关键词: Collaborative; Exploiting; Component; Contracts; Static

0306270/0306286Collaborative: Exploiting Component Contracts Robert Bruce Findler/Matthew FlattDespite the central role of testing in the development process, current programming languages and environments provide scarcely any support for testing. Most testing research has focused on generatingtest inputs and test oracles from program specifications, but program specifications are difficult to produce and maintain. Consequently, language and environment designers remain unmotivated to support specifications, and opportunities to support testing are lost.Contracts offer a route around the specification problem. Contracts are a form of lightweight specification that work with the base programming language, i.e., there is no need for the programmer to learn a special logic for writing specifications. Contracts are monitored as the program executes, which means that the programmer is forced to maintain contracts with the code. Since contracts are essentially a generalization of assert statements, experience suggests that programmers will use them.The investigators focus on contracts as a specification language for automatic test suite generation. To validate their investigations, they will extend the DrScheme programming environment to support unittesting at component boundaries. In addition, they will use the new testing infrastructure to test DrScheme itself.

0306270/0306286协作：利用组件合同Robert布鲁斯Findler/Matthew Flatt尽管测试在开发过程中扮演着核心角色，但当前的编程语言和环境几乎没有为测试提供任何支持。大多数测试研究都集中在从程序规格说明生成测试输入和测试预言，但程序规格说明很难产生和维护。因此，语言和环境设计者仍然没有动力去支持规格说明，并且失去了支持测试的机会。契约是一种轻量级规范的形式，它与基础编程语言一起工作，即，程序员不需要学习用于编写规范的特殊逻辑。合约在程序执行时被监视，这意味着程序员被迫维护与代码的合约。由于合约本质上是断言语句的概括，经验表明程序员会使用它们。为了验证他们的研究，他们将扩展DrScheme编程环境，以支持组件边界的单元测试。此外，他们将使用新的测试基础设施来测试DrScheme本身。