AB:一种简单的性能测试工具

Web及其应用程序的普及使得Web服务器的性能测试变得越来越重要,现有的性能测试工具林林总总,数量很多,不同的性能测试工具都有其优缺点,应根据实际情况挑选最适合的工具.Apache自带的性能测试工具AB,功能虽然不多,但非常实用,使用也很简单.文章阐述了性能测试工具AB的特点、安装及测试方法,并结合测试实例分析了它的测试结果及遇到的一些问题.     

性能测试工具LoadRunner介绍

性能测试用来测试软件在集成系统中的运行性能的,它是相对于功能测试,并在功能测试基础上对系统进行的全面的测试。而LoadRunner正是一款能够预测系统行为和性能的负载测试工具。通过以模拟上千万用户实施并发负载及实时性能监测的方式来确认和查找问题,LoadRunner能够对整个企业架构进行测试。     

网络性能测试工具浅析

网络性能测试被认为是对下一代网络的一种挑战。文章论述了几种主要的网络性能测试工具的应用,并就其功能和特点进行了比较分析,以便人们选择合适的网络性能测试工具。     

磁盘阵列性能测试工具研究

目前国内外有许多优秀的性能评测基准如TPC、SPC、IOMeter、IOZONE等,但它们在应用环境和功能上存在一些限制。为了解决这个问题,设计并实现了一个基于Linux分布式系统的磁盘阵列性能测试工具DAMeter,并与业内广泛使用的Windows下磁盘阵列性能测试基准IOMeter进行对比实验,证明了DAMeter工具测试结果的准确性和可靠性。并介绍了如何使用DAMeter产生不同负载进行磁盘阵列性能测试。     

性能测试工具的研究与设计

研究了目前应用较广的几种性能测试工具，给出了一个分布式性能测试工具的体系结构，分析了其中的脚本开发平台，给出了设计和实现方案。     

性能测试工具能力评估框架研究

随着分布式应用系统的广泛使用,对性能测试的要求越来越高,而性能测试通常都需要借助于自动化性能测试工具才能实现.但是,评估工具的能力成熟度从而为选择恰当的工具提供依据,仍然是性能测试人员面临的主要困难.为解决这个问题,本文提出了一个框架,从如下三个方面评估性能测试工具的能力：可靠性,测试能力和资源管理能力.每个评估方面都由一组评估特性组成.最后,以目前市场上最流行的三种产品为例进行了分析和比较.     

自动化测试工具性能优化研究

软件测试在系统开发过程中发挥着越来越重要的作用,而传统的LAMP结构已经无法满足快速增长的业务需求。基于自动化测试工具使用过程中遇到的变更类的测试流程耗时、数据加载速度等实际问题,本文重点从测试流程、算法、数据库等几个方面对自动化测试工具的性能进行了优化研究,并对优化结果进行了分析。     

Apache性能测试工具开发与研究

根据对Apache中的测试工具ApacheBench的分析,采用了CMMI3中的软件开发方法,利用多线程模拟多个用户实现了多用户并发测试,并利用管道技术对多个线程进行操作,实现数据共享。设计并实现了一个新的测试工具,可以实现对符合HTTP协议的网站性能进行测试。     

TPC-DS性能测试工具的实现

阐述了新一代面向决策支持的数据库性能测试基准TPC-DS的数据模型、业务模型、执行模式和度量方法,设计了一个支持不同数据库管理系统(DBMS)性能对比测评的TPC-DS测试框架,阐述了配置文件、查询执行控制、数据维护机制等关键实现技术。最后通过对任务配置和语法配置的实践,验证了工具对不同DBMS、不同优化配置的对比测试可用性。     

RTSP流媒体服务器性能测试工具

基于RTSP协议的流媒体应用日益增加,如何评测RTSP流媒体服务器的服务性能成为一个亟待解决的实际问题.本文在分析流媒体业务性能指标的基础上,设计和实现了一种RTSP协议流媒体服务器性能的测试工具.该工具通过读取测试用例脚本设定参数建立测试场景,利用多线程机制生成多实例伪终端向流媒体服务器发送RTSP信令、接收和解析R...     

Web系统性能测试研究与实践

随着Internet技术的日益发展,Web系统应用越来越广泛,面向的用户群体也日益庞大。系统的复杂性及用户操作的不确定性,对系统性能提出了更高的要求。在Web系统上线发布之前,对其开展性能测试,及时发现不足,为系统正式运行提供质量保障。介绍性能测试的原理、指标及测试场景的选择等,并使用Silk Performer性能测试工具测试企业外部网站系统。实验结果表明,性能测试可以模拟和预测真实环境中对系统的压力,将系统中存在的问题暴露出来,有助于问题的定位与解决。     

