基于领域知识软件测试方法的研究与应用

采用本体理论来表示软件测试领域知识,完成对测试用例的快速分类与检索,设计出一个专门应用于软件测试领域的测试用例知识管理系统,并以某公司编码物料软件为测试对象,验证了基于领域知识的软件测试的可行性和适应性。该系统缩短了编写测试用例的时间,最大限度地提高了测试用例的复用率,研究课题的价值也在于此。     

构建软件测试领域不确定性知识图谱

由于软件测试技术的不足和成本的限制,从历史软件测试资产中获取的可复用知识对象具有不确定性。为了更有效地复用历史测试知识,软件测试知识复用系统应当建模和评估知识的不确定性。模糊知识图谱是利用不确定性理论对典型知识图谱的一种扩展,在利用语义网络描述知识实体及其关系的基础上,通过模糊关系建模知识不确定性。通过分析软件测试资产,确定测试需求、测试用例和问题报告三类知识的表现形式和内涵,建立软件测试资产本体和领域特征本体作为知识图谱模式层,提出一种基于信息论的领域特征抽取方法,构建领域特征图谱。分析软件测试不确定性的产生原因,基于粗糙集理论对本体进行扩展,在软件测试资产和领域特征之间建立模糊关系。提出一种基于知识粒度的模糊置信度计算方法,用于构建软件测试模糊知识图谱,为软件测试中不确定性知识的复用提供了基础。通过一个指挥信息系统领域实例验证了方法的可行性。     

一种基于本体的测试用例研究与应用

测试用例是软件测试的重要组成,也是软件测试成败的关键性因素之一。测试用例的完备性和复用性研究已经成为当前软件测试领域的两大热点。论文提出一种基于本体论的测试用例分析与刻画方法,它统一了测试用例的内涵,并为测试用例提供了可穷举的外延选择。该方法解决了软件测试用例完备性和复用性问题。     

测试用例描述语言研究

软件测试是软件开发生命周期的一项重要活动,也是保证软件质量和可靠性的重要手段。测试用例是软件测试的核心和关键。而迄今为止,在测试领域,还没有统一的测试用例描述语言。虽然目前大量的测试工具引入了测试用例描述技术,但也是五花八门、各自为政,这成为提高软件测试的效率和软件测试复用程度的瓶颈。在对国内外的测试用例描述语言进行了广泛调研后,作了简要的总结。提出了设计测试用例描述语言的准则,同时阐述了测试用例描述技术在嵌入式软件测试领域的应用情况。     

软件测试领域的知识管理及模型研究*

软件测试组织中知识管理具有不同的特征,以建立测试知识共享场所为基础,对软件测试知识传递和积累进行分析,提出了一个面向软件测试过程的知识管理模型。该模型强调了将知识服务与软件测试活动紧密联系的思想,为软件测试领域知识管理技术研究提供了重要基础。基于该模型,给出了在QESuite2.0 项目中的应用情况。     

面向软件测试过程的知识管理方法的研究与实现

在软件测试组织中,对测试过程中的知识进行有效的管理,是提升组织整体测试水平的关键.一个重要的研究问题是怎样将知识管理过程与软件测试过程有效集成,从而促进知识资产在软件测试组织中的传播与重用.给出了软件测试领域知识管理子系统的体系结构、主要功能以及使用流程,对一些关键技术进行了探讨.最后,给出了知识地图模块的设计与实现,验证了本文所实现的软件测试领域知识管理系统的合理性和有效性.     

基于本体的软件测试知识管理模型研究

本文针对知识管理在软件测试领域的具体应用，提出了一个基于本体的软件测试知识管理模型，其关注的主要对象是软件测试过程中产生的具有高知识密集性的创造性文档。该模型的主要思想是：将软件测试知识分为个人知识和组织知识，并以本体索引的自由文本为软件测试知识的方式得以表示和组织，然后根据SWEBOK软件测试领域本体得到分类保存，最终目的是协助软件测试知识以“知识螺旋”的方式得以共享和重用。     

面向对象软件的测试方法研究

面向对象软件测试是保证面向对象软件开发项目质量的重要手段,而测试用例设计是实施面向对象软件测试的重要方面。从软件测试的技术出发,讨论了软件测试的技术特点,如何选择合适的测试方法,如何进行测试用例设计与工具选择,结合项目说明了测试实施和阶段划分。该领域的测试理论和技术还待完善,最终目的是克服软件测试的局限性,提高软件质量。     

