Electronic Unit Pump Test Bench Development and Pump Properties Research

A unit pump test bench is developed on an in-line pump test platform. The bench is composed of pump adapting assembly, fuel supply subsystem, lubricating subsystem and a control unit. A crank angle domain injection control method is given out and the control accuracy can be 0.1° crank degree. The bench can test both mechanical unit pump and electronic unit pump. A test model-PLD12 electronic unit pump is tested. Full pump delivery map and some influence factors test is done. Experimental results show that the injection quantity is linear with the delivery angle. The quantity change rate is 15% when fuel temperature increases 30 ℃. The delivery quantity per cycle increases 30 mg at 28 V drive voltage. The average delivery difference for two same type pumps is 5 %. Test results show that the bench can be used for unit pump verification.

A note on self-normalized Dickey-Fuller test for unit root in autoregressive time series with GARCH errors

In this article, the unit root test for AR（p） model with GARCH errors is considered. The Dickey-Fuller test statistics are rewritten in the form of self-normalized sums, and the asymptotic distribution of the test statistics is derived under the weak conditions.

Using Genetic Algorithm as Test Data Generator for Stored PL/SQL Program Units

PL/SQL is the most common language for ORACLE database application. It allows the developer to create stored program units (Procedures, Functions, and Packages) to improve software reusability and hide the complexity of the execution of a specific operation behind a name. Also, it acts as an interface between SQL database and DEVELOPER. Therefore, it is important to test these modules that consist of procedures and functions. In this paper, a new genetic algorithm (GA), as search technique, is used in order to find the required test data according to branch criteria to test stored PL/SQL program units. The experimental results show that this was not fully achieved, such that the test target in some branches is not reached and the coverage percentage is 98%. A problem rises when target branch is depending on data retrieved from tables;in this case, GA is not able to generate test cases for this branch.

Approach of Separately Applying Unit Testing to AspectJ Program

A unit testing approach for AspectJ programs is proposed to separately test aspect units which have their own states. In the approach, aspects under test are converted to classes before execution of unit testing. In the conversion process, the context information passed through pointcut is transformed into advices, then the advices are converted to class member methods, and conflicts in the conversion result, if any, are resolved finally. The unit testing process consists of generating test cases, executing test cases and checking results.

Test Case Prioritization in Unit and Integration Testing:A Shuffled-Frog-Leaping Approach

Both unit and integration testing are incredibly crucial for almost any software application because each of them operates a distinct process to examine the product.Due to resource constraints,when software is subjected to modifications,the drastic increase in the count of test cases forces the testers to opt for a test optimization strategy.One such strategy is test case prioritization(TCP).Existing works have propounded various methodologies that re-order the system-level test cases intending to boost either the fault detection capabilities or the coverage efficacy at the earliest.Nonetheless,singularity in objective functions and the lack of dissimilitude among the re-ordered test sequences have degraded the cogency of their approaches.Considering such gaps and scenarios when the meteoric and continuous updations in the software make the intensive unit and integration testing process more fragile,this study has introduced a memetics-inspired methodology for TCP.The proposed structure is first embedded with diverse parameters,and then traditional steps of the shuffled-frog-leaping approach(SFLA)are followed to prioritize the test cases at unit and integration levels.On 5 standard test functions,a comparative analysis is conducted between the established algorithms and the proposed approach,where the latter enhances the coverage rate and fault detection of re-ordered test sets.Investigation results related to the mean average percentage of fault detection(APFD)confirmed that the proposed approach exceeds the memetic,basic multi-walk,PSO,and optimized multi-walk by 21.7%,13.99%,12.24%,and 11.51%,respectively.

Empirical Analysis of Object-Oriented Design Metrics for Predicting Unit Testing Effort of Classes

