Skip to main content


Showing posts from October, 2013

How to check the duration of transaction in the middle of execution in vugen?

You can check the duration of transaction in middle of the execution in vugen by using the following method. For example, in the middle of the execution the user wants to check the response time of a transaction. If the user found that the response time is more than 10 seconds the user wants to stop the transaction else continue with the execution of the script. This can be achieved using lr_stop_transaction and lr_resume transaction. lr_stop_transaction function will not end a transaction but it stops the timing of a transaction. It is useful for validating purposes. You can include a conditional statement after calling the stop function as shown in the below example. Example: Start transaction. request Sent. Stop transaction(lr_stop_transaction). Take the duration of the transaction. If it is more than 10 seconds stop the transaction. Else. Continue with the transaction(lr_resume_transaction). Script Example: Action() {     double  dur;     lr

lr_start_transaction Usage and Dynamic Transactions Generating withExamples

Why do you use lr_start_transaction? It is mainly used to check the response time of a particular request. Enter or, how much time Google or Bing has taken to load the page. How to use lr_start_transaction? lr_start_transaction to be inserted before beginning of a request/transaction, which you need to analyse the request/transaction. Lr_start_transaction and lr_end_transaction are inserted before and after the request. Each lr_start_transaction must have corresponding lr_end_transaction, otherwise vugen will consider as illegal statement. Note: Do not use period(.) in transaction names. Period indicates end of transaction in vugen and analysis. In this following example, lr_start_transaction starts a transaction whose purpose is to measure the response time of (How much time it take to load a page). Example: lr_start_transaction(Loadrunnerz_Home_Page); web_url("Loadrunnerz", "URL=

Checklist to Follow Before and After the Script Development in Vugen

In order for the vugen scripts to be developed properly. It is better to maintain a checklist and also make sure you meet your internal company standards. If you don’t have one, prepare one as following. Please share in the below comments if you have and add if I miss anything in the checklist. Before start of recording the script make sure you select the proper run time settings. Insert the proper action names and transaction names where and when necessary. Make sure to insert proper comments where and when necessary. All values that need to be correlated must be correlated. Add text checks using web_reg_find or web_find wherever necessary in the script. Make sure all the requests are included in between lr_start_transaction and lr_end_transaction. Make sure that the script runs without any errors and warnings. Make sure you have done all the values that need to be parameterized are parameterized and have selected correct setting in the parameterization settings. Before up

Sitescope Monitoring Tool Features and Monitors

Why Sitescope is called Agentless Monitoring Tool? HP SiteScope monitors the application/infrastructure/server/operating system without installing any agent software on the system to be monitored. This feature makes the installation, usage and maintenance of Sitescope simpler when compared with the any performance monitoring tools like Diagnostics. Sitescope Monitors: Sitescope has also upgraded and changed drastically to meet the rapidly changing technologies and environments like virtualization and cloud computing. Using Sitescope we can monitor different web servers, application servers and database servers. We can also monitor operating systems Windows, Linux, Sun Solaris, IBM AIX. It has more than 100 monitors including Weblogic, Websphere, SAP, SIEBEL, SNMP, LDAP, Network Monitor etc. HP SiteScope can also monitor cpu utilization, response time, disk space, and resource availability of a variety of host types and application platforms. Sitescope Features:

Lr Convert String Encoding Function Usage in Loadrunner with Examples

lr_convert_string_encoding=convert a string to a different encoding. By using this Loadrunner function we can convert string to following formats Unicode UTF8 System Locale The function saves the result string, including its terminating NULL, in the parameter name. Printable characters in the Output result string are displayed in VuGen and its logs as the actual characters. Non-printable characters are displayed in Hexadecimal. For example: rc = lr_convert_string_encoding("A", NULL, LR_ENC_UTF8, "stringInUnicode"); The output in the vugen string displays as A\x00, and not \x41\x00, because A is a printable character. Add lr_convert_string_encoding is not recorded during recording. We need to insert manually when needed. Script in Vugen: Action() { int rc = 0; //Convert String to Unicode in Loadrunner rc = lr_convert_string_encoding("Hello world", LR_ENC_SYSTEM_LOCALE, LR_ENC_UNICODE, "stringInUnicode"); // Convert Str

lr advance param Function in Loadrunner with Example

This function is not recorded during recording. We manually insert this function whenever there is a need of it. lr_advance_param works depends upon the settings we give in parameter list (ctrl+L). lr_advance_param is like update value on each occurrence. Whenever we want to update a parameter value in the same iteration we use lr_advance_param. For example when we want to use two parameters Google and Bing in one Iteration. Usually the Vugen takes the first value google and if we want to use the second value in the same iteration we use update value on each occurrence in the parameter settings. We can do the same using lr_advance_param function. Example: I have set following settings in Parameter Select Next Row: Sequential Update value on: Each Iteration If we want to take the next value in the pramater list we use lr_advance_param as shown below. Parameter Name: DomainName Google Bing Yahoo Ask Vugen Script: Action () { web_url("Google Home Pag