动态故障树分析方法在测试用例设计中的应用探讨

本文主要针对动态故障树分析方法在测试用例设计中的应用问题进行了分析,初步探讨了基于软件故障信息的测试用例设计流程,对动态故障树分析方法进行了讨论,最后提出了基于动态故障树的测试用例设计步骤,希望对于今后的软件测试工作具有一定帮助。     

测试用例的设计和复用技术

软件测试是企业保证软件产品质量的一个重要手段,其中测试用例的设计是软件测试的关键,它一般包括功能测试用例的设计,结构测试用例设计以及系统方面的测试用例设计等.结合实际经验,系统地阐述了如何有效地进行测试用例的设计以及复用.并给出两个案例进行分析,探讨测试用例设计中的一些注意事项.     

软件测试中的测试用例及复用研究

软件测试过程中产生的大量测试用例对保证软件的质量起到关键作用,对于专门从事软件测试的机构来说,测试用例的复用尤其重要。在测试用例的设计、选择的基础上,构造出基于复用的测试用例,同时采用测试用例库管理的方法来实现测试用例的复用,可以提高软件测试的工作效率。     

软件测试中的测试用例及复用研究

软件测试过程中产生的大量测试用例对保证软件的质量起到关键作用，对于专门从事软件测试的机构来说，测试用例的复用尤其重要。在测试用例的设计、选择的基础上，构造出基于复用的测试用例，同时采用测试用例库管理的方法来实现测试用例的复用，可以提高软件测试的工作效率。     

软件测试中测试用例设计的问题研究

软件测试作为软件质量的保证,受到了IT行业的高度重视。测试用例的设计是软件测试的主要内容。重点分析了测试用例的优点和不足,建议针对不同的软件项目采取不同的测试用例设计方法。     

基于二叉树满足MC/DC测试用例设计方法

软件测试是保证软件质量的有效方法,但测试工作过程繁琐,工作量较多。探索高效、可靠的测试用例设计方法一直是大家追求的目标,随着航空航天产品逻辑复杂性的提高及软件规模的日益增大,这种要求也变得更加迫切。依据MC/DC设计的测试用例既提高了测试用例设计的效率又增加了测试覆盖率,比较适合测试逻辑关系相对复杂的软件。当前的很多软件测试工具提供了软件测试覆盖率的判定功能,可以评定设计出的测试用例是否满足MC/DC的要求,而软件测试人员需要的是逆向的过程,论文提出应用唯一原因法和屏蔽法原理设计测试用例,可达到根据逻辑关系自动生成满足MC/DC要求测试用例的目的,提高了测试用例设计的效率。     

用于GUI软件的测试工具

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

一种基于大数定律的软件测试方法

随着软件规模越来越大,复杂程度越来越高,软件测试也变得越来越复杂.由于人力、经费、时间等测试资源有限,穷尽测试显然是不划算的.故需要从数量众多的可能测试数据中精心挑选出尽量少的测试数据来设计测试用例,通过这样设计的测试用例可以高效地把隐藏在软件中的错误、缺陷检测出来.文中根据历史数据和以往的经验,利用统计学中的大数定律提出了设计测试用例的"测试用例优先值向量法".该方法的思想是当软件开发的资源、技术条件、开发过程管理等影响软件质量的因素相同时,软件产品中的各种缺陷、错误发生的概率也是基本一定的,因此,可以根据历史数据来推断出各类错误的分布情况,并由此来设计测试用例.该方法具有客观性、高效性和可复用等特点,在软件测试过程中可以节省大量的资源,提高软件测试的效率.     

并发软件适应性随机测试方法

测试用例选择是软件测试中的关键问题之一.目前,测试用例选择在并发软件测试方面鲜有涉及.以多线程并发程序为研究对象,提出面向并发软件的适应性随机测试方法,通过优化测试用例选择,来提高并发软件测试的效率和错误发现能力.根据实验结果,我们提出的并发软件适应性随机测试方法比随机测试方法的测试效率更高,错误发现能力也更强.     

基于UML的测试用例生成方法研究

