基于众测操作记录的GUI软件测试用例生成

众包测试是一种新兴的软件测试模式,具有测试周期短、测试成本低的优点.但是在众包测试中也存在测试人员水平不一、无法形成规范化测试用例的问题.文章提出一种基于操作记录的GUI软件测试用例生成方法,该方法将测试人员操作记录转化为规范化测试用例.实验结果表明,相对于手工测试生成的测试用例,该方法生成的测试用例在缺陷检测方面有显...     

基于遗传算法的测试用例生成技术

在计算机软件的生命周期中,由于各种各样的原因,留给软件测试的时间往往不够执行全面而充分的测试。覆盖率和数量作为测试用例质量的主要影响因子,一直受到人们的关注。然而测试用例的执行顺序作为影响测试效率的重要因素,却一直未引起足够的重视。提出了一种基于遗传算法的测试用例生成技术,综合考虑覆盖率、数量和用例的执行顺序三个因子,生成高效的测试用例集。使测试人员能够按照既定的顺序执行用例集,在最短的时间内,完成最重要的软件功能测试。     

基于UML面向对象软件静态测试方法的研究

文章提出了一种基于UML面向对象软件静态测试的方法,论述了方法的基本框架及具体实现流程。针对面向对象软件的特点,静态测试主要是通过分析源程序得到类关系图,使测试人员能快速而清晰地了解程序结构,有效的设计测试用例。     

基于形式化描述可复用测试用例库的研究与实现

软件测试作为保证软件质量的重要手段,是软件开发过程中的重要环节。软件测试过程中产生的大量测试用例对保证软件的质量起到了关键作用。为了共享和复用测试用例,提出了基于形式化语言描述的可复用测试用例库的构建方法,收集大量测试用例,并进行合理的分类和管理,测试人员可以从库中选择合适的测试用例直接使用或稍作修改来使用,从而大幅度降低了测试人员的工作量,极大地提高了测试工作效率,进而更好地保证软件质量。     

基于任务分析的交互式系统用户界面测试研究

交互式系统的用户界面测试很难预测用户的输入,将人机交互领域的任务分析理论应用于交互式系统的用户界面测试,提出了测试用例图形化及测试用例聚焦用户任务的新观点。由于在线帮助是用户界面重要的一部分,在线帮助的测试往往被测试人员忽视,其测试方法也比较陈旧,然而任务分析理论提供了一种有效的方法帮助测试人员保证在线帮助是面向用户任务的,而不是仅仅是软件功能的描述。     

一种针对交互式软件的测试用例生成技术

对于交互式软件而言,功能的实现是通过复杂的人机交互完成的,目前的功能测试用例生成方法常常只考虑软件的界面信息,而不考虑软件的具体需求和逻辑实现流程,这就导致产生的测试用例随意性较大,测试过程难以有序进行,为此,本文将软件功能的逻辑实现流程和界面信息结合在一起考虑,提出一种基于数据流图的测试用例生成方法,以业务处理中数据的漉向来描述业务流程,生成测试用例.该方法能够生成有效的测试用例,更全面地测试交互式软件功能,并便于定位错误.     

基于本体和规则推理的GUI软件测试用例生成*

为了提高GUI软件测试用例的生成效率和可维护性,提出了一种基于本体和规则推理的GUI软件测试用例生成方法。首先建立一个通用的GUI软件测试用例本体模型,通过对其继承和实例化可获得具体被测软件的测试用例本体模型,同时开发反映测试数据生成和测试路径生成的测试用例生成规则。最后将基于OWL的测试用例本体和基于SWRL的测试用例生成规则导入Jess推理引擎,通过推理得到符合测试需求的、易于维护的测试用例子集。在核电站堆芯换料管理系统上的应用,验证了该方法的有效性。     

基于路径引导的回归测试用例集扩增方法

为了全面测试演化软件,回归测试通常需要生成新的测试用例。concolic测试是一种沿着具体执行路径进行符号执行的软件验证技术,通过生成测试数据来执行程序的所有可行路径。回归测试中,由于concolic测试关注于程序本身,没有利用已有测试用例和软件演化信息,导致生成大量无效测试数据,浪费资源和时间。为解决此问题,提出一种基于路径引导的回归测试用例集扩增方法。该方法将目标路径作为引导,根据软件演化信息选择有利于覆盖目标路径的测试用例,利用已有测试用例跳过重叠初始子路径,对后续目标子路径进行concolic测试并生成覆盖目标路径的测试数据。案例分析表明,本文方法相比传统concolic测试,本方法在覆盖程序可行路径的同时,可有效减少concolic测试路径,提高测试数据生成效率。     