软件测试不确定性研究及解决途径

从分析软件测试的不确定性产生的原因,分析软件测试中存在的问题,提出加强软件测试工程化管理、测试方法模板的复用、采用测试用例的知识共享作为解决问题的途径,介绍了一种软件测试管理平台的实现。     

可复用测试用例研究

软件测试是提高软件质量的关键步骤,测试用例的设计又是软件测试的核心,对已有的优秀的测试用例进行复用能够缩短软件测试的时间,该文对介绍了可复用测试用例的概念及设计思想,提出了可复用测试用例库的模型,提高了测试用例的复用程度。     

An initial industrial evaluation of interactive search-based testing for embedded software

Search-based software testing promises the ability to generate and evaluate large numbers of test cases at minimal cost. From an industrial perspective, this could enable an increase in product quality without a matching increase in the time and effort required to do so.Search-based software testing, however, is a set of quite complex techniques and approaches that do not immediately translate into a process for use with most companies.For example, even if engineers receive the proper education and training in these new approaches, it can be hard to develop a general fitness function that covers all contingencies. Furthermore, in industrial practice, the knowledge and experience of domain specialists are often key for effective testing and thus for the overall quality of the final software system. But it is not clear how such domain expertise can be utilized in a search-based system.This paper presents an interactive search-based software testing (ISBST) system designed to operate in an industrial setting and with the explicit aim of requiring only limited expertise in software testing. It uses SBST to search for test cases for an industrial software module, while also allowing domain specialists to use their experience and intuition to interactively guide the search.In addition to presenting the system, this paper reports on an evaluation of the system in a company developing a framework for embedded software controllers. A sequence of workshops provided regular feedback and validation for the design and improvement of the ISBST system. Once developed, the ISBST system was evaluated by four electrical and system engineers from the company (the ‘domain specialists’ in this context) used the system to develop test cases for a commonly used controller module. As well as evaluating the utility of the ISBST system, the study generated interaction data that were used in subsequent laboratory experimentation to validate the underlying search-based algorithm in the presence of realistic, but repeatable, interactions.The results validate the importance that automated software testing tools in general, and search-based tools, in particular, can leverage input from domain specialists while generating tests. Furthermore, the evaluation highlighted benefits of using such an approach to explore areas that the current testing practices do not cover or cover insufficiently.     

一种基于规范和程序域分析的软件测试方法

虽然软件规范规定了输入变量的定义域(功能域)，但程序实现本身也定义了其定义域(运行域)．如果二者不能完全重合，那么某些软件故障就可检测出来．为此，提出了一种基于规范和程序域分析的软件测试方法，介绍了一个运行域自动确定系统ADSOD，并讨论了边界测试数据的选取原则．对特殊表达式，采用程序切片技术，构造基于表达式的可执行模块，通过执行该模块，识别其输入变量的奇异值，进而确定其输入变量的取值范围．通过分析功能域和运行域的边界测试数据集，检测二者的重合性，并根据其分析结果产生测试用例．实验表明：所提方法产生的测试用例，可以有效地提高测试效率．     

一种基于约束的变异测试数据生成方法

作为衡量测试用例集完备性的测试策略,变异测试是一种“面向缺陷”的单元测试技术,主要用来生成完备的测试用例集.其中面向路径测试数据生成技术通过约束系统构造和求解过程实现用例集生成,是一种高效的测试用例生成技术.但目前大部分面向路径测试用例生成技术只考虑了程序语句间的控制依赖,即通过对控制流图的分析来构建约束系统,而忽略了语句间的数据依赖对约束系统的影响.充分考虑两种依赖关系,针对域削减的测试数据生成技术进行了改进,提出了一种考虑数据依赖的域削减方法.实验表明,这种方法在变异测试数据生成的成功率和执行效率上都有较大程度的提高.     

基于知识图谱的雷达软件测试用例复用研究

为了更加充分地利用雷达软件测试用例与其他测试知识的关系,进一步优化雷达软件测试用例复用效果,提出了一种基于知识图谱的雷达软件测试用例复用方法.该方法依据雷达软件测试本体关系模型,从现有的雷达软件测试管理系统中抽取测试知识构建雷达软件测试知识图谱,以实体特征属性文本的语义相似度匹配为基础,结合知识推荐和协同过滤推荐技术建...     

A formal analysis of the subsume relation between software testadequacy criteria

