LoadRunner案例分析

1、LoadRunner案例分析（一） 來源： 作者： 日期：2008-06-16 【聚杰網(wǎng)測(cè)試工具】LoadRunner案例分析（一） 昨天和Zee兄交流的時(shí)候，探討了最近無憂測(cè)試論壇上的兩個(gè)問題，我們倆的看法基本一致。第一個(gè)問題：是如何利用LoadRunner判斷HTTP服務(wù)器的返回狀態(tài)。 兩種方法，第一種方法是利用LR的內(nèi)置函數(shù)web_get_int_property， 如下是一個(gè)簡(jiǎn)單的例子： Action.cint HttpRetCode;web_url(”my_home”, “URL=http:/my_home”, “TargetFrame=_TOP”, LAST);HttpRetCod

2、e = web_get_int_property(HTTP_INFO_RETURN_CODE);if (HttpRetCode = 200)lr_log_message(”The scrpt successfully accessed the My_home home page”);elselr_log_message(”The scrpt failed to access the My_home home page “); 另外一種就是最原始的辦法，也是Zee兄這種高手才最先想到的，自己取HTTP服務(wù)器的數(shù)據(jù)，然后利用關(guān)聯(lián)函數(shù)分析啊。 （果然是高?。?。 其實(shí)所有的東西都可以從服務(wù)器的返回取，

3、然后自己動(dòng)手解析，呵呵。 舉個(gè)不太恰當(dāng)?shù)睦樱?你需要一套家具，可以去家具市場(chǎng)挑，當(dāng)然也可以自己買木材原料和工具，動(dòng)手加工。 那才是最合乎自己需要的。第二個(gè)問題：動(dòng)態(tài)數(shù)據(jù)參數(shù)化的問題。其實(shí)第一次看到這個(gè)問題，我沒有馬上反應(yīng)過來，后來仔細(xì)想想， 明白了。 就是需要參數(shù)化的數(shù)據(jù)不是靜態(tài)的，是動(dòng)態(tài)的。 比如從數(shù)據(jù)庫(kù)中選出來的。針對(duì)這個(gè)問題，我跟Zee兄弟的看法一致，應(yīng)該提前從數(shù)據(jù)源（比如數(shù)據(jù)庫(kù)）把數(shù)據(jù)選取出來，然后在執(zhí)行的時(shí)候直接進(jìn)行參數(shù)化的選取。 反之，如果在程序執(zhí)行期間，進(jìn)行數(shù)據(jù)的選取，將可能帶來數(shù)據(jù)庫(kù)服務(wù)器的強(qiáng)大壓力，因?yàn)閰⒓硬l(fā)執(zhí)行的每個(gè)虛擬用戶都去數(shù)據(jù)庫(kù)搜刮一下，對(duì)數(shù)據(jù)庫(kù)將是多么嚴(yán)峻的考驗(yàn)

4、啊。朋友或者同事之間的探討是加深對(duì)問題理解和增加知識(shí)面，擴(kuò)展視野最直接的途徑和方法，加強(qiáng)溝通，keep in touch.LoadRunner案例分析（二）昨天在廣州交流會(huì)開始之前，一個(gè)朋友問起這樣一個(gè)問題：他們公司的系統(tǒng)上線以后，用戶分布在各個(gè)不同的地區(qū)，而且接入系統(tǒng)的方式和帶寬也不同，這種情況下進(jìn)行性能測(cè)試，如何保證更加真實(shí)的模擬用戶行為？用LoadRunner可以做到嗎？回答當(dāng)然是肯定的，其實(shí)這些都是簡(jiǎn)單問題的組合，這樣的問題考察的也是你對(duì)工具的熟悉和掌握程度。在VUGen里面，是可以通過RTS （runTimeSetting）來模擬一個(gè)單個(gè)用戶更加真實(shí)的行為，比如思考時(shí)間，網(wǎng)絡(luò)帶寬，是

5、否清除cache等等。同樣的設(shè)置也可以在場(chǎng)景中進(jìn)行設(shè)置。而且LoadRunner提供設(shè)置不同用戶組不同RunTimeSetting的功能。以達(dá)到模擬不同用戶行為的更加真實(shí)組合。假設(shè)有三種不同帶寬的用戶，而且上傳和下載的帶寬也有所不同，那么可以錄制兩個(gè)腳本，分別模擬上傳和下載的用戶行為，再Controller里面，建立六個(gè)不同的腳本組，腳本組的用戶數(shù)可以按照絕對(duì)或者百比分的方法分布。比如100，50，200用戶或者20%，40%，40%等，這取決于你的業(yè)務(wù)模型。然后設(shè)置不同的帶寬和分布情況。這樣不同用戶組的虛擬用戶模擬出來的就是不同帶寬的用戶實(shí)際接入情況。就可以滿足之前的問題的要求LoadRun

