录制https://wap.daishubank.com/网站扣,回放时报错。
脚本如下:
web_url("https://wap.daishubank.com/","URL=https://wap.daishubank.com/",LAST);
进行回放操作,信息如下:
Starting iteration 1.
Starting action Action.
Action.c(6): Error -27780: [GENERAL_MSG_CAT_SSL_ERROR]connect to host "wap.daishubank.com" failed: [10054] Connection reset by peer [MsgId: MERR-27780]
Action.c(6): Warning -26000: Empty or no response for URL="https://wap.daishubank.com/" [MsgId: MWAR-26000]
Action.c(6): web_url("https://wap.daishubank.com/") highest severity level was "ERROR", 0 body bytes, 0 header bytes [MsgId: MMSG-26388]
Ending action Action.
Ending iteration 1.
截图如下:
网上并未查到与之相同的问题,很接近的一篇文是一位刚进阿里不久的牛人(http://bbs.51testing.com/thread-107301-1-1.html),按照其方面还真的可以回放了,谢谢这位大牛!!
http://www.wilsonmar.com/1loadrun.htm
If an Web SSL script works in the Controller but not vuGen, try changing the controller's Runtime Settings Preferences to "WININET replay instead of Sockets".
现贴出相关解决方法:
在vugen 内, run-time settings->preferences->勾上WININET replay instead of Sockets。
原理:
vugen user's guide 提到 Advanced Web run-time options
WinInet Replay (instead of Sockets): Instructs VuGen to use the WinInet
replay engine. VuGen has two HTTP replay engines: Sockets-based (default)
or WinInet based. The WinInet is the engine used by Internet Explorer and
it supports all of the features incorporated into the IE browser. The
limitations of the WinInet replay engine are that it is not scalable, nor does
it support UNIX. In addition, when working with threads, the WinInet
engine does not accurately emulate the modem speed and number of
connections.
VuGen's proprietary sockets-based replay is a lighter engine that is scalable
for load testing. It is also accurate when working with threads. The
limitation of the sockets-based engine is that it does not support SOCKS
proxy. If you are recording in that type of environment, use the WinInet
replay engine.
从上可知,winInet replay 支持集成如IE的所有特征。回放时,底层的winInet函数完成SSL握手过程。同时每种mode均有优劣。
另外,找到一些说明:
Any Web script can be replayed in LoadRunner in two modes:
1. WinInet Mode - Using the WinInet.dll provided by Internet Explorer.
2. Socket mode - Using the Sockets Replay engine developed by Mercury.