基于模型的软件测试是由软件需求分析模型与设计模型中生成一套测试用例的技术.随着基于UML模型的软件开发与RUP(Rational Unified Process)开发过程的广泛应用,基于UML模型的软件测试逐渐成为基于模型软件测试的主要研究方向.结合UML模型中的测试信息,结合并改进了传统的测试用例生成方法,如场景法、判定表法等,提出了一套较合理的基于UML的测试用例生成方法,使得基于UML的测试用例生成方法的流程更加规范,更加易于生成满足很高覆盖要求的测试用例,并运用实例对其进行了验证.     

软件测试用例设计

软件测试重要性越来越大,测试用例的设计是整个测试过程的基础。结合工作实践介绍软件测试用例的重要性和测试用例的设计方法,并举例说明如何应用白盒测试技术和黑盒测试技术。     

A practical model‐based statistical approach for generating functional test cases: application in the automotive industry

With the growing complexity of industrial software applications, industrials are looking for efficient and practical methods to validate the software. This paper develops a model‐based statistical testing approach that automatically generates online and offline test cases for embedded software. It discusses an integrated framework that combines solutions for three major software testing research questions: (i) how to select test inputs; (ii) how to predict the expected results of a test; and (iii) when to stop testing software. The automatic selection of test inputs is based on a stochastic test model that accounts for the main particularity of embedded software: time sensitivity. Software test practitioners may design one or more test models when they generate random, user‐oriented, or fault‐oriented test inputs. A formal framework integrating existing and appropriate specification techniques was developed for the design of automated test oracles (executable software specifications) and the formal measurement of functional coverage. The decision to stop testing software is based on both test coverage objectives and cost constraints. This approach was tested on two representative case studies from the automotive industry. The experiment was performed at unit testing level in a simulated environment on a host personal computer (automatic test execution). The two software functionalities tested had previously been unit tested and validated using the test design approach conventionally used in the industry. Applying the proposed model‐based statistical testing approach to these two case studies, we obtained significant improvements in performing functional unit testing in a real and complex industrial context: more bugs were detected earlier and in a shorter time. Copyright © 2012 John Wiley & Sons, Ltd.     

基于多优化目标的软件测试用例约简方法研究

软件测试是软件工程的一个重要组成部分,其目标是能够及时发现软件中的错误,确保软件高质量。测试用例是软件测试的基础,覆盖度较高且精简的测试用例集可以提高测试效率和降低成本。软件测试覆盖标准较多,一个好的测试用例评价指标也存在多种,为了能够在约简测试用例集规模的同时获取较高的测试能力,本文提出了一种基于多优化目标的测试用例集约简算法,该算法旨在根据测试用例需求,构建多优化目标的测试用例模型,使用该模型获取一个最优解的测试用例子集,使用最小化用例集方法最小化测试用例,迭代执行直到测试用例集覆盖所有的测试需求,实验结果表明该算法可以约简测试用例集,获取较高的综合测试效果。     

USB接口软件自动化测试实现

随着软件技术的发展,手工测试已不能满足软件测试的要求,软件测试自动化是软件测试的发展趋势。结合USB接口软件功能测试的特点,对其进行了自动化测试需求分析;确定了自动化测试的范围;在Microsoft Visual Studio.net平台下,基于组件开发的思想,用C#语言开发了USB接口软件自动化测试系统。并经过测试实践,验证了该自动化测试系统的可靠性。通过对手工测试和自动化测试的对比,展示了该系统的优越性。     

Factor oriented requirement coverage based system test case prioritization of new and regression test cases

Test case prioritization involves scheduling test cases in an order that increases the effectiveness in achieving some performance goals. One of the most important performance goals is the rate of fault detection. Test cases should run in an order that increases the possibility of fault detection and also that detects the most severe faults at the earliest in its testing life cycle. In this paper, we propose to put forth a model for system level test case prioritization (TCP) from software requirement specification to improve user satisfaction with quality software that can also be cost effective and to improve the rate of severe fault detection. The proposed model prioritizes the system test cases based on the six factors: customer priority, changes in requirement, implementation complexity, completeness, traceability and fault impact. The proposed prioritization technique is validated with two different validation techniques and is experimented in three phases with student projects and two sets of industrial projects and the results show convincingly that the proposed prioritization technique improves the rate of severe fault detection.     

软件内建自测试中模板内容的研究和实现