6、ner案例分析（三） 來源： 作者： 日期：2008-06-16 【聚杰網(wǎng)測(cè)試工具】LoadRunner案例分析（三） 把昨天的功課補(bǔ)了，本來打算昨天分析一個(gè)典型案例，可惜太忙了。所以這么說。以前一直沒有解決的問題，利用LoadRunner測(cè)試一個(gè)應(yīng)用的時(shí)候，需要驗(yàn)證域用戶，所以即使錄制成功，每次回放的時(shí)候都提示錯(cuò)誤，用戶名和密碼不對(duì)，對(duì)此耿耿于懷了很久。今天居然解決了。解決方法就是一個(gè)簡(jiǎn)單的函數(shù)調(diào)用： web_set_user，此函數(shù)的解釋和用法如下： The web_set_user function is a Service function that specifies a login

7、 string and password for a Web server or proxy server. It can be called more than once if several proxy servers require authentication. web_set_user overrides the run-time proxy authentication settings for user name and password.When you log onto a server that requires user and password validation，

8、VuGen records a web_set_user statement containing the login details. However， there are some more stringent， authentication methods for which VuGen is unable to insert web_set_user statements. See User Authentication for more detail. In such cases， you can add web_set_user into your scrpt manually.W

9、hen you run the scrpt， LoadRunner automatically submits the user authorization along with every subsequent request to that server. At the end of the scrpt， LoadRunner resets the authorization.This function is supported for all Web Vusers， and for WAP Vusers running in HTTP mode only. It is not suppo

10、rted for WAP Vusers running in Wireless Session Protocol （WSP） replay mode.Example 3The following example was inserted manually by the user into the scrpt as the Web server “mansfield” uses NTLM authentication. VuGen cannot record NTLM or Digest authentication. Note that for NTLM authentication the

11、domain name “mansfield” followed by a double backslash must be prepended to the user name：web_set_user（“mansfield/freddy”， “XYZ”， “mansfield：80）； 原來一直沒有想到域的設(shè)置，結(jié)果一直不行，現(xiàn)在可以了。另外一個(gè)問題跟之前這個(gè)有關(guān)系，那就是驗(yàn)證碼的問題，之前曾經(jīng)看過段念（關(guān)河大俠）的關(guān)于驗(yàn)證碼的是三個(gè)解決方案，這里是第四種解決方案。對(duì)于一些比較簡(jiǎn)單有規(guī)律的驗(yàn)證碼可以搞定。對(duì)于復(fù)雜的比如有干擾的，或者沒有規(guī)律的則參考關(guān)大俠的其他解決方案。這個(gè)應(yīng)用經(jīng)過源代碼分

12、析，發(fā)現(xiàn)每次客戶端請(qǐng)求過來的驗(yàn)證碼都可以取到，格式如下固定，是四個(gè)數(shù)字的組合。經(jīng)過多次嘗試發(fā)現(xiàn)如下規(guī)律：驗(yàn)證碼如下： 52|52|52|51|46|47|49|55|對(duì)應(yīng)界面的驗(yàn)證碼是： 6039規(guī)律是第2，5，8，9位的值減去46對(duì)應(yīng)的即是驗(yàn)證碼有了這個(gè)規(guī)律，就可以通過關(guān)聯(lián)提前取得服務(wù)器的驗(yàn)證碼，然后通過簡(jiǎn)單的計(jì)算，得到結(jié)果。詳細(xì)代碼如下： #include "web_api.h"Action() / char* str = “52|52|52|51|46|47|49|55|”;char result64;int num1;int num2;int num3;int nu

