基于模型的图形用户界面事件交互图生成方法

用户界面(GUI)测试是一项很困难的工作,一个重要的原因是背景事件会影响测试结果,基于模型的图形用户界面测试技术可以解决这个问题。目前基于模型的图形用户界面测试技术有两种常用的GUI模型:事件流图(EFG)和事件交互图(EIG)。这两种模型可以表示GUI事件之间的交互关系,其中EIG是从EFG转换而来的。通过一个简单的GUI实例对GUI中的事件进行了明确的划分,并且为适应文中的划分事件改进了原有的MX算法。最后根据GUI的事件驱动性和对GUI事件的划分提出了一种由EFG转换成EIG的新方法:驱动算法。实例表明,此方法使EFG转换成EIG的过程更简单。     

面向GUI软件测试的交互图生成及其实现*

从控件的信息入手,研究了界面的控件间功能交互关系,提出了基于交互图的GUI测试方法,并开发了一个基于交互图的GUI测试工具GUITester.它能自动生成交互图和测试用例,大大提高了GUI软件测试的效率和覆盖率.     

Pattern‐based GUI testing: Bridging the gap between design and quality assurance

Software systems with a graphical user interface (GUI) front end are typically designed using user interface (UI) Patterns, which describe generic solutions (with multiple possible implementations) for recurrent GUI design problems. However, existing testing techniques do not take advantage of this fact to test GUIs more efficiently. In this paper, we present a new pattern‐based GUI testing (PBGT) approach that formalizes the notion of UI Test Patterns, which are generic test strategies to test UI patterns over their different implementations. The PBGT approach is evaluated via 2 case studies. The first study involves 2 fielded Web application subjects; findings show that PBGT is both practical and useful, as testing teams were able to find real bugs in a reasonable time interval. The second study allows deeper analysis by studying software subjects seeded with artificial faults; the findings show that PBGT is more effective than a manual model‐based test case generation approach.     

GUICop: Approach and toolset for specification‐based GUI testing

Oracles used for testing graphical user interface (GUI) programmes are required to take into consideration complicating factors such as variations in screen resolution or colour scheme when comparing observed GUI elements with expected GUI elements. Researchers proposed fuzzy comparison rules and computationally expensive image processing techniques to tame the comparison process because otherwise the naïve matching comparison would be too constraining and consequently impractical. Alternatively, this paper proposes GUICop, a novel approach with a supporting toolset that takes (1) a GUI programme and (2) user‐defined GUI specifications characterizing the rendering behaviour of the GUI elements and checks whether the execution traces of the programme satisfy the specifications. GUICop comprises the following: (1) a GUI Specification Language; (2) a Driver; (3) Instrumented GUI Libraries; 4) a Solver; and (5) a Code Weaver. The user defines the specifications of the subject GUI programme using the GUI Specification Language. The Driver traverses the GUI structure of the programme and generates events that drive its execution. The Instrumented GUI Libraries capture the GUI execution trace, ie, information about the positions and visibility of the GUI elements. And the Solver, enabled by code injected by the Code Weaver, checks whether the traces satisfy the specifications. GUICop was successfully evaluated using 4 open source GUI applications that included 8 defects, namely, Jajuk, Gason, JEdit, and TerpPaint.     

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.     

Comparing model-based and dynamic event-extraction based GUI testing techniques: An empirical study

Graphical user interfaces are pervasive in modern software systems, and to ensure their quality it is important to test them. Two primary classes of automated GUI testing approaches, those based on static models and those based on dynamic event-extraction, present tradeoffs in cost and effectiveness. For example, static model-based GUI testing techniques can create test cases that contain nonexecutable events, whereas dynamic event-extraction based GUI testing techniques can create larger numbers of duplicate test cases. To better understand the effects of these tradeoffs, we created a GUI testing framework that facilitates fair comparison of different GUI testing techniques, and we conducted a controlled experiment comparing representative versions of static-model based and dynamic event-extraction based testing techniques on several GUI-based Java applications. Our study reveals several cost and effectiveness tradeoffs between the techniques, with implications for research and practice.     

基于CIS的消息驱动的GUI自动测试方法