用模型检验产生约简测试集

基于模型检验的自动化测试技术已经得到普遍应用,由于测试用例自动化生成过程中会产生巨大的资源消耗,优化问题越来越受到软件测试行业的广泛关注。提出一种基于节点权重的性质覆盖度计算方法,在模型检验器自动化生成测试用例之前对测试目标排序,能够更有效地检测到冗余性质,从而减少模型检验器被调用执行次数并且避免大规模的测试用例生成。     

用于GUI软件的测试工具

为提高GUI软件测试的效率、降低软件成本,提出一种针对GUI软件的测试工具.该工具由测试配置设定模块、测试用例设计模块和测试用例执行模块组成.首先根据测试需求进行测试配置设定生成INI文件,然后根据INI文件内容将测试对象窗体中需要测试的控件及属性设定到测试用例设计界面中,在界面中进行测试用例设计,并将设计数据保存到XML文件中,测试用例执行模块通过读取XML文件中的数据完成测试用例的自动执行,同时进行测试结果判断,最后生成测试报告.测试人员只需输入数据,不用编写测试脚就能实现测试用例的自动执行,能减轻测试人员负担,提高软件测试效率.     

一个划算的回归测试用例排序的成本-收益模型

回归测试是一个昂贵的测试过程,它验证修改的软件,确认是否给已经测试的代码引进了新的错误.因为在软件开发的过程中,测试人员给测试包中增加了新的测试用例,使软件确认更加困难.为了使回归测试更经济划算,提出了很多技术和方法.测试用例选择,测试包缩减,测试用例排序可以帮助我们减少需要运行的测试用例数目,同时能够更快地满足测试目标.测试用例排序是在满足某个性能目标的基础上,保证在测试过程中首先执行更重要的功能.以前的研究提出了一个性能目标:缺陷发现率(APFD),以及很多改善缺陷发现率的技术.但是这些技术运用起来非常昂贵,而且可能不会减少回归测试的成本.在以往研究的基础上,提出了一个成本-收益模型,为比较各种排序算法提供了一定依据.并在此基础上,提供了一个测试用例排序算法.     

Should software testers use mutation analysis to augment a test set?

Mutation testing has historically been used to assess the fault-finding effectiveness of a test suite or other verification technique. Mutation analysis, rather, entails augmenting a test suite to detect all killable mutants. Concerns about the time efficiency of mutation analysis may prohibit its widespread, practical use. The goal of our research is to assess the effectiveness of the mutation analysis process when used by software testers to augment a test suite to obtain higher statement coverage scores. We conducted two empirical studies and have shown that mutation analysis can be used by software testers to effectively produce new test cases and to improve statement coverage scores in a feasible amount of time. Additionally, we find that our user study participants view mutation analysis as an effective but relatively expensive technique for writing new test cases. Finally, we have shown that the choice of mutation tool and operator set can play an important role in determining how efficient mutation analysis is for producing new test cases.     

Performance appraisal of software testers

ContextTo determine the effectiveness of software testers a suitable performance appraisal approach is necessary, both for research and practice purposes. However, review of relevant literature reveals little information of how software testers are appraised in practice.Objective(i) To enhance our knowledge of industry practice of performance appraisal of software testers and (ii) to collect feedback from project managers on a proposed performance appraisal form for software testers.MethodA web-based survey with questionnaire was used to collect responses. Participants were recruited using cluster and snowball sampling. 18 software development project managers participated.ResultsWe found two broad trends in performance appraisal of software testers – same employee appraisal process for all employees and a specialized performance appraisal method for software testers. Detailed opinions were collected and analyzed on how performance of software testers should be appraised. Our proposed appraisal approach was generally well-received.ConclusionFactors such as number of bugs found after delivery and efficiency of executing test cases were considered important in appraising software testers’ performance. Our proposed approach was refined based on the feedback received.     

一种分布式可持续集成自动化测试平台

软件开发过程中,随着逻辑复杂度的不断增加,专门的测试可以有效地减少软件的bug,提高软件的质量,然而传统的人工测试已经不能满足当前软件开发的需求。为此,提出一种分布式可持续集成的自动化测试平台,基于Jenkins平台实现分布式可持续集成,选用Git作为版本管理工具,使用Katalon作为自动化测试工具。平台实现对Web软件每日自动更新并持续集成自动化测试,该平台在Web软件测试中大大地减少了测试人员重复回归测试的工作量。     

软件自动化测试中热点路径的研究