13、m4;int temp1;int temp2;int temp3;int temp4;web_set_user(”XXXXDomain/szXXXX”,lr_decrypt(”46246a2633f042c67758b9ddc2b863038aa063c03d7e”),“XXXX.XXXX:8080);web_reg_save_param(”check”, “LB=Image=”, “RB=/”, LAST);web_url(”Register”,“URL=http:/XXXX.XXXX:8080/xx/main/Register”,“Resource=0,“RecContentType=te

14、xt/html”,“Referer=”,“Snapshot=t1.inf”,“Mode=HTML”,LAST);lr_think_time( 6 );sscanf(lr_eval_string(”check”), “%d|%d|%d|%d|%d|%d|%d|%d”, &temp1, &num1, &temp2, &temp3, &num2, &temp4, &num3, &num4);num1 -= 46;num2 -= 46;num3 -= 46;num4 -= 46;sprintf(result, “%d%d%d%d”, nu

15、m1, num2, num3, num4);lr_log_message(”getvalue : %s”, result);web_submit_form(”Register;jsessionid=6726009A7D21963602B166D91C883413,“Snapshot=t2.inf”,ITEMDATA,“Name=Register.reason”, “Value= “, ENDITEM,“Name=set_attach”, “Value=result”, ENDITEM,LAST);return 0; LoadRunner案例分析（四） 來源： 作者： 日期：2008-06-16

16、 【聚杰網(wǎng)測(cè)試工具】LoadRunner案例分析（四） 最近在論壇上看到幾次這樣的問題，今天突然想起來，覺得比較典型，有必要分析一下。這個(gè)問題的具體描述大概是這樣的：在web應(yīng)用下，模擬十個(gè)用戶并發(fā)進(jìn)行數(shù)據(jù)的添加，結(jié)果每次執(zhí)行全部成功，但是數(shù)據(jù)卻不是十條，每次數(shù)據(jù)不一樣，但是都比十小。乍一看，可能是數(shù)據(jù)參數(shù)化的問題，其實(shí)仔細(xì)想想，道理其實(shí)很簡(jiǎn)單。是數(shù)據(jù)庫(kù)的問題。大多數(shù)的數(shù)據(jù)庫(kù)都有記錄鎖的問題，第一次的數(shù)據(jù)操作沒有commit之前，第二次對(duì)同樣表進(jìn)行的操作可能就沒有辦法成功。所以每次數(shù)據(jù)的條數(shù)都達(dá)不到十條。但是為什么每次都不一樣呢？這個(gè)問題也容易解釋，因?yàn)槊看蔚牟僮鞣?wù)器的響應(yīng)時(shí)間是不同的，所以

17、不同虛擬用戶的提交時(shí)間也不是不同的，這樣一來，就導(dǎo)致每次提交成功的數(shù)據(jù)量不一致。導(dǎo)致每次結(jié)果的條數(shù)可能是不同的。其實(shí)這個(gè)問題，跟LoadRunner的使用并沒多大關(guān)系，而主要是對(duì)數(shù)據(jù)庫(kù)的了解和應(yīng)用執(zhí)行機(jī)制的了解。如何解決這個(gè)問題，我現(xiàn)在還沒有好的思路，是否對(duì)應(yīng)用程序?qū)憯?shù)據(jù)庫(kù)的過程作一些改進(jìn)？大家可以一起探討LoadRunner案例分析（五） 來源： 作者： 日期：2008-06-16 【聚杰網(wǎng)測(cè)試工具】LoadRunner案例分析（五） 最近被一個(gè)代理的問題搞的糾纏不清。我這個(gè)人其實(shí)很多時(shí)候是不求甚解的那種。自打上次跟Zee版主交流了以后，很受打擊，慚愧的要命。打算以后改改這個(gè)毛病。凡是要探個(gè)

18、究竟，正所謂懲前毖后，治病救人嘛。問題是這樣的，VUGen里面錄制的腳本，回放的時(shí)候出錯(cuò)，錯(cuò)誤信息是：Net An. Warning （ 218： 9f0） Request Connection： Remote Server 47：80 （Service=） Failed attempt #3. Unable to connect to remote server： rc = -1 ， le = 0）Net An. Error （ 218： 9f0） Request Connection： Remote Server 47：80 （Service=） N

19、OT PROXIED！ （REASON： Unable to connect to remote server： rc = -1 ， le = 0）重新安裝了LoadRunner，結(jié)果同樣。從錯(cuò)誤的表面看是代理的問題，但是本機(jī)上網(wǎng)不需要任何代理。也沒有設(shè)置任何的代理。搜了一下，發(fā)現(xiàn)了問題的解決方法。其實(shí)挺搞笑的。居然是殺毒軟件的問題。下面是詳細(xì)的討論經(jīng)過（英文的，大家將就看，看不懂就查查辭典）= Ive installed LR on a new machine and Im encountering an error at record time. This is the error as