软件安全性测试方法与工具

软件的应用越来越广泛,规模和复杂度不断提高,软件中的安全缺陷与漏洞也在不断增多,软件安全性问题日益突出.软件安全性测试是保证软件安全性、降低软件安全风险的重要手段.论述了软件安全性测试的特点、内容,重点研究了国内外软件安全性测试的主要方法与工具,分析了各种方法的优缺点与适用范围,提出了一种安全性测试工具的分类方法,总结了当前研究工作并指出了未来软件安全性测试技术的研究重点与发展方向.     

Effects of computer-based testing on test performance and testing motivation

Computer-based testing (CBT) is a green computing strategies used to reduce paper consumption. However, some scholars have questioned the effectiveness of CBT and suggested for conducting systematic studies on CBT to carefully check its reliability and validity before opting for it. Recently, some studies have evaluated the effectiveness of CBT by comparing it with paper–pencil testing (PPT), and the findings were inconsistent. Besides this, most of these studies have been conducted using quasi or basic experimental designs without identifying testing effects on test takers. The limitation of these design is testing effects might occur when a participant in the control or treatment group is tested at least twice on a same test, and it influences the outcomes of taking a posttest, therefore, the findings might be misinterpreted. This study employed a Solomon four-group experimental design (2 × 3 factorial design) on a group of student teachers (n = 140) to compare CBT and PPT on test performance (test scores), testing time and testing motivation. Results indicated that the CBT mode is more reliable in terms of internal and external validity. The CBT significantly reduced testing time and developed stronger self-efficacy, intrinsic and social testing motivation in the participants.     

Implementing prototype testing tools

Testing tools are software analyzers that use information from particular executions of a program as well as information about a specification and the program text itself. Research prototypes of such tools are essential to investigate the ideas they embody. Often, hand calculation is so tedious and error-prone that an investigator cannot obtain any intuition about his or her ideas without an implementation to aid in experiments. Traditionally, such tools have been implemented in conventional high-level languages (e.g., C, Pascal), a process that takes more time than a prototype should. The technology of compiler generators and logic programming, applied to the idea of self-instrumenting programs, drastically shortens the prototype cycle. This paper describes a general method for implementing prototype tools, gives examples of several old and new testing techniques fitted into the method, and discusses the ease with which such prototypes may be changed.     

Integrating techniques and tools for testing automation

This article presents two tools to generate test cases, one for Java programs and one for .NET programs, as well as a structured testing process whereby such tools can be used in order to help in process automation. The main innovation in this work is the joint use of diverse techniques and technologies, which have been separately applied to test automation: reflection to extract the class structure; regular expressions to describe test templates and test cases; JUnit and NUnit as test case execution frameworks; mutation and MuJava as test case quality measurers; serialization to deal with the parameters of complex data types; and once more, reflection, to facilitate the test engineer in the task of writing the oracle. Finally, the article presents an experiment carried out to validate the work. Copyright © 2006 John Wiley & Sons, Ltd.     

Compiler performance analysis tools

Most of the performance bench-marks for compilers do not give detailed performance characteristics that might be useful to a programmer. The goal of most bench-marks seems to be to produce a single number. A set of bench-mark tools that measure individual language features of C and generate a large number of measurements has been designed to create a detailed performance profile of any C compiler. There is an emphasis on the detailed statement-level measurements of both CPU and I/O aspects of C, but there is also a range of routine and program-level bench-marks that seek to measure the interaction of CPU and I/O in actual application programs. The programs are portable, parametrized, and openended so that additional measurements can be added with little effort. With some additional effort, the tools could be adapted to other languages.     

基于敏捷开发的X测试模型的研究与改进

软件测试的实施效果直接影响到软件的质量,目前出现了一些测试模型,并且有一定的实用性,例如V模型、W模型、X模型等,其中X测试模型正受到越来越多的关注.对当前颇为流行的敏捷开发模式进行了一定的研究之后,适当地调整模块任务分配的粒度,软件开发过程中采用了X测试模型,并根据具体开发情况对X测试模型进行了相应的调整与改进,体现出其较好的应用效果,对中小型软件开发的测试有着很好的适用性.     

Reproducible testing of monitors

This paper describes a systematic method for testing monitor modules which control process interactions in concurrent programs. A monitor is tested by executing a concurrent program in which the processes are synchronized by a clock to make the sequence of interactions reproducible. The method separates the construction and implementation of test cases and makes the analysis of a concurrent experiment similar to the analysis of a sequential program. The implementation of a test program is almost mechanical. The method, which is illustrated by an example, has been successfully used to test a multicomputer network program written in Concurrent Pascal.