基于一致性测试理论的Statechart描述的测试用例自动生成

本文研究Statechart描述的测试语义和测试用例的自动生成.基于Tretmans的从标记转换系统描述自动生成测试用例的方法,我们研究如何从Statechart描述自动生成测试用例.本文的主要贡献在于建立了基于Statechart描述的一致性测试和测试用例生成的形式化基础.为Statechart描述建立了形式化测试语...     

基于输入/输出动作的协议形式化描述和测试用例生成方法

通信协议的形式化描述及在其基础之上的协议测试用例生成,一直是协议工程的重要研究内容。为此尝试将RSL引入协议形式化描述：首先探讨了一种基于输入/输出动作模型的协议形式化描述方法;随后对基于RSL描述的协议测试技术展开了讨论,提出了一种基于输入/输出动作的协议测试序列生成法则以及基于此法则的测试用例生成方法,并对使用该方法生成的测试用例的性质进行了讨论。     

基于UML集成测试用例的算法研究

对基于状态图生成集成测试用例的方法进行了研究,通过构造集成测试模型,重点描述了两个对象或组件的状态图进行合并的方法,并给出了状态图的形式化描述,以及如何对组合状态图进行展开用于集成测试用例的生成.为了验证该方法的实用性,又以实际项目研究为例,实现了基于状态图集成测试用例的生成工具,对该方法进行了验证,并给出了算法的部分实现代码.该方法将系统设计和测试用例的设计统一起采,是软件测试自动化的一个探索.     

基于形式化方法的测试驱动开发研究

对测试驱动开发中测试用例的自动生成和管理问题进行了研究,并时现有方法进行了分析和比较.给出了一种基于形式化方法的测试用例生成和管理方案.该方案通过形式化语言描述软件规约,并通过相应工具生成和管理测试用例,从而提高了测试驱动开发的效率.最后给出了该方案在极限编程各个开发阶段的应用.     

一种编译优化测试用例自动生成方法的设计与实现

编译器的质量保证对提高软件产品的质量有着重要作用,对编译优化的测试是其中的核心部分.对编译优化的测试需要大量的测试用例程序.要构造这些测试用例,使用传统手工构造方法面临着效率低的问题,而基于文法的构造方法则针对性不足.从对优化的形式化描述出发来自动构造测试用例能克服这些缺点.本文设计并实现了一种基于形式化描述的编译优化测试用例程序生成方法.该方法基于编译优化的时序逻辑描述构造关键顶点控制流图,逐步转换为控制流图并得到用例程序.针对GCC(版本4.1.1)进行的覆盖率测试实验表明,该方法可以生成具有较高针对性的测试用例,并达到相当的覆盖程度.     

一个面向对象软件自动测试框架的设计和实现

介绍了一个测试用例驱动的面向对象软件自动化测试框架(简称为TCDA).TCDA使用UML作为形式化的分析和设计规格说明,从UML的体系结构视图中自动获取测试用例,并以XML的形式保存这些测试用例.TCDA可以根据具体编程语言,将测试用例翻译成由一系列源文件组成的测试脚本.测试执行过程中,测试脚本首先会被编译和链接,生成可执行文件,接着这些可执行文件将被运行,同时测试结果将被记录和分析,并最终生成一个结果分析报告.TCDA的原型系统使用Java实现.该系统包括测试配置、测试用例生成、测试脚本生成、测试执行和结果分析五个模块,分别支持以上描述的过程.     

形式化的软件测试模型研究

传统方法中基于软件测试工程师经验的测试用例构造技术使得软件测试的质量很难得到保证。本文提出一种基于形式化方法的软件测试模型。该模型使用形式化描述语言RSL对软件设计进行描述,并在此基础上提出了自动生成软件测试各个阶段所需测试用例的方法框架以及相关实验结论。     

基于时态逻辑的协议RSL形式化描述

研究以RAISE规范语言(RSL)描述时态逻辑中always算子、sometimes算子和until算子的方法以及对复合时态算子的描述方法,提出在时态逻辑模型基础上用RSL对协议进行形式化描述的步骤,以AB协议为示例,给出其基于时态逻辑模型的RSL描述,从而证明该描述模型有利于协议验证和协议测试用例生成的自动实现。     

基于模型检测技术的变异测试用例生成方法

为了进行基于模型的软件测试变异分析,文中提出了一种基于模型检测的变异测试用例生成方法。基于模型检测工具UPPAAL的形式化分析与测试框架,首先用符合规范的时间自动机模型描述被测系统;然后基于时间自动机模型的基本结构和语法,对系统模型进行一组变异操作,并模拟实现时可能出现的一些错误;对变异后的模型分别使用UPPAAL Yggdrasil工具,生成一组能覆盖变异区域的测试用例;在系统变异模型上执行生成的测试用例,根据测试执行结果(是否能“杀死”变异体)筛选出一组有效的测试用例。通过实例验证,所提方案生成的测试用例是有效的,且测试用例集变异分数优于现有的基于状态机复制的变异测试用例自动生成方法和基于模型中变换覆盖的变异测试用例生成方法。     

UML顺序图的结构化操作语义研究

UML顺序图侧重于展示对象之间的消息交互过程,但其动态语义缺乏形式化的描述,不利于对顺序图模型的准确理解和基于该模型的测试用例生成。为此,依据UML1. 5规范,采用BN定义顺序图的形式化语法,提出了活动点的概念;在此基础上,讨论并给出了单个对象执行消息动作的结构化操作语义以及顺序图模型的整体结构化操作语义,为模型检验和基于顺序图的测试用例生成提供了前提。     

Systems engineering principles for the design of biomedical signal processing systems

