基于XML的通用测试文档生成方法研究

针对目前软件测试过程中通用文档自动生成所面临的问题,介绍了一种基于XML的通用测试文档生成方法.分析了软件测试文档的基本种类及文档生成的重要性,论述了将XML技术用于通用文档生成中的优势,给出了一个基于XML的通用测试文档生成模型,并探讨了该模型的关键方案设计.     

基于XML的测试流程模板定义和存储方法

通过研究传统的测试模型以及WfMC规范,依据H模型提出了一个5阶段测试模型,并基于XML技术提出了一种新的软件测试流程模板的定义及存储方法.该方法既可以存储流程的数据信息,还可以表现出测试流程与流程包含的测试阶段和测试活动之间的逻辑关系.将该方法应用到QESuite2.0项目中,主要用于测试阶段与活动的分离,以及于系统结构的分离,收到了很好的效果,最后给出了在项目中的实现示例.     

软件测试管理及其工程应用

在分析软件测试模型和软件测试流程的基础上，总结测试管理原则，并将其应用于工程实践中。     

基于能力成熟度模型的软件测试改进

当前软件企业面临着用户需求日益复杂、软件产品架构日益扩大等问题。这些问题向软件测试提出了更高的要求。该文对传统测试模型进行了介绍和分析。基于以上工作,以CMMI的标准为指导对软件测试流程以及测试模型的改进提出了思路和方法。     

一种有效的软件测试模型

软件测试是软件质量保证的一个重要元素。在测试过程中使用合理的软件测试模型可以降低测试在开发活动中的花费。该文提出了一个软件测试模型。该模型将软件测试贯穿软件开发周期的各个阶段,可以尽可能早地发现软件中的错误,有效地缩短了测试在软件开发过程中所占的时间。最后给出该测试模型在报表生成软件升级开发项目中的应用。     

一种软件可靠性的随机测试模型研究

本文提出一种基于随机测试模型的软件可靠性测试方法、评判准则和测试策略,并利用蒙特卡罗方法进行了分析。通过实例证明了该模型在软件测试中的实用性和有效性,使用该模型可以提高软件测试的准确性和正确率、缩短软件测试的周期。     

面向对象软件闭环测试模型探讨

参考传统软件测试模型,根据面向对象软件设计过程,结合软件测试建立了一种面向对象闭环软件测试模型。依照该测试模型,提出各测试阶段面向对象软件测试的内容、测试方法和测试技术,并对基于闭环模型的测试实施进行了讨论,为面向对象软件测试研究探索了一条新的途径。     

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

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

软件测试过程模型的研究与应用

软件测试管理在软件测试过程中起着重要的作用。文章在分析了软件测试过程的三个模型的优缺点后,参考W模型和H模型的特点,提出适合实际软件项目的测试管理模型,它能够在软件开发的同时同步完成相应的测试,支持软件的迭代开发,简化了缺陷跟踪流程。该模型在实际应用中取得了良好效果。     

有效测试模型的研究与应用

软件测试是保证软件质量的一个重要因素，软件测试直接关系整个软件的成败。本文在分析目前流行的几种软件测试模型的基础上，提出了一种改进模型。该模型将软件测试和软件开发紧密地结合在一起，使bug尽可能早地被发现，提高了软件的开发效率，保证了软件质量。最后给出了该模型的一个具体应用实例。     

A mathematical modeling framework for software reliability testing†

Software reliability testing refers to various software testing activities that are driven to achieve a quantitative reliability goal given a priori or lead to a quantitative reliability assessment for the software under test. In this paper we develop a modeling framework for the software reliability testing process, comprising a simplifying model and a generalized model. In both models the software testing action selection process and the defect removal mechanism are explicitly described. Both the discrete-time domain and the continuous-time domain are involved. The generalized model is more accurate or realistic than the simplifying model since the former avoids the assumption that defects are equally detectable and the assumption that defects are removed upon being detected. However simulation examples show that the simplifying model really captures some of essential features of the software testing process after a short initial testing stage. The modeling framework is practically realistic, mathematically rigorous, and quantitatively precise. It demonstrates that the relationship between software testing and delivered software reliability, which was poor understood, can well be formulated and quantified. Rigorous examinations show that several common assumptions adopted in software reliability modeling, including the independence assumption, the exponentiality assumption, and the NHPP assumption, are theoretically false in general. This paper sets a good starting point to further formalize and quantify the software testing process and its relation to delivered software reliability.     

Investigating software testing and maintenance reports: Case study