20、recorded against loading the Google home page， along with the three warnings that proceed it：Net An. Warning （ 218： 9f0） Request Connection： Remote Server 47：80 （Service=） Failed attempt #1. Unable to connect to remote server： rc = -1 ， le = 0）Net An. Warning （ 218： 9f0） Request Connection

21、： Remote Server 47：80 （Service=） Failed attempt #2. Unable to connect to remote server： rc = -1 ， le = 0）Net An. Warning （ 218： 9f0） Request Connection： Remote Server 47：80 （Service=） Failed attempt #3. Unable to connect to remote server： rc = -1 ， le = 0）Net An. Error （ 218： 9f0

22、） Request Connection： Remote Server 47：80 （Service=） NOT PROXIED！ （REASON： Unable to connect to remote server： rc = -1 ， le = 0）Ive reinstalled LR twice with the same results.One other thing Ive noticed is that under Run-time Settings， the browser emulation was set to IE 4 and no O/S. I in

23、stalled LR on a second machine and the setting is IE 6/NT 5.1. The recorder also worked as expected. However this is an older box and Id rather not use it.The Mercury forums point to possible spyware， but the new machine is clean. If anyone has any information it would be most appreciated. 1. What v

24、ersion of LoadRunner or PerformanceCenter are you using？ 2. What is the protocol you are recording？ HTTP/HTML2.1 If HTML - are you using HTML-Advanced with URLs or， NO2.2 URL mode with Concurrent groups， or NO2.3 URL mode without Concurrent groups？ NO3. Which LoadRunner/PerformanceCenter feat

25、ure or service packs are you using？ None4. What kind of LoadRunner license do you have - Subscrption， Perpetual， Virtual User days， or Evaluation？ （choose the one that fits your license model） Evaluation4.1 If subscrption， is subscrption current or expired？5. What platform（s） and Operating Systems？

26、Include version and service packs. IE 6.0 SP2 and XP SP 26. If you have filed a service request with Mercury， what have they told you at this point with respect to your issue？Ill be filing an SR today.Thanks，DanDan， since you are using the evaluation version， please turn your questions to your field

27、 sales engineer for HP|Mercury or your VAR for assistance prior to your sale. It is their job to make sure all engineering issues are addressed prior to your purchase of LoadRunner， just as it is the sales representatives job to make sure all organizational and logistical issues are addressed prior

28、to your purchase. If your VAR or vendor sales engineer is unresponsive to your inquiries， then seek a new representative to work with. However， it has been my experience that a slight threat to go with another vendor that can better support your environment tends to light the fire under most sales t

29、ypes， particularly with a product like LoadRunner that easily can exceed $100，000.00 USD when optioned out.Thank you for your interest in evaluating LoadRunner prior to your purchase.James Pulley=Thanks for the suggestion.The controller license is purchased and this is the machine designated for act

30、ivation. Im dealing with Mercury on this issue as well.This is not the first time Ive had installation issues with a Mercury product and Im sure it wont be the last. As I mentioned this is a new laptop so maybe that has something to do with it. But Ive seen one other post in this forum describing my

31、 same problem and there was no resolution so Im not optimistic that this will be resolved quickly.If Mercury/HP provides a solution Ill post it here.=A Mercury engineer provided a workaround for this recording error. Under Tools -> Recording Options -> Network -> Port Mapping， the capture l

32、evel was changed from Socket Level Data to WinINet level data。When I get the fix for Socket Level Data recording error on this PC， Ill post it here.Dan=Thanks， Dan. You may not know it， but it all too rare for people to come back and post solutions， so we are truly grateful.=Thanks for that Peter. I

33、 find it worthwhile to post resolutions as I hope they can help others.So I solved my problem. Digging into the process explorer pointed to the biolsp.dll from Wave Systems. I Googled it and found several discussion forums indicating it causes problems with other applications as well. The patch down

34、load link on the Wave website was dead. I dont need bio security on my Dell so I uninstalled the whole program group. VUGEN is now working as expected.Good luck to all，Dan=so let me get this straightyou have to disable the bio security on the computer to get it to work？ Seems like an interesting pro

35、blem if you are required to have the security on as a company policy.=Thats a great point jamesso and I agree； this wasnt the solution I was looking for. Unfortunately there is more going on here. We aquired a term license with Mercury/HP and it activated the virtual users two weeks ago， even though

36、 the installation on the controller did not go as planned. But Im at the point now where weve already burnt too much and cant afford to burn any more of the license. I have to get back on track with the client so Im going with this for now.Regards，Dan=So the term license started before you could act

