On integration testing object-oriented software systems

面向对象软件系统的集成测试

• 批准号: 239119-2011
• 负责人: Labiche, Yvan
• 金额: $ 2.4万
• 依托单位: Carleton University
• 依托单位国家: 加拿大
• 项目类别: Discovery Grants Program - Individual
• 财政年份: 2013
• 资助国家: 加拿大
• 起止时间: 2013-01-01 至 2014-12-31
• 项目状态: 已结题
• 来源: https://www.nserc-crsng.gc.ca/ase-oro/Details-Detailles_eng.asp?id=524579
• 关键词: integration; testing; object; oriented; software

Most, if not all, of the software testing approaches are incremental in nature: either by following an agile (or extreme) development process or a unified process, testing activities are performed in increments. Any incremental class testing approach for an object-oriented software system has to answer the two following questions: What integration process, indicating in which order classes are (integration) tested, should be selected? Which test design techniques should be applied to unit and integration test classes? Although there is a fairly large number of reported works on both questions, much remains to be done. On the one hand, class (integration) testing techniques have mostly been described without any consideration for any integration process. On the other hand, integration processes have been suggested without much consideration for how they could be used in practice, along with class (integration) test design techniques. It appears that there is a lack of research and practical results on how a class integration process can be used to conduct class (integration) testing. Therefore, it is often difficult to answer any of the two aforementioned questions. This, along with a lack of tool support, is likely one of the main reasons why the notion of integration testing is not well understood by practitioners and therefore why integration testing activities are seldom performed (e.g., with the intend to reveal integration faults).

大多数（如果不是全部的话）软件测试方法本质上是增量的：通过遵循敏捷（或极端）开发过程或统一过程，测试活动是增量执行的。任何面向对象软件系统的增量类测试方法都必须回答以下两个问题：应该选择什么样的集成过程，表明类（集成）测试的顺序？哪些测试设计技术应该应用于单元和集成测试类？虽然在这两个问题上有相当多的报道，但仍有许多工作要做。一方面，类（集成）测试技术大多是在没有考虑任何集成过程的情况下描述的。另一方面，集成过程的提出并没有考虑如何在实践中使用，沿着类（集成）测试设计技术。似乎缺乏关于如何使用类集成过程来进行类（集成）测试的研究和实际结果。因此，通常很难回答上述两个问题。这沿着缺乏工具支持，很可能是集成测试的概念没有被从业者很好地理解的主要原因之一，因此也是集成测试活动很少被执行的主要原因之一（例如，旨在揭示整合故障）。