软件内建自测试是软件测试和可测性设计研究领域中的一个新概念,其思想来源于硬件内建自测试BIST(BuildinSelfTest)。软件内建自测试为程序员提供一套预先设计好的模板,由模板对所编写的程序植入测试信息,实现软件内建自测试以解决软件测试难的问题。模板是软件内建自测试系统的基石,其内容关系到整个系统的性能和效果。具体讨论了模板的实现,根据软件故障模型对代码进行改装,从而减少程序出错的概率,同时为软件内建自测试系统中测试用例的生成提供了更丰富的信息。     

On the Use of Mutation Faults in Empirical Assessments of Test Case Prioritization Techniques

Regression testing is an important activity in the software life cycle, but it can also be very expensive. To reduce the cost of regression testing, software testers may prioritize their test cases so that those which are more important, by some measure, are run earlier in the regression testing process. One potential goal of test case prioritization techniques is to increase a test suite's rate of fault detection (how quickly, in a run of its test cases, that test suite can detect faults). Previous work has shown that prioritization can improve a test suite's rate of fault detection, but the assessment of prioritization techniques has been limited primarily to hand-seeded faults, largely due to the belief that such faults are more realistic than automatically generated (mutation) faults. A recent empirical study, however, suggests that mutation faults can be representative of real faults and that the use of hand-seeded faults can be problematic for the validity of empirical results focusing on fault detection. We have therefore designed and performed two controlled experiments assessing the ability of prioritization techniques to improve the rate of fault detection of test case prioritization techniques, measured relative to mutation faults. Our results show that prioritization can be effective relative to the faults considered, and they expose ways in which that effectiveness can vary with characteristics of faults and test suites. More importantly, a comparison of our results with those collected using hand-seeded faults reveals several implications for researchers performing empirical studies of test case prioritization techniques in particular and testing techniques in general     

GUI测试中多级形态模型的分割与应用

基于模型的GUI测试方法(MBGT)可自动化生成测试用例,在MBGT中引入多级形态模型(Multilevel Morphology Model,MMM)可以实现从不同的形态角度考察系统,可控地提高模型的错误检测效力。但多级形态模型只能整体扩展到高阶,且随着模型的扩展,测试用例的长度与数量急剧增长,极大地影响了测试效率。对此提出一种可进行局部扩展的多级形态模型的分割方法以及相应的测试用例生成策略。该方法通过GUI事件的分类,实现了对基础模型的分割与化简,并采用广度优先搜索(BFS)与中国邮递员问题(CPP)求解算法生成测试用例。该方法使得GUI模型的表达更为清晰直观,在有效区分测试重点的同时,缩小了测试集规模,极大地提高了多级形态模型在GUI测试中的灵活性与测试效率。实验证明,经模型分割后的多级形态模型具有与未分割模型基本等同的错误检测效力,且随着模型级数的提高,模型分割对测试效率的提升增大。     

Empirical evaluations on the cost-effectiveness of state-based testing: An industrial case study

ContextTest models describe the expected behavior of the software under test and provide the basis for test case and oracle generation. When test models are expressed as UML state machines, this is typically referred to as state-based testing (SBT). Despite the importance of being systematic while testing, all testing activities are limited by resource constraints. Thus, reducing the cost of testing while ensuring sufficient fault detection is a common goal in software development. No rigorous industrial case studies of SBT have yet been published.ObjectiveIn this paper, we evaluate the cost-effectiveness of SBT on actual control software by studying the combined influence of four testing aspects: coverage criterion, test oracle, test model and unspecified behavior (sneak paths).MethodAn industrial case study was used to investigate the cost-effectiveness of SBT. To enable the evaluation of SBT techniques, a model-based testing tool was configured and used to automatically generate test suites. The test suites were evaluated using 26 real faults collected in a field study.ResultsResults show that the more detailed and rigorous the test model and oracle, the higher the fault-detection ability of SBT. A less precise oracle achieved 67% fault detection, but the overall cost reduction of 13% was not enough to make the loss an acceptable trade-off. Removing details from the test model significantly reduced the cost by 85%. Interestingly, only a 24–37% reduction in fault detection was observed. Testing for sneak paths killed the remaining eleven mutants that could not be killed by the conformance test strategies.ConclusionsEach of the studied testing aspects influences cost-effectiveness and must be carefully considered in context when selecting strategies. Regardless of these choices, sneak-path testing is a necessary step in SBT since sneak paths are common while also undetectable by conformance testing.