Software test adequacy criteria are rules to determine whether a software system has been adequately tested. A central question in the study of test adequacy criteria is how they relate to fault detecting ability. We identify two idealized software testing scenarios. In the first scenario, which we call prior testing scenario, software testers are provided with an adequacy criterion in addition to the software under test. The knowledge of the adequacy criterion is used to generate test cases. In the second scenario, which we call posterior testing scenario, software testers are not provided with the knowledge of adequacy criterion. The criterion is only used to decide when to stop the generation of test cases. In 1993, Frankl and Weyuker proved that the subsume relation between software test adequacy criteria does not guarantee better fault detecting ability in the prior testing scenario. We investigate the posterior testing scenario and prove that in this scenario the subsume relation does guarantee a better fault detecting ability. Two measures of fault detecting ability will be used, the probability of detecting faults and the expected number of exposed errors     

服务接口测试自动化工具的研究

在面向服务的架构中,软件功能通常被封装为服务,并以开放可编程接口的方式提供应用.因此,服务接口的正确性和可靠性对于服务理解、重用和集成至关重要.随着软件即服务的思想被广为认可,互联网上越来越多的软件应用以服务接口方式提供开放式访问.面对众多的服务接口,如何进行高效且有效的测试是一个亟待解决的问题.为此,提出了一种基于模型驱动的自动化测试方法,首先采用接口语义契约模型对被测服务接口建模,然后基于接口模型和测试覆盖率需求为单个服务和组合服务生成测试数据和测试用例.在此基础上,设计并实现了AutoTest自动化测试工具,该工具采用多种算法用于优化测试用例生成,且支持图形化测试计划编排和跨语言测试代码生成.实验结果表明,AutoTest能够有效支持大批量测试用例的设计和生成,根据OED(正交实验设计)算法生成的测试用例与IPO组合算法得到的用例相比,具有更为理想的测试覆盖率.     

GUI testing assisted by human knowledge: Random vs. functional

Software testing is a labor-intensive task in software development life-cycle. Human knowledge is useful in the practices of software testing, especially GUI testing. There are many strategies for GUI testing assisted by human knowledge, in which manual random testing and manual functional testing are two of widely used ones. In this paper, an empirical study is conducted to compare random testing and functional testing in order to provide guidelines for GUI testing. 234 participants were recruited to create thousands of random and functional test cases for open source GUI applications. Some of these test cases were selected with certain coverage criteria and then run on GUI applications to evaluate random testing and functional testing. We study three aspects on the two testing strategies: effectiveness, complementarity and impact of test case length. Some useful observations in the empirical study are: (1) Random testing is more effective in the early stage of testing on small applications and functional testing has more extensive applicability for testing large sized applications. (2) Random testing and functional testing exhibit some complementarity in our experiment. (3) Short test cases can reveal some faults more quickly and long test cases can reveal more faults lastingly.     

Graphical user interface (GUI) testing: Systematic mapping and repository

ContextGUI testing is system testing of a software that has a graphical-user interface (GUI) front-end. Because system testing entails that the entire software system, including the user interface, be tested as a whole, during GUI testing, test cases—modeled as sequences of user input events—are developed and executed on the software by exercising the GUI’s widgets (e.g., text boxes and clickable buttons). More than 230 articles have appeared in the area of GUI testing since 1991.ObjectiveIn this paper, we study this existing body of knowledge using a systematic mapping (SM).MethodThe SM is conducted using the guidelines proposed by Petersen et al. We pose three sets of research questions. We define selection and exclusion criteria. From the initial pool of 230 articles, published in years 1991–2011, our final pool consisted of 136 articles. We systematically develop a classification scheme and map the selected articles to this scheme.ResultsWe present two types of results. First, we report the demographics and bibliometrics trends in this domain, including: top-cited articles, active researchers, top venues, and active countries in this research area. Moreover, we derive the trends, for instance, in terms of types of articles, sources of information to derive test cases, types of evaluations used in articles, etc. Our second major result is a publicly-accessible repository that contains all our mapping data. We plan to update this repository on a regular basis, making it a “live” resource for all researchers.ConclusionOur SM provides an overview of existing GUI testing approaches and helps spot areas in the field that require more attention from the research community. For example, much work is needed to connect academic model-based techniques with commercially available tools. To this end, studies are needed to compare the state-of-the-art in GUI testing in academic techniques and industrial tools.