Story: Recently I was busy with writing some HP LoadRunner scripts for WebUI. Having no practical experience and being actually a dummy in HP LR in general, I trained myself based on the multiple videos available on YouTube. However, when doing scripts for WebUI I experienced some problems, which are not described well enough somewhere. Therefore, I decided to share my experience here…
1. Manual Correlation
A first thing what you need to do with your script, you need to correlate your script parameters. This means that we need to identify the source for the values and using this source we need to populate our variables.
The process of identifying a proper source for the variable looks like described below.
For instance, you noticed down you are missing a variable REF_ID at line 114. Variable HOST is a defined constant.
We can assume that the variable is coming from the previously executed request or requests. First you need to step over the previously executed request, at the line 77. Then select a tab “Snapshot” – “Recording”. Next, navigate to “Response” area and click CTRL+F.
Copy the value (e.g. bD1lbiZjPTEwMCZkPW1pbg==) from your Excel file and search for all the occurrences of it.
Double-click on the first occurrence in the list.
You are navigated to the place of occurrence.
What do we get from this? It was a redirected GET request, data is located in the response header, within the following line: location: /sap(bD1lbiZjPTEwMCZkPW1pbg==)/bc/bsp/sap/crm_ui_start/default.htm?sap-sessioncmd=open , in between: “()”. And it’s already enough to get this data in runtime, by using the function web_reg_save_param_ex.
We need to place the following code into the lines right BEFORE our request. So lines 59 – 74 should look like below.
|
You can find more details regarding this function here: http://lrhelp.saas.hp.com/en/latest/help/function_reference/Content/web/lrFr_web_reg_save_param_ex.htm
Similar procedures must be performedfor all the variables you defined.
We will consider some common cases that can be relevant for all WebUI HP LR Scripts.
1.1. Getting Referrer ID
Referrer ID is required across complete script, from the login page until log-out.
/* Correlation comment - Do not change! |
1.2. Getting Session ID
Session ID is required across complete script, from the login page until log-out.
/* Correlation comment - Do not change! "RB=)", |
1.3. Getting WCF Request Ticket
WCF Request Ticket is required across complete script, from the login page until log-out.
/* Correlation comment - Do not change!
web_url("main.htm", |
Hint: Symbol \ (back-slash) before the character means that this character should be considered as part of the text string, and not as a “special character”.
Hint: Sometimes you get several values for the same criteria. Therefore while testing and debugging you can set up Ordinal=All to get a clear vision on which value you need. In this case, we wanted the LAST occurrence only.
1.4. Getting Referrer ID (2)
Referrer ID is required across complete script, from the login page until log-out.
/* Correlation comment - Do not change!
web_url("main.htm", |
Hint: Sometimes you get several values for the same criteria. Therefore while testing and debugging you can set up Ordinal=All to get a clear vision on which value you need. In this case, we wanted the LAST occurrence only.
1.5. Getting WCF Request Ticket (2)
Referrer ID is required across complete script, from the login page until log-out.
/* Correlation comment - Do not change! */ |
Hint: Symbols “\r\n” from the above script mean NEW LINE.
1.6. Adding Thinking Time
Often you need to add thinking time in seconds into your script. It can be done using the command lr_think_time()as shown below.
lr_think_time(5); |
You can also influence thinking time by respective runtime settings of your script.
2. Hints
When you test your script you will probably get several errors when processing a logon step or at the very beginning of your script. Next possible issues are related to processing of the popups, especially when they are appearing sequentially one after another. In this case you may not even get any errors in VUGen, but the script execution won’t be successful. This chapter will describe some known cases and the ways to overcome the issues.
The following table contains some common errors and solutions.
| Error | Reason | Solution |
|---|---|---|
HTTP Status Code 400 (Session Timed-Out) | Most probably, your session id ESID or referrer session id REF_ID(n) are not correct. | Check the correlation of ESID and REF_ID parameters. See hint 5. |
HTTP Status Code 403 (Unauthorized Request) | Most probably, your wcf-request-ticket is not correct. | Check correlation of WCF_REQUEST_TICKET(n) parameter. See hints 5 and 6. |
VUGen does not give you any error, but popups are not working. | Most probably you have problems with wcf-request-ticket or referrer session id REF_ID(n). | Check the correlation of REF_ID(n) and WCF_REQUEST_TICKET(n). See hints 5, 6, 7 and 8. |
Hint 1: Always back-up your script.
Hint 2: Never displace the parameters you cannot correlate by other parameters that you think you correlated correctly.
Hint 3: Try to correlate all parameters. If not possible, try to use constants.
Hint 4: Snapshots can be truncated. Use HTTP tracers instead.
Hint 5: Sometimes in VUGen you get several parameters, even though you can see only one in the Snapshot or in HTTPWatch. In this case use option Ordinal = All to get all the variables (VAR_n) and chose the appropriate one later: Ordinal = 1, 2, N, or LAST.
Hint 6: If the right border (parameter RB) for certain variable is NEXT LINE, you need to use “RB=\r\n” in respective web_reg_save_param_ex call.
Hint 7: VUGen does not give you any error, but popups are not working. You should pay attention to referrer ids and wcf-request-tickets, especially for callbackFlashIslands and callbackSilverlightIslands.
"Action={HOST}/sap({REF_ID_2})/bc/bsp/sap/crm_ui_frame/bspwdapplication.do?id=1&wcf-request-ticket={WCF_REQUEST_TICKET_6}",
"Name=wcf-secure-id","Value={WCF_REQUEST_TICKET}",ENDITEM,
"Name=callbackFlashIslands","Value=/sap({REF_ID_2})/webcuif/uif_callback?crm_handler=CL_THTMLBX_FLASH_ISLAND&wcf-request-ticket={WCF_REQUEST_TICKET}",ENDITEM, |
Most probably your have displaced the variables manually (see Hint 2.), or simply the performed correlation does not work (Hints 5 and 6).
Hint 8: For the above (Hint 7) described scenario, you could probably see */logon_error.html call within statistical records, transaction STAD.
Hint 9: Always include logoff and browser closure steps into the script.
Hint 10: To identify if your script is executed successfully or not, do not rely on VUGen. Define functional exit criteria and check them on the back-end. For instance if you create 1Order documents, check if they are being created in the table CRMD_ORDERADM_H.
P.S. If you have some interesting case, issue or error, feel free to add it here.
BR, Dima
![2016-05-31 08_54_24-Launch Transaction - [SAP] - Internet Explorer.png](http://scn.sap.com/2016-05-31%2008_54_24-Launch%20Transaction%20-%20%5BSAP%5D%20-%20Internet%20Explorer.png)