37、ually get a controller working to use them。hmmm. Is HP flexible enough to own this problem and give you time that you lost？=Time will tell jamesso. I do want that time back and I am looking for consideration， but at this point Im not optimistic.I dont mind saying at this point that I was unhappy wit

38、h being tied to a start date to begin with. This is the first time Ive worked with a term license from HP and I would be very happy if it is my last. In my previous term engagements I used Segue/Borland. With their model I activated the license the day I was ready which got the project more value， m

39、ore flexibility， and less waste.=Hi Dan，i had same problem with new LR 8.1 installation with trial 10 days licensesand my friend with 8 years LR experience say me possible solution（99%）：you need to disable（sometimes uninstall） any antivirus software during installation process （LR need to notify USE

40、R before starting installation process， but i not find it），after restart the PC you can to enable AV again.Try and Enjoyloadrunner8.1一次簡(jiǎn)單的實(shí)踐來源： 作者： 日期：2008-06-16 【聚杰網(wǎng)測(cè)試工具】loadrunner8.1一次簡(jiǎn)單的實(shí)踐 一、分析應(yīng)該系統(tǒng) 1.硬件環(huán)境： 硬件名稱 CPU 內(nèi)存 硬盤 服務(wù)器 Pentium(R) 4 2.66 GHz(雙核) 1G 80G WEB服務(wù)器 賽揚(yáng)1.7GHz 256M 40G 測(cè)試機(jī)器 Pentium(R

41、) 4 2.66 GHz 760M 80G 2.軟件環(huán)境： 硬件名稱 操作系統(tǒng) 應(yīng)用軟件 版本 數(shù)據(jù)庫(kù)服務(wù)器 WindowsXP sp2 Oracle 9i. WEB服務(wù)器 Windows2000 sp4 WebLogic 8.1 測(cè)試機(jī)器 WindowsXP sp2 8.1 3.網(wǎng)絡(luò)環(huán)境： 采用局域網(wǎng)； 4.系統(tǒng)、應(yīng)用軟件配置環(huán)境： 操作系統(tǒng)、Oracle、WebLogic各參數(shù)采用默認(rèn)設(shè)置；二、壓力測(cè)試的對(duì)象及目標(biāo) 1.測(cè)試對(duì)象： 教學(xué)平臺(tái)課程通知部分； 2.測(cè)試目標(biāo)： 測(cè)試得到點(diǎn)擊通知時(shí)的最大并發(fā)人數(shù)； 三、壓力測(cè)試過程 1.錄入腳本、增強(qiáng)腳本 前提：采用WEB（HTTP/

42、HTML）協(xié)議錄入腳本； 錄入腳本并通過驗(yàn)證回放； 在課程通知處插入集合點(diǎn)，為了實(shí)現(xiàn)并發(fā)訪問課程的目的； 集合點(diǎn)：是一個(gè)并發(fā)訪問的點(diǎn)，在LoadRunner中可以通過在提交數(shù)據(jù)操作前面加入集合點(diǎn)，這樣當(dāng)虛擬用戶運(yùn)行到提交數(shù)據(jù)的集合點(diǎn)時(shí)，LoadRunner 就會(huì)檢查同時(shí)有多少用戶運(yùn)行到集合點(diǎn)，如果不到事先定義人數(shù)，LoadRunner就會(huì)命令已經(jīng)到集合點(diǎn)的用戶在此等待，當(dāng)在集合點(diǎn)等待的用戶達(dá)到事先定義的人數(shù)時(shí)，LoadRunner 命令這些人同時(shí)去提交數(shù)據(jù)，并發(fā)訪問的目的。 在課程通知處插入檢查點(diǎn)，以驗(yàn)證訪問的頁(yè)面里的文字的準(zhǔn)確性； 此處因?yàn)槭窃L問類的腳本，一定要添加檢查點(diǎn)，以保證在測(cè)試時(shí)結(jié)果的正確性。因?yàn)長(zhǎng)R只要檢測(cè)到網(wǎng)頁(yè)的響應(yīng)，就認(rèn)為是pass而并不管當(dāng)前網(wǎng)頁(yè)內(nèi)容的正確性。在進(jìn)行壓力測(cè)試時(shí)，為了檢查Web服務(wù)器返回的網(wǎng)頁(yè)是否正確，VuGen允許我們插入Text/Imag 檢查點(diǎn)，這些檢查點(diǎn)驗(yàn)證網(wǎng)頁(yè)上是否存在指定的Text或者Image，還可以