vuser_init()
{
ctrx_set_connect_opt(APPLICATION, "#Hyperspace 2010-SUP");
ctrx_set_connect_opt(NETWORK_PROTOCOL, "TCP/IP + HTTP");
ctrx_connect_server("64.54.43.254:1494", "loadrunner1", lr_decrypt("4d65322c54bf1230aeed14fc637d1a"), "ucsfmc", CTRX_LAST);
ctrx_wait_for_event("LOGON", CTRX_LAST);
lr_think_time(7);
ctrx_sync_on_window("Hyperspace - UCSF SUP", ACTIVATE, 64, 39, 1025, 768, "", CTRX_LAST);
ctrx_type("ipuc", "", CTRX_LAST);
ctrx_key("TAB_KEY", 0, "", CTRX_LAST);
ctrx_type("model", "", CTRX_LAST);
ctrx_key("ENTER_KEY", 0, "", CTRX_LAST);
ctrx_key("ENTER_KEY", 0, "", CTRX_LAST);
lr_think_time(9);
ctrx_sync_on_window("Hyperspace - 14L MEDICINE - UCSF SUP - CLERK I.", ACTIVATE, 98, 9, 1025, 768, "", CTRX_LAST);
ctrx_mouse_click(242, 35, LEFT_BUTTON, 0, "Hyperspace - 14L MEDICINE - UCSF SUP - CLERK I.", CTRX_LAST);
lr_think_time(4);
ctrx_mouse_click(271, 329, LEFT_BUTTON, 0, "Hyperspace - 14L MEDICINE - UCSF SUP - CLERK I.", CTRX_LAST);
ctrx_mouse_click(945, 230, LEFT_BUTTON, 0, "Hyperspace - 14L MEDICINE - UCSF SUP - CLERK I.", CTRX_LAST);
ctrx_type("t", "", CTRX_LAST);
ctrx_key("TAB_KEY", 0, "", CTRX_LAST);
ctrx_type("n", "", CTRX_LAST);
ctrx_key("TAB_KEY", 0, "", CTRX_LAST);
ctrx_key("TAB_KEY", 0, "", CTRX_LAST);
ctrx_key("TAB_KEY", 0, "", CTRX_LAST);
ctrx_type("3", "", CTRX_LAST);
ctrx_key("TAB_KEY", 0, "", CTRX_LAST);
lr_think_time(10);
ctrx_mouse_click(987, 716, LEFT_BUTTON, 0, "Hyperspace - 14L MEDICINE - UCSF SUP - CLERK I.", CTRX_LAST);
ctrx_mouse_click(997, 111, LEFT_BUTTON, 0, "Hyperspace - 14L MEDICINE - UCSF SUP - CLERK I.", CTRX_LAST);
ctrx_mouse_click(976, 31, LEFT_BUTTON, 0, "Hyperspace - 14L MEDICINE - UCSF SUP - CLERK I.", CTRX_LAST);
ctrx_mouse_click(1014, 10, LEFT_BUTTON, 0, "Hyperspace - UCSF SUP", CTRX_LAST);
ctrx_disconnect_server("64.54.43.254:1494", CTRX_LAST);
return 0;
}
NS
--
You received this message because you are subscribed to the Google "LoadRunner" group.
To post to this group, send email to LR-Loa...@googlegroups.com
To unsubscribe from this group, send email to
LR-LoadRunne...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/LR-LoadRunner?hl=en
Hi Chaithanya,Regarding your comment ,
2. Install Citrix agent on the server box to increase the robustness of your script. Citrix agent allows Loadrunner to recognize application objects such as buttons and fields by their properties. This increases the accuracy of object activation during script replay.
I am using Citrix Xen App 6.0 hosted on Windows server 2008.Lr 11.0 on Windows server 2003.I want to install LR citrix agent on Citrix Server,Let me know is it compatible , if it is compatible please help me in installing it.Thanks in advanceRajasekhar
Chaitanya,is it required to install LR 11.0 on windows server 2008 and then install the Citrix agent which is in Additional components (or) only installing Citrix agent which is in additional components is enough.
Also, there are 2 Loadrunner Citrix agents. Be sure to install the 64 bit agent which was added to support in January.
Noelle
I logged a ticket with support to find out how to parameterize a Citrix script this was their response:
For the Citrix section, you can create parameters normally and replace certain values in the script.
For example :
Ctrx_type("shellfish", "", CTRX_LAST);
You could create a parameter for the value of shellfish, resulting in :
Ctrx_type("{DATA_PARAM_1}", "", CTRX_LAST);
Values in the ctrx_type function ( from your script : ‘fammd’, ‘model’, ‘test’, ‘98.5’, ‘shellfish’, ‘shee’, ‘llfish’; which are your input data ) can be parameterized.
Correlation doesn’t exist in Citrix, since there is a synchronization via bitmaps.
Hope it helps!
Noelle
From: chaitanya bhatt [mailto:bhatt.c...@gmail.com]
Sent: Thursday, February 24, 2011 4:28 AM
To: raja sekhar
Cc: lr-loa...@googlegroups.com; Stimely, Noelle
Subject: Re: How Do you Parameterize a Citirix Script?
Only agent installation is sufficient. Remember to inform the client about the additional memory and CPU usage consumed by this agent on the server. ~2mb of physical memory space is consumed per vuser by ctrxagent.exe process during test execution. You can see this agent process spawned during load test from via task manager in the Win 2008 server. So if you are running a 20vu test then 20*2 mb of space will used in the server only for ctrxagent.exe process. You will have to carefully deal with this issue. Inform you client about the pros and cons of using this agent on this server. It will affect your test results significantly however this is the only way you can create a relatively robust citrix loadrunner script. The problem is choosing between testing approach against accuracy of test result.