在面向路径的软件测试中,对于大型系统将会产生海量的静态路径,测试人员很难对所有路径进行完全测试。本文提出热点路径的思想,运用该思想可以在繁多的静态路径中迅速找到容易引起程序缺陷的路径,通过热点函数树形化可以对热点进行快速定位显示,给软件测试人员带来更多的便捷,提高测试效率,降低测试成本。     

Automated test generation using model checking: an industrial evaluation

In software development, testers often focus on functional testing to validate implemented programs against their specifications. In safety-critical software development, testers are also required to show that tests exercise, or cover, the structure and logic of the implementation. To achieve different types of logic coverage, various program artifacts such as decisions and conditions are required to be exercised during testing. Use of model checking for structural test generation has been proposed by several researchers. The limited application to models used in practice and the state space explosion can, however, impact model checking and hence the process of deriving tests for logic coverage. Thus, there is a need to validate these approaches against relevant industrial systems such that more knowledge is built on how to efficiently use them in practice. In this paper, we present a tool-supported approach to handle software written in the Function Block Diagram language such that logic coverage criteria can be formalized and used by a model checker to automatically generate tests. To this end, we conducted a study based on industrial use-case scenarios from Bombardier Transportation AB, showing how our toolbox CompleteTest can be applied to generate tests in software systems used in the safety-critical domain. To evaluate the approach, we applied the toolbox to 157 programs and found that it is efficient in terms of time required to generate tests that satisfy logic coverage and scales well for most of the programs.     

One World,Two Realities: Perception Differences between Software Developers and Testers

Strong working relations between software developers and testers are critical to the efficient and effective development of high-quality software. Smooth collaboration must occur as testers find problems and developers fix problems in the software. Prior studies based on anecdotal data have suggested that developers and testers have different personalities, approaches to work, etc., and these differences may have negative impacts on software project outcomes such as software quality and job satisfaction. This study examines the results of a nationwide survey undertaken to empirically examine and to improve our understanding of the pertinent areas where developers and testers differ. Results support that significant differences exist in perceptions between developers and testers. We conclude that these differences must be considered in order to improve software development efficiency and effectiveness.     

Risk-based test case prioritization using a fuzzy expert system

Context: The use of system requirements and their risks enables software testers to identify more important test cases that can reveal the faults associated with system components.Objective: The goal of this research is to make the requirements risk estimation process more systematic and precise by reducing subjectivity using a fuzzy expert system. Further, we provide empirical results that show that our proposed approach can improve the effectiveness of test case prioritization.Method: In this research, we used requirements modification status, complexity, security, and size of the software requirements as risk indicators and employed a fuzzy expert system to estimate the requirements risks. Further, we employed a semi-automated process to gather the required data for our approach and to make the risk estimation process less subjective.Results: The results of our study indicated that the prioritized tests based on our new approach can detect faults early, and also the approach can be effective at finding more faults earlier in the high-risk system components compared to the control techniques.Conclusion: We proposed an enhanced risk-based test case prioritization approach that estimates requirements risks systematically with a fuzzy expert system. With the proposed approach, testers can detect more faults earlier than with other control techniques. Further, the proposed semi-automated, systematic approach can easily be applied to industrial applications and can help improve regression testing effectiveness.     

Stochastic software testing

This paper presents a method for test case selection that allows a formal approach to testing software. The two main ideas are (1) that testers create stochastic models of software behavior instead of crafting individual test cases and (2) that specific test cases are generated from the stochastic models and applied to the software under test. This paper describes a method for creating a stochastic model in the context of a solved example. We concentrate on Markov models and show how non‐Markovian behavior can be embedded in such models without violating the Markov property.     

R2P: An open source hardware and software modular approach to robot prototyping

Rapid prototyping is a key aspect for the development of innovative robotic applications. A modular, platform-based, approach is the way to obtain this result. Modular approaches are common for software development, but hardware is still crafted often re-inventing solutions every time. As a consequence, the resources that should be invested in the development of a new robot get often drained by the implementation of a physical, working prototype to test the application idea. To overcome this problem, we propose R2P (Rapid Robot Prototyping), a framework to implement real-time, high-quality architectures for robotic systems with off-the-shelf basic modules (e.g., sensors, actuators, and controllers), integrating hardware and software, which can be assembled in a plug-and-play way. R2P provides hardware modules, a protocol for real-time communication, a middleware to connect components as well as tools to support the development of software on the modules. R2P aims at dramatically reduce time and efforts required to build a prototype robot, making it possible to focus the resources on the development of new robotic applications instead of struggling on their implementation. This enables also people with experience in a specific application domain, but with little technical background, to actively participate in the development of new robotic applications. R2P is open-source both in its software and hardware to promote its diffusion among the robotics community and novel business models that will substantially reduce the costs to design a new robotic product.