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

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

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

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

测试用例描述语言研究

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

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

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

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.     

Knowledge management initiatives in software testing: A mapping study

ContextSoftware testing is a knowledge intensive process, and, thus, Knowledge Management (KM) principles and techniques should be applied to manage software testing knowledge.ObjectiveThis study conducts a survey on existing research on KM initiatives in software testing, in order to identify the state of the art in the area as well as the future research. Aspects such as purposes, types of knowledge, technologies and research type are investigated.MethodThe mapping study was performed by searching seven electronic databases. We considered studies published until December 2013. The initial resulting set was comprised of 562 studies. From this set, a total of 13 studies were selected. For these 13, we performed snowballing and direct search to publications of researchers and research groups that accomplished these studies.ResultsFrom the mapping study, we identified 15 studies addressing KM initiatives in software testing that have been reviewed in order to extract relevant information on a set of research questions.ConclusionsAlthough only a few studies were found that addressed KM initiatives in software testing, the mapping shows an increasing interest in the topic in the recent years. Reuse of test cases is the perspective that has received more attention. From the KM point of view, most of the studies discuss aspects related to providing automated support for managing testing knowledge by means of a KM system. Moreover, as a main conclusion, the results show that KM is pointed out as an important strategy for increasing test effectiveness, as well as for improving the selection and application of suited techniques, methods and test cases. On the other hand, inadequacy of existing KM systems appears as the most cited problem related to applying KM in software testing.     

嵌入式软件自动化测试及管理系统研究

随着嵌入式软件技术的发展,嵌入式软件规模日益扩大、复杂程度越来越高,给软件测试提出了挑战。针对复杂嵌入式软件,设计一种软件自动化测试及管理系统,融入软件工程化管理过程,将自动化测试与测试管理过程相结合,打造一个无缝连接的系统。自动化测试及管理系统包括：接口设计、测试策划、测试设计、测试执行、测试结果显示与记录、缺陷管理和回归测试,以及数据分析和知识库等。在此基础上,设计并实现了自动化测试及管理系统,并在某测试项目中进行了应用。实践证明,使用自动化测试及管理系统开展嵌入式软件测试可以有效提高测试效率和质量。     

基于软件、测试、缺陷“三域”铰链的 软件测试新架构研究与应用

为推动软件测试更加精准深入高效,促进软件测试从“遍历式”向“启发式”转变,提出了一种新型的基于软件、缺陷、测试“三域”铰链的关联知识启发式的新型软件测试架构。通过信息表征模型化、缺陷数据知识化、测试投向精准化等,突破了软件测试数据聚类重组技术和软件典型缺陷模式提取技术,设计开发了相应的软件测试信息管理系统,实现软件精准化测试。在提高软件测试效益的同时,也为软件研制单位和使用单位提高研发质量、快速诊断排故等提供更具针对性的数据服务。