在CIS概念的基础上,结合GUI系统的消息特性,提出了一套基于CIS的消息驱动的GUI自动测试方法。介绍了一套自定义的基于CIS的测试脚本描述语言。讨论了基于CIS测试脚本的消息驱动的GUI自动测试方法的原理、步骤。分析了GUI系统的CIS之间的关系并给出了一个CIS测试顺序分配算法。实验结果表明该方法对GUI系统的一致性测试、回归测试和资源消耗测试是非常有效的。     

基于事件权重的GUI测试路径生成方法

针对GUI事件驱动特性产生无限多个测试路径的问题,提出在事件流图中考虑事件权重的GUI测试路径生成方法。分析了事件流图模型,采用层次分析法计算事件的权重,通过遍历事件流图生成GUI测试路径。该方法减少了测试路径的数目,生成的测试路径更具有效性,提高了测试效率。     

嵌入式数字存储示波器的图形界面设计与应用

嵌入式图形用户界面（Embedded GUI）是嵌入式计算机系统的核心技术之一。本文讲述了如何实现Nano—X Windows GUI系统在DSP blackfin 533上的移植，以及在嵌入式示波器程序中的应用。     

Integration testing of Object-Oriented and Aspect-Oriented programs: A structural pairwise approach for Java

Several testing approaches focus on finding faults in software units of implementation. A problem not addressed by unit testing is the interaction among units, with respect to the correctness of their interfaces. In this paper a structural integration testing approach for Object-Oriented (OO) and Aspect-Oriented (AO) Java programs is presented. To make the activity more feasible, we address the testing of pairs of units (i.e., methods and pieces of advice). A model called (PairWise Def-Use) graph to represent the flow of control and data between pairs of units is proposed. Based on the , the following family of testing criteria is defined: all-pairwise-integrated-nodes (control-flow based), all-pairwise-integrated-edges (control-flow based), and all-pairwise-integrated-uses (data-flow based). To evaluate the proposed approach, an implementation of the criteria in a testing tool is presented along with an example of usage and an exploratory study. The study with 7 AO programs that are also OO was conducted to investigate the cost of application and usefulness of the approach. Results provided evidence that the criteria are practical and useful for integration testing of OO and AO programs.     

JFCunit在GUI界面自动化测试中的应用与实现

JFCunit是基于Junit扩展而来,专门用于解决JAVA GUI图形界面功能测试的问题。该文先简要介绍了JFCunit的简介及其用途,分析了JFCunit的实现流程图。最后以一个简单实例阐述了使用JFCunit进行GUI图形界面功能测试的实现方式。     

JFCunit在GUI界面自动化测试中的应用与实现

JFCunit是基于Junit扩展而来,专门用于解决JAVA GUI图形界面功能测试的问题。该文先简要介绍了JFCunit的简介及其用途,分析了JFCunit的实现流程图。最后以一个简单实例阐述了使用JFCunit进行GUI图形界面功能测试的实现方式。     

A safe regression testing approach for safety critical systems

Regression testing is important activity during the software maintenance to deal with adverse effects of changes. Our approach is important for safety critical system as usually formal methods are preferred and highly recommended for the safety critical systems but they are also applied for the systems development of other than critical system. Our approach is based on Regression testing using VDM++ which takes two VDM++ specifications, one baseline and other delta (Changed) along with test suite for the baseline version. It compares both versions by using comparator module, identifies the change. By analyzing the change we classify the test cases from original test suite into obsolete, re-testable, and reusable test cases. Our scope is at unit level i.e. at class level. Our approach gets two versions of VDM++ specification and returns regression test suite for the delta version. Our approach distinguishes test cases which are still effective for the delta version of VDM++ specification and it differs from re-test all strategy as it can distinguish the test cases and identifies test cases which are useful for delta version. Test cases reusability and test case reduction is the main objective of our approach. Our approach presents how to perform regression testing using VDM++ specification during the maintenance of systems.     

基于GUI的Android移动软件性能测试

