这是一个内部流程图,LoadRunner内部各个组件之间如何进行交互,数据流和文件流之间如何进行.
下面是各个步骤的简单介绍
1. application serverson this page under test are placed under stress by
2. driver processes mdrv.exe (the Multi-threaded Driver Process) and
r3vuser.exe which emulate application clients such as Internet Explorer web
brower. It performs 3 main actions:
(1). Kli> cpp (C language pre-processor) cci (C pre-compiling) which creaes
a file with ci file, and
(2). execute using the driver for the protocol technology being tested.
Runs can be invoked to run “silently” by invoking Mdrv.exe
from a Windows batch script.
Mdrv can automatically stop loading Vusers because they
communicate with Vusers and monitor CPU usage on Windows Load Generator
machines.
A separate JVM is instantiated by each Java-based Vuser on
Windows-based machines. #Java Vusers are not supported on Unix platforms.
3. virtual Vusers are invoked as groups (logical collection
of virtual users running the same script on a specific load generator machine)
4. by agents (3,900K magentproc.exe) running as a service or as a processon
this page
5. on load generator client machines.
6. Each machine hosting agents maintains an Execution Log
in a .qtp file.
7. When logging is enabled, the agent also creates within the results folder a
sequential log file for each Vuser (segregated by Vuser group).
8. During execution, this file is displayed in the view > Show Output window
on the LoadRunner Controller machine.
9. Upon a pre-set delay, the Scheduler running on a
Controller machine instructs agents (via Windows port 54345 or dynamic Unix
port) to initiate test session scenarios. The Controller (wlrun.exe) sends a
copy of scenario files along with the request.
10. Agents are launched by the Remote Agent Dispatcher process (formerly called
Remote Command Launcher (RCL)) on each load generator machine.
11. Each agent refer to scenario (.lrs) definition files to determine which
Vuser groups and scripts to run on host machines.
Idea This means the Controller can be started from a DOS
batch (.bat) file (preferrably with a short name on a root drive):
REM Start Controller:
SET M_ROOT=C:\Program Files\Mercury Interactive\LoadRunner\bin
cd %M_ROOT%
wlrun.exe -TestPath D:\Dev\Dev1.lrs -port 8080 -Run -DontClose
pause Press Ctrl-Z to keep this window or
* Including the -Run parameter is the same as manually
pressing the “Start Scenario” automatically upon invocation. This is not a good
idea because you may have to decide about collating the file from a previous
run or want to change the output folder.
* This assumes that the system’s environment PATH variableanother page on this
site was updated to include where LoadRunner is installed.
12. The Controller is invoked using parameter values within
files in the Windows OS folder (WINNT for Windows 2000 and WINDOWS for Windows
XP). The Windows folder is used because LoadRunner is designed to have only one
instance of Controller running at a time on a machine.
Idea To quickly switch among several applications, save a
copy of LoadRunner’s ini files after working on it within the Controller, then
use Notepad to craft a batch fileanother page on this site to copy
application-specific versions of ini files before executing wlrun. An example
of file copy actions for application XXX:
copy %WinDir%/wlrun7-XXX.ini %WinDir%/wlrun7.ini
copy %WinDir%/wlrun7-XXX.dft %WinDir%/wlrun7.dft
Some defaults you might want to change:
* In the wlrun7.ini file file [output] section, MaxNumberOfOutputMessages= from
10000 to 100000 for long runs. This limits the number of output messages stored
in the database.
* MaxOutputUIRowsToShow limits the amount of messages/errors (lines) displayed
in the Controller’s Output window.
* In the QTWeb.lrp file within the LoadRunner Program Files dat\protocols
folder section [Vugen], add entry MaxThreadPerProcess=5 to limit the number of
threads managed by each load generator mdrv.exe process.
Values for DefaultScenarioDir, DefaultScriptDir,
DefaultResultDir, and [Recent File List] stored in the wlrun5.ini and
wlrun7.dft files updated whenever values are changed within the Controller.
13. The blocks of actions taken by each Vuser are
14. defined in Vu scriptsanother page on this site created using Loadrunner’s
VuGen.exe. When this program is invoked, it stores in the Windows folder a
comparamui.INI file to save under “[LastTablesUsed]” a history of files and
[ParamDialogDates] specified using menu option Insert > New Parameter >
Dates.
VuGen stores and retrieves a vugen.ini file in the Windows
folder. Mercury KnowledgeBase article When using Java, enable additional debug
options:
[DynaDlg]
JavaLevel=3
When using 8.0 scripts within VuGen 8.1, add to Vugen.ini:
[Editor]
OLDEDITOR = 1
VuGen opens in LR folder template/qtweb default.cfg and
script files.
Vu scripts can be coded to use variable values obtained
from parameter files external to the script.
I have a lot more on VuGenanother page on this site here
15. During a run, execution results are stored to a results
folder.
Idea I prefer to set Results Settings to “Automatically create a results
directory for each scenario execution.” which means that LR will increment the
name of the Results Name when I start a scenario runs. For example, a value of
“Res11″ will be automatically incremented to “Res12″ or sometimes “Res11-1″.
Errors are written to the output.mdb MS Access database.
tool See the ASP page I have written to access this databaseanother page on
this site
16. Within each results folder, a “Log” folder is
automatically created to contain a log file for each group. After a run, to
view a log file from within the Controller, click Vusers button then
right-click on a group to select “Show Vuser Log”.
17. As a scenario is run, monitors maintain counters
locally on each host.
18. After a run, the “collate” process takes .eve and .lrr
result files and creates in the results folder a temporary .mdb
(MS-Accessanother page on this site) database.
To prevent errors when processing large result files, use
MSDE (Microsoft SQL Desktop Engine). Don’t install it from the Add-in folder on
the LoadRunner 7.8 CD, which is obsolete SQL7. Download MSDE 2000 Release A
which includes MSDE 2000 Service Pack 3a and MDAC 2.7 SP1a for use by Analysis
on any Windows machine. Extract the file and share that folder. Open a command
window to run a command such as:
setup SAPWD=”StrongPassword” INSTANCENAME=”LR”
SECURITYMODE=SQL DISABLENETWORKPROTOCOLS=0 /L*v path to log file
Using Windows Explorer, share the Data folder.
Then in Analysis Options > Database tab, use 8.3 names without spaces
(indentified with DOS command DIR /X):
1. Input the SAPWD password specified above.
2. Logical Storage location: \\loadclient02\Data (the folder you shared)
3. Physical Storage Location: C:\PROGRA~1\MICROS~1\MSSQL\Data (not C:\Program
Files\Microsoft SQL Server\MSSQL\Data)
4. Click “Test parameters”. (This takes a few seconds)
19. [icon for Analysis module] The Analysis Module (8,320K
analysisu.exe)
20. generates analysis graphs and reports using data from the .mdb database.
21. The LoadRunner Results file results_name.lrr from each scenario run — also
called an Analysis document file — is read by the Analysis program to display
Percentile graphs.
22. By default, the LRReport folder is created in the test analyst’s local
machine My Documents folder to store Analysis Session files.
23. They can optionally be formated in HTML.
24. Their format are controlled by a .tem template file.
25. Optionally, Mercury’s Remote Performance Monitoring
(RPM) MS-IIS/ASP web server for LoadRunner 7.8 can be installed on a Windows
2000 server (Caution! but not on a Windows 2003 server) so that
26. load test results to be viewed using a web browser.
Not pictured is the LoadRunner Tuning Module (a separate $50,000 product).
- 大小: 83 KB
分享到:
相关推荐
**5.4 内部结构** - **组成部分**:Vuser发生器、Controller控制器、Analysis分析器。 - **协同工作**:各组件间紧密配合,实现全面的性能测试流程。 **5.5 测试步骤** 1. **录制脚本**:记录用户操作。 2. **场景...
### LoadRunner性能测试报告知识点详解 #### 一、概述 **编写目的:** - **目的:** 对**xxx系统**的性能进行全面评估,确保系统能够满足预期的性能需求。 - **对象:** 用户、测试人员、开发人员、项目管理者、...
内部结构方面,LoadRunner 包括了控制器(Controller)、虚拟用户生成器(VuGen)、运行时服务器(Run-Time Server)和分析器(Analysis)。Controller 设计和管理测试场景,VuGen 用于录制和编辑脚本,Run-Time ...
6. **集成开发环境**:LoadRunner可以与其他工具集成,如版本控制系统(如Git)、持续集成服务器(如Jenkins),实现自动化测试流程。 7. **性能测试最佳实践**:在使用LoadRunner进行性能测试时,需要合理设置测试...
### 性能测试学习笔记之LoadRunner实战 #### 第1章 一切从零开始 **1.1 拒绝性能测试的理由** 在探索性能测试的过程中,很多人可能会因为种种原因而选择回避或延迟开始。本章节列出了几种常见的拒绝理由,并试图...
软件测试技术实验报告图书管理系统测试报告 ...LoadRunner测试流程包括制定测试计划、开发测试脚本、创建测试场景、分析测试结果和监视性能指标等。LoadRunner测试流程可以帮助开发人员对软件产品进行文档和优化。
1. **Bug状态流程图**:Bug状态流程图是跟踪和管理软件缺陷的过程模型。通常包括新建、已确认、已分配、处理中、已解决、验证通过和关闭等状态。每个状态代表问题的不同阶段,帮助团队理解缺陷处理进度,保证修复的...
这种方法主要关注于软件功能性的验证,而不是内部逻辑或流程。在黑盒测试中,测试用例是基于需求规格说明书来设计的,目标是检查软件是否满足其指定的功能需求。 - **目的**:确保软件按照用户需求工作,发现与规格...
8. **LoadRunner组件与流程**:LoadRunner分为用户动作设计(录制和编辑脚本)、场景设计(定义虚拟用户数量和行为模式)和测试数据分析(监控和分析负载测试结果)。测试流程包括创建脚本、构建场景、运行脚本、...
首先,我们关注“软件测试的基本流程图”。软件测试流程通常包括以下几个阶段:需求分析、测试计划、设计测试用例、执行测试、记录结果、缺陷跟踪和修复、回归测试以及测试报告。需求分析是测试的基础,确保测试目标...
- **性能测试工具**:如LoadRunner、JMeter等。 - **缺陷跟踪工具**:如JIRA、Bugzilla等。 #### 十三、兼容性测试 - **浏览器兼容性测试**:确保网站在不同浏览器中表现一致。 - **设备兼容性测试**:适用于移动...
"地图文件"在测试领域中通常指的是测试场景或测试流程图,它描述了测试步骤和各个步骤之间的关系。在这里,地图文件可能是用来规划和记录登录测试的不同路径,包括成功的登录流程以及无效的等价类。等价类划分是一种...
5. 链接测试:测试所有内部和外部链接是否有效,确保无死链,页面跳转正常。同时,还要确保用户可以通过链接到达预期的目标页面。 6. 表单测试:表单是Web应用中常见的一种用户交互形式,测试人员需要确保表单数据...
7. 测试用例设计方法有边界值分析、等价类划分、业务流程图分析和状态转换分析等。例如,设计登录功能的测试用例时,会考虑正常输入、边界值、异常输入等情况。 8. 设计测试用例的关键在于深入理解业务需求,根据...
在实际工作中,测试人员需要结合自动化测试工具(如LoadRunner、JMeter、Selenium)进行测试,提高效率并减少人为误差。每个测试阶段都需要详尽的测试计划和测试用例,确保覆盖所有可能的用户场景。通过这个全面的...
详细设计则关注每个模块内部的实现逻辑,通常使用伪代码、流程图、类图等技术来描绘。 **编码**阶段是将设计转化为实际可执行程序的过程。在这一阶段,开发人员需要遵循良好的编程规范,选择合适的编程语言和开发...
10. **LoadRunner测试流程**:包括创建测试用例、编写虚拟用户脚本、构建运行场景、执行测试脚本、监控和分析结果。例如,在模拟电商网站的并发测试中,会创建用户登录、浏览和购买的脚本,然后设定并发用户数量,...