In this paper, we investigate empirically the relationship between object-oriented design metrics and testability of classes. We address testability from the point of view of unit testing effort. We collected data from three open source Java software systems for which JUnit test cases exist. To capture the testing effort of classes, we used metrics to quantify the corresponding JUnit test cases. Classes were classified, according to the required unit testing effort, in two categories: high and low. In order to evaluate the relationship between object-oriented design metrics and unit testing effort of classes, we used logistic regression methods. We used the univariate logistic regression analysis to evaluate the individual effect of each metric on the unit testing effort of classes. The multivariate logistic regression analysis was used to explore the combined effect of the metrics. The performance of the prediction models was evaluated using Receiver Operating Characteristic analysis. The results indicate that: 1) complexity, size, cohesion and (to some extent) coupling were found significant predictors of the unit testing effort of classes and 2) multivariate regression models based on object-oriented design metrics are able to accurately predict the unit testing effort of classes.

Is There Hysteresis in Unemployment in OECD Countries？ Evidence From Panel Unit Root Test With Structural Breaks

This study tests the hysteresis hypothesis of unemployment in fifteen OECD countries by using panel unit root tests which allow for structural breaks. We apply annual unemployment rates covering 1985-2008 periods. We test whether unemployment rates are stationary by using second generation tests which allow cross section dependency among series and panel unit root test based on structural break advanced by Carrion-i-Silvestre, Barrio-Castro and Lopez-Bazo （2005）. We find series as a stationary process with structural breaks according to Carrion-i Silvestre et al. （2005） test, while we find series as unit root process with second generation panel unit root test. According to the Carrion-i Silvestre et al. （2005） test, we find the evidence of absence of hysteresis in analyzed countries. As a result, temporary shocks have temporary effects on unemployment instead of permanent effect. Structural factors can affect the natural rate of unemployment and, therefore, unemployment would be stationary around a process that is subject to structural breaks. So, there still exists a unique natural rate of unemployment to which the economy eventually will converge.

Unit 1 of Ling’ao Nuclear Power Plant phase II underwent hot functional test successfully

On February 25, the Unit 1 of Ling’ao Nuclear Power Plant phase II underwent a 41-day-long hot functional test successfully with its major systems satisfying the requirements for

Architecture and Methodology of Unit Testing Embedding Pair-Wise Mode for Small Team

In this paper, the new organization for unit testing embedding pair-wise mode is proposed with the core thought focused on the cooperation of programmer and tester by “cross-testing”. The typical content of unit testing for the new organizing mode should have three aspects, including self-checking, cross-testing and independent-testing. For cross-testing, executing “pair-wise” mode, mainly tackles data testing, function testing and state testing, which function testing must be done by details and state testing must be considered for completeness. With the specializing of independent-testing, it should be taken as more rigid testing without arbitrariness. Consequently, strategy and measure are addressed for data testing focusing on boundary testing and function/state testing. And organizing method of procedure and key points of tackling unit testing are investigated for the new organizing mode. In order to assess the validity of our study and approach, a series of actual examples are demonstrated for GUI software. The result indicates that the execution of unit testing for the new organizing mode is effective and applicable.

Obsidian: Pattern-Based Unit Test Implementations

There exist many automated unit test-generator tools for Java with the primary task of generating test cases, comprised of inputs and a corresponding oracle, each of which is explicitly paired with a specific supporting test implementation. The authors posit that this explicit pairing, or conflating, of test implementation with test case is unnecessary and counter-productive. The authors address this problem by separating the conflated concerns into two distinct tasks: 1) instantiating test implementations and 2) instantiating test cases. This paper focuses on automating the first task in support of the second with the goal of freeing the test engineer to concentrate on test case instantiation. The authors present a new open-source test-preparation tool Obsidian that produces robust, comprehensive, and maintainable unit test implementations. Obsidian, built on the JUnit framework, uses a set of context patterns and associated algorithms combined with information from the Java Reflection API to generate these unit test implementations from Java byte code. These context patterns guide Obsidian to prepare test implementations that guarantee compilation, support exception handling, enable multiple test cases when required, and provide a suitable location for assertions about the test case outcome(s). Obsidian supports regression testing and test-driven development through its novel audits of the testing process.

