LoadRunner基本问题：记录流量还是浏览器操作？
我找不到有关 LoadRunner 的基本信息：它是否记录浏览器操作（如 QTP）或网络流量（我的意思是数据包嗅探？）。 我不清楚，因为有类似于 QTP 对象操作的脚本视图。但另一方面，运行测试时没有打开浏览器。 我需要了解它是如何工作的，提前谢谢您！
I cannot find the basic information about LoadRunner: does it record browser actions (like QTP) or network traffic (I mean packet sniffering?).
It is not clear to me since there is Script view that resembles QTP object actions. But on the other hand there is no browser opened when running the tests.
I would need to understand how it works, thank you in advance!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
VuGen 在协议级别记录流量。这意味着从 TCP 角度“看到的”所有流量都会受到检查。我假设您想了解此处的 HTTP(S) 记录，因为您谈论的是浏览器。
HTTP(S) 可以通过多种不同的方式进行记录，但所有方式都会生成一个记录日志，然后检查该日志并基于该日志“生成”脚本。在“记录日志”和“生成日志”选项卡中，您可以看到记录的实际流量以及脚本的生成方式。
运行脚本时，生成的命令将原始 HTTP(S) 请求发送到目标服务器，无需任何 UI。根据请求模式，还可以检查结果数据是否引用其他资源，例如图像、css 或 js 文件等。
VuGen records the traffic on a protocol level. This means that all traffic "as seen" from TCP perspective is inspected. I will assume you want to understand the HTTP(S) recording here since you talk about browsers.
HTTP(S) can be recorded in a number of different ways, but all result in a recording log that is then inspected and the script is "generated" based on that. In the "Recording Log" and "Generation Log" tabs you can see the actual traffic recorded and how the script was generated.
When running a script the commands generated send the raw HTTP(S) requests to the target server, without any UI. Depending on the request mode the resulting data may also be inspected for references to other resources, such as images, css or js files etc.
它根据所选协议记录两者（然后记录一些）。请记住，LoadRunner 可以作为 GUI 虚拟用户执行 QTP 脚本。它还可以在客户端界面之外的层执行 Citrix 和远程桌面协议脚本。
它还可以记录各种级别的应用程序和表示层协议，一直到 Winsock 级别，
It records both (and then some) depending upon the protocol selected. Keep in mind that LoadRunner can execute QTP scripts as GUI Virtual Users. It can also execute Citrix and Remote Desktop Protocol Scripts at a layer even outside of the client interface.
It can also record at a variety of levels of application and presentation layer protocols, all the way down to the Winsock level,