ContextAlthough many papers have been published on software development and defect prediction techniques, problem reports in real projects quite often differ from those described in the literature. Hence, there is still a need for deeper exploration of case studies from industry.ObjectiveThe aim of this study is to present the impact of fine-grained problem reports on improving evaluation of testing and maintenance processes. It is targeted at projects involving several releases and complex schemes of problem handling. This is based on our experience gained while monitoring several commercial projects.MethodExtracting certain features from detailed problem reports, we derive various measures and present analysis models which characterize and visualize the effectiveness of testing and problem resolution processes. The considered reports describe types of problems (e.g. defects), their locations in project versions and software modules, ways of their resolution, etc. The performed analysis is related to eleven projects developed in the same company. This study is an exploratory research with some explanatory features. Moreover, having identified some drawbacks, we present extensions of problem reports and their analysis which have been verified in another industrial case study project.ResultsFine-grained (accurate) problem handling reports provide a wider scope of possible measures to assess the relevant development processes. This is helpful in controlling single projects (local perspective) as well as in managing these processes in the whole company (global perspective).ConclusionDetailed problem handling reports extend the space and quality of statistical analysis, they provide significant enhancement in evaluation and refinement of software development processes as well as in reliability prediction.     

基于行为的软件测试过程模型及其应用研究

在深入研究各种综合测试技术的基础上,通过对比分析各种主流的测试模型,提出了一种基于行为的软件测试过程模型,包括了测试设计、测试计划、测试执行、测试结果分析和测试重用等活动,把这些测试活动嵌入到软件开发的整个生命周期当中。然后将这种测试模型应用到一个大型的应用程序测试项目(AMP)中,发现这种测试模型在尽早发现Bug和回归测试选择效率上具有较好的测试效果。     

基于覆盖的软件测试技术在实时嵌入式软件中的应用研究

基于覆盖软件测试技术在实时嵌入式软件中的应用进行的研究，针对实时嵌入式软件测试的特点，文中提出了一个适用于实时嵌入式系统覆盖测试的软件测试模型。并对该模型实现中的核心技术进行了阐明。最后介绍了以上软件测试技术在实际工程项目的应用情况。     

嵌入式实时系统软件测试实践

软件质量是软件的生命,软件测试是保证软件产品质量的重要手段。本文从嵌入式系统的特点出发,阐述了嵌入式系统软件测试的实现方法。并结合某无线通信电台软件测试的实例,详细叙述了如何利用Testbed和RTInsight搭建嵌入式实时系统的软件测试平台,说明了在此平台上进行软件覆盖率测试和性能分析的全过程,同时给出了部分测试结果。     

嵌入式实时系统软件测试实践

软件质量是软件的生命,软件测试是保证软件产品质量的重要手段。本文从嵌入式系统的特点出发,阐述了嵌入式系统软件测试的实现方法。并结合某无线通信电台软件测试的实例,详细叙述了如何利用Testbed和RTInsight搭建嵌入式实时系统的软件测试平台,说明了在此平台上进行软件覆盖率测试和性能分析的全过程,同时给出了部分测试结果。     

基于评价软件测试的有效性问题研究

随着软件产业的迅猛发展,软件产品的规模越来越大,复杂度越来越高,但是软件产品质量却变得越来越难以控制。在软件测试过程中,因为多方面的因素,常常会导致一些错误和失效,为了改善测试过程、使测试过程变得更为有效,需要对软件测试过程进行一个补充,那就是对软件测试的有效性进行评价。本文介绍了评价软件测试有效性工作的一般流程,并提出了一系列用于精确度量测试有效性的度量指标。     

软件测试管理的研究与应用

随着计算机的广泛应用和计算机科学技术的不断发展，计算机系统的组成也相应发生了许多变化，计算机软件的主导作用愈加明显。软件工程的进一步发展，给软件测试及测试管理带来很大帮助。本文简要介绍了软件测试管理的概念、计划、活动、功能、周期、工作量模型及其应用。     

基于场景的软件测试工具系列的设计与实现

文章将场景技术用于软件测试工具系列Safepro的开发,在讨论测试工具开发共性的基础上,还兼顾个别测试工具的一些特别之处。文中简要介绍了软件测试工具的研究现状,随后给出了系统的测试场景,并基于场景分析了系统的构成模式,讨论了测试数据流模型,包括测试过程的数据流模型,数据流的性能改进,以及基于消息的数据分发和缓冲计数的应用。文章还介绍了采用Makefile规则实现测试分析过程组织的方法。     

The Economics of Unit Testing

Conventional wisdom and anecdote suggests that testing takes between 30 to 50% of a project's effort. However testing is not a monolithic activity as it consists of a number of different phases such as unit testing, integration testing and finally system and acceptance test. Unit testing has received a lot of criticism in terms of the amount of time that it is perceived to take and its perceived costs. However it still remains an important verification activity being an effective means to test individual software components for boundary value behavior and ensure that all code has been exercised adequately. We examine the available data from three safety-related, industrial software projects that have made use of unit testing. Using this information we argue that the perceived costs of unit testing may be exaggerated and that the likely benefits in terms of defect detection are quite high in relation to those costs. We also discuss the different issues that have been found applying the technique at different phases of the development and using different methods to generate those tests. We also compare results we have obtained with empirical results from the literature and highlight some possible weakness of research in this area.