移动应用软件已经拥有了数以千万计的用户群体.根据最新统计,Android手机以85.1%的市场占有份额,成为了最受欢迎的移动端设备.Android应用软件的快速开发,使得如何保证程序质量,成了难题.我们不仅要考虑程序的正确性,也应保证运行时的流畅性.现有的性能研究工作都基于传统的静态分析或者动态执行.对于Android程序,静态分析具有一定的局限性,而动态分析又忽略了APP执行时的遍历方式.因此,本文提出了基于GUI的Android自动化性能测试框架,将着重关注页面状态和APP状态的相关性.通过对页面的分析,聚合,尽可能遍历到APP的各个状态,然后从日志中,找出APP性能上的问题.本框架使用Java作为开发语言,搭建了Android移动软件自动化性能测试框架,并在开源社区F-Droid上随机抽取了移动应用软件进行实验.实验表明,该技术能更多的遍历APP的状态,发现APP在运行过程中出现的性能问题,取得良好的效果.     

软件测试方法简述与展望

软件测试是一门重要的、具有广泛应用的学科,随着应用系统的不同,软件的测试方法呈现多样性。该文从概念、基本问题、方法、任务等各个方面进行评述,讨论了待解决的问题,并对今后的发展方向进行了展望。     

基于XML的桌面软件GUI的设计和应用

传统桌面软件的GUI(GraphicUserInterface)实现方式缺乏类似HTML模式的"页面描述机制",这个弊端导致大量冗余工作的出现。而且软件GUI的运行时动态创建也存在问题。针对这些缺陷,该文提出了基于XML的图形用户界面的表达描述和实现,在这种方式下的GUI与软件属于无耦合方式,从而从根本上解决了跨平台的问题。另外,这种方式下GUI可以与插件系统进行对接,为界面的构件化提供了可能。     

A practical approach for testing timed deterministic finite state machines with single clock

Finite State Machines (FSMs) are widely used for verification and testing of many reactive systems and many methods are proposed for generating tests from FSMs with the guaranteed fault coverage. However, some systems can only be properly described when time constraints are considered, advocating the adoption of models with the notion of time. In this paper, a method for deriving conformance tests with the guaranteed fault coverage from a Timed FSM (TFSM) with a single clock is presented. Test derivation is based on a given fault domain that allows the derivation of test suites with reasonable length. More precisely, the fault domain includes every possible faulty TFSM implementation with the known largest time constraints boundaries and minimal duration of time guards. Given a deterministic possibly partial TFSM specification, a complete test suite that guarantees the detection of all faulty implementations with respect to the above fault domain is derived. Experiments with randomly generated timed FSMs are conducted to determine length of obtained test suites and assess the impact of varying the TFSM specification parameters on length of obtained test suites. Further, experiments with both untimed and timed machines are conducted and these experiments show that similar patterns for timed and untimed machines are obtained with respect to varying the number of states, inputs, and outputs of machines.     

基于UC/GUI的嵌入式GUI在S3C 2410上的移植

嵌入式图形用户界面为嵌入式系统提供了人机交互界面,大大方便了嵌入式系统的人机交互,进而加速了嵌入式系统的流行。选择了基于UC/GUI的嵌入式GUI作为移植对象,并详细介绍了将其移植至S3C2410开发平台上的技术。该移植技术对于其他的嵌入式开发板也具有一定的参考价值。     

基于“Good”测试套件的GUI回归测试优化

回归测试在软件测试过程中是非常重要的,同时也是非常费时费力的。为了适应软件测试的需求,提高回归测试的效率,降低测试成本,针对目前GUI回归测试的困难,依据Atif M.Memon等人提出的新的回归测试方法,根据一个"Good"的测试套件对测试成本和"fault-detection effectiveness"的影响,突出一个"Good"的测试套件的特点,给出一个新的回归测试方法。该方法根据测试套件的特点,有针对性地选择合适的测试用例来构建回归测试套件。这样不仅有针对性,同时也优化了测试套件,提高了测试效率。     

一种基于UML的多态性测试线索生成方法

首先分析了多态性的成因及形式化表示;然后借用控制流图的思想分析协作图,将类图中的信息结合到协作图中,对传统的函数间受限控制流图IRCFG进行多态性扩展并带上类图的基本信息;最后分析了测试覆盖准则并给出测试线索的生成方法。