Deep Description on Runlogic

Types of Action files
  • Vuser_init
  • Action
  • Vuser_end
Vuser_init
  • This is the first action that is executed by the vuser and it comes under the init section of the script.
  • It is executed only once in the life cycle of a vuser. By life cycle we mean the time between the start and the stop of a vuser.
  • Even if the vuser has multiple iterations to execute, the set of steps incorporated within this action file is executed only once.
  • We cannot disable/delete vuser_init. Even if it does not contain any steps to execute, it has to be present.
  • We can put those steps in vuser_init that need to be executed only once. E.g. a script that logs in the same user to an application and performs certain tasks, since the same user is logging in every time, login steps can be put in vuser_init. But it also depends on the business requirement whether we should include launch and login in vuser_init. If launch and login is to be observed for its performance then including them in vuser_init is not recommended.
Action
  • By default vuser creates an action file named as Action when we create/record a script. It comes under the run section of the script.
  • Every time that a vuser iterates, the steps that are embedded within this file are executed.
  • We can have multiple action files of this type in a script.
  • We can disable/delete this action. The script can execute without it.
Vuser_end
  • This is the last action file that is executed and it comes under the end section of the script. Like the vuser_init, the step within this actiona re alos executed once in the entire life cycle of a vuser.
  • We cannot disable/delete vuser_end. Even if it does not contain any steps to execute, it has to be present.
  • Like vuser_init, we can put steps that need to be executed once for the entire execution of a vuser.
Blocks
  • A script can be divided in to three sections
  • Init
  • Run
  • End
  • Each of the above sections can be further divided in to one of more sub sections called blocks.
  • Each block can contain one or more action blocks or simply actions.
  • The blocks are particularly useful if we need to repeat a set of actions.
  • Action blocks can be created in the run time settings of the LR script. To create a block, just select the section that and then click insert block or right click on the section and then select Insert Actions Block.
Insert Block Img1
  • The number of iterations for a block can be set in the properties of it.
  • One thing to note is that only the block in the run section can have multiple iterations set. The ones in init and end section can set for single iteration only.
  • Each block in the run section can be set to execute for different number of iterations.
  
  • One thing to note is that only the block in the run section can have multiple iterations set. The ones in init and end section can set for single iteration only.
  • Each block in the run section can be set to execute for different number of iterations.
  • In the scenario shown above, we observe
  • Run section has two blocks viz. Block0 and Block2.
  • Each block has one action each.
  • Run section will iterate 2 times.
  • Each time in the run section, block0 will be executed 2 times and block1 will be executed 3 times.
  • In total, block0 will be executed 2 X 2 times and block1 2 X 3 times.

Comments

Post a Comment

Popular posts from this blog

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_u
Read more

web_set_max_html_param_len

The  web_set_max_html_param_len  function sets the maximum length of any HTML string which VuGen can retrieve and save in a parameter. The default value for the maximum length of a parameter that can be captured during correlation is 256 characters. To retrieve a string longer than 256 characters, use  web_set_max_html_param_len  to increase the maximum valid length. An attempt to save a string whose length exceeds the maximum length will fail
Read more

Error -27492: "HttpSendRequest" failed, Windows error code=12057 (certificate revoked) and retry limit (0) exceeded for URL="

This error occurs when using WinInet replay instead of sockets with Integrated Authentication enabled in run-time settings. The purpose of this was to allow vusers to use SSO with SPNEGO authentication in an IBM WebSEAL environment. After spending some time with the mystical HP level 3 support, they identified an undocumented flag which helps out significantly in this. So, instead of using the WinInet replay engine (which is not encouraged by HP) you should do something similar to the following. vuser_init() {             // Preferred run-time settings             // Browser -> Browser Emulation        // [ ] Simulate a new user on each iteration        // Preferences -> Options        // Enable Integration Authentication [Yes]             web_set_sockets_option("INITIAL_BASIC_AUTH","1");             web_set_user("DOMAIN.LOCAL\\username",                         "password",                         "s
Read more