Systems engineering aims to produce reliable systems which function according to specification. In this paper we follow a systems engineering approach to design a biomedical signal processing system. We discuss requirements capturing, specification definition, implementation and testing of a classification system. These steps are executed as formal as possible. The requirements, which motivate the system design, are based on diabetes research. The main requirement for the classification system is to be a reliable component of a machine which controls diabetes. Reliability is very important, because uncontrolled diabetes may lead to hyperglycaemia (raised blood sugar) and over a period of time may cause serious damage to many of the body systems, especially the nerves and blood vessels. In a second step, these requirements are refined into a formal CSP‖ B model. The formal model expresses the system functionality in a clear and semantically strong way. Subsequently, the proven system model was translated into an implementation. This implementation was tested with use cases and failure cases.Formal modeling and automated model checking gave us deep insight in the system functionality. This insight enabled us to create a reliable and trustworthy implementation. With extensive tests we established trust in the reliability of the implementation.     

A systematic approach to embedded biomedical decision making

An embedded decision making is a key feature for many biomedical systems. In most cases human life directly depends on correct decisions made by these systems, therefore they have to work reliably. This paper describes how we applied systems engineering principles to design a high performance embedded classification system in a systematic and well structured way. We introduce the structured design approach by discussing requirements capturing, specifications refinement, implementation and testing. Thereby, we follow systems engineering principles and execute each of these processes as formal as possible. The requirements, which motivate the system design, describe an automated decision making system for diagnostic support. These requirements are refined into the implementation of a support vector machine (SVM) algorithm which enables us to integrate automated decision making in embedded systems. With a formal model we establish functionality, stability and reliability of the system. Furthermore, we investigated different parallel processing configurations of this computationally complex algorithm. We found that, by adding SVM processes, an almost linear speedup is possible. Once we established these system properties, we translated the formal model into an implementation. The resulting implementation was tested using XMOS processors with both normal and failure cases, to build up trust in the implementation. Finally, we demonstrated that our parallel implementation achieves the speedup, predicted by the formal model.     

Formal methods software engineering for the CARA system

This paper discusses the application of formal methods software engineering (FMSE) to the development of the Computer Automated Resuscitation A (CARA) medical device at Walter Reed Army Institute of Research. Because this system is potentially life critical, a high level of quality was required. A formal engineering approach to the software development activities was chosen to satisfy this need. Specifically, a technique called sequence enumeration was applied to elicit and refine requirements while deriving a formal specification. The fundamentals of the specification process that was used on the project are described along with a brief summary of the project experience in the development and testing phases. The project employed recent advances in Cleanroom software engineering methods along with older box-structured development and usage-model-based statistical testing techniques.     

基于测试需求的互操作性测试用例生成方法

网络化应用将成为未来软件技术发展的主导模式。为了保证网络化应用之间能够有效地协同工作,必须对其进行互操作性测试。互操作性测试具有测试需求复杂易变、测试用例设计困难的特点,因而需要消耗大量成本。为此,提出一种基于测试需求的互操作性测试用例生成方法。该方法采用模型驱动的测试思想,以测试需求模型描述互操作性测试需求,以状态图描述各被测应用的规格说明,通过两者的结合生成满足测试需求的测试用例。     

Towards the Integration of Visual and Formal Models for GUI Testing

This paper presents an approach to diminish the effort required in GUI modelling and test coverage analysis within a model-based GUI testing process. A familiar visual notation a subset of UML with minor extensions is used to model the structure, behaviour and usage of GUIs at a high level of abstraction and to describe test adequacy criteria. The GUI visual model is translated automatically to a model-based formal specification language (e.g., Spec), hiding formal details from the testers. Then, additional behaviour may be added to the formal model to be used as a test oracle. The adequacy of the test cases generated automatically from the formal model is accessed based on the structural coverage of the UML behavioural diagrams.     

Integration and analysis of use cases using modular Petri nets inrequirements engineering

It is well known that requirements engineering plays a critical role in software quality. The use case approach is a requirements elicitation technique commonly used in industrial applications. Software requirements are stated as a collection of use cases, each of which is written in the user's perspective and describes a specific flow of events in the system. The use case approach offers several practical advantages in that use case requirements are relatively easy to describe, understand, and trace. Unfortunately, there are a couple of major drawbacks. Since use cases are often stated in natural languages, they lack formal syntax and semantics. Furthermore, it is difficult to analyze their global system behavior for completeness and consistency, partly because use cases describe only partial behaviors and because interactions among them are rarely represented explicitly. We propose the Constraints-based Modular Petri Nets (CMPNs) approach as an effective way to formalize the informal aspects of use cases. CMPNs, an extension of Place/Transition nets, allow the formal and incremental specification of requirements. The major contributions of the paper, in addition to the formal definitions of CMPNs, are the development of: 1) a systematic procedure to convert use cases stated in natural language to a CMPN model; and 2) a set of guidelines to find inconsistency and incompleteness in CMPNs. We demonstrate an application of our approach using use cases developed for telecommunications services     

Constructing and revising formal arguments in requirements engineering

Confidence that a proposed software-based system, once implemented, will be successful in its environment can be given through a formal argument, typically proof in a formal language. Problems with such arguments include the need to account for the relationships between different kinds of model (models of the proposed system, of assumptions concerning its environment, and of the joint properties, or requirements, which the system should achieve with its environment), and the need to revise these models within an exploratory requirements engineering process. This paper investigates the assumption/commitment style of modelling, originally developed for reasoning about interference in concurrent systems, for developing such arguments. The style, using a simple temporal logic, is used to express these models, with an associated compositional reasoning method allowing arguments to be constructed, and revised with minimal re-work of proof. Some conclusions are drawn concerning the benefits of, and problems with, this approach. The approach is illustrated with a meeting-scheduler example.