基于TestBed/TBrun的高效测试执行方法

在使用TestBed/TBrun工具执行软件单元测试用例过程中,存在长数组无法自动赋值和结果比对导致测试效率低的问题。针对该问题,提出了一种基于TestBed/TBrun的高效测试执行方法。通过在后台文件中建立可自动识别读取长数组的通用驱动函数和自动对比测试结果的比对函数,对软件单元中的长数组输入/输出变量进行自动赋值及结果比对。经测试验证,该方法降低了用例执行耗时,提高了测试执行效率。

基于XML的UUT测试需求描述方法研究

针对ATS开发过程中UUT测试需求缺乏标准规范的信息描述方法,致使ATS软件复用性、移植性差等问题日益突出的现状,参考有关国际标准,建立了UUT测试概念模型和基于XML的UUT测试信息描述模型,包括原子测试模型、组合测试模型等,阐述了模型之间的关系,给出了UUT测试需求描述模型应用实例;UUT测试概念模型揭示了UUT测试问题的本质,为UUT测试需求描述模型的建立打下了基础,UUT测试需求描述模型实现了UUT测试需求的标准化描述;该方法提高了UUT测试需求描述信息的复用性,改善了ATS的互操作性。

基于Junit自动生成类测试案例框架的实现

论文对Java程序的抽象类、包含内隐类的接口、其它内隐类和普通类的测试提出了不同的测试案例模式,结合Liskov替代原则对类测试的要求,实现一个基于Junit生成包含测试神谕的测试案例框架的工具。借助该工具,程序员在编写测试案例时,只需在自动生成的测试案例框架中添加测试数据就可获得完整的测试案例。

基于CppUnit的虚拟试验单元测试研究

虚拟试验是通过大量平台软件验证实物试验的可行性,达到"以实验虚以虚辅实以虚预实"的目的;这对平台软件的稳健性具有较高的要求,软件测试是提高软件产品质量的重要手段,而其中的单元测试是对软件模块的功能测试;CppUnit主要用于实现对软件的单元测试,基于CppUnit提出了一种应用于虚拟试验平台软件的单元测试方法,实现了对平台软件功能的单元测试,平台使用者在软件开发阶段不仅能较好地验证软件的稳健性,而且能提高虚拟试验验证的效率,为实物试验提供参考依据。

JUnit在单元测试中的应用

单元测试在软件开发过程中起着非常重要的作用。JUnit是一个用于Java单元测试的开放源代码的测试框架,本文通过具体案例,介绍应用JUnit进行自动化测试的方法。

JUnit框架剖析

JUnit是java语言的开放源码的单元测试框架,设计非常精巧。分析它的包结构、主要类的关系和作用以及框架中涉及到的设计模式,并通过一个实例展示其扩展功能。

一种面向UUT的自动测试信息模型

根据大型复杂装备测试面临的被测设备数量多,被测信号类型、测试需求多样的问题,建立面向UUT的自动测试信息模型,包括测试资源信息模型、测试项目信息模型和测试数据信息模型,将测试流程所需的UUT信息模型化,并在UUT、TPS、测试信息模型间建立一一对应关系,由此提高软件的模块化水平和可移植,并降低测试软件开发和维护的难度和成本。

基于JTest的自动化单元测试技术

单元测试框架在软件开发及测试领域均较普及,基于常用基类和各种断言进行用户运用和拓展,可编写出适用于不同项目的单元测试用例。但当项目调用关系复杂或规模较大时,传统测试框架具有一定局限性。针对该问题,结合JTest测试工具,介绍了自动化单元测试流程和方法,可实现运用传统框架对大型项目自动生成并执行测试用例。JTest可通过分析代码自动生成并执行单元测试用例,跟踪代码执行情况,并生成测试报告,从而有效降低单元测试成本并提高测试效率。