LoadRunner Foundations

• Covers the minimum hardware requirements
• Looks at where each part of LoadRunner does and where they should be installed in relation to its other parts.

• Looks at various installation designs which are dependent on test application environments and locations.

• Discover the capabilities of LoadRunner while learning LoadRunner specific terminology.

• Follow a game based set of examples that promotes discussion around the entire load testing process, from looking at which scripts to record, to how many days spent testing.

Day 2 - Running Load Tests

• Determining which test cases to perform
• Gathering information on number ofusers completing each business process
• Determine rates of business process usage

• Create a new Manual Scenario
• Adding Scripts to the Scenario
• Adding Load Generators
• Setting number of Vusers per Script

• Run-Logic settings – when do the number of iterations count
• Logging settings
• Think Times
• Pacing – how to use when given testing rates
• Other run-time settings

• Per Script vs. Per Group Scheduling
• Initializing a test run
• Setting Ramp-ups
• Setting Run-lengths
• Setting Ramp-downs

• Adding a monitor
• Configuring the monitor

• Start the run manually (via Vusers window, or by group)
• Start the run to follow the schedule
• Viewing the logs during the test run
• Examining Pass vs. Failed transactions
• Viewing Error

Day 3 - LoadRunner Scripting - Web

• Determining what steps to perform
• Consider data and data usage Recording a Script
• Recording Options – HTML vs. URL recording
• Recording the test case

• Add Transactions during recording
• Add Transactions after recording using the transaction workflow tool, and manually via the keyword view.

• Why is a verification point necessary
• Add a verification during recording
• Add a verification after recording using the keyword view screenshots
• Global Verification Points

• Setting appropriate logging option
• Controlling the number of iterations to playback
• Think times and Pacing settings
• Other settings

• Adding Parameters in the keyword view, and in the script view
• Create a file type parameter
• Examine other parameter types, e.g. Random type, date time type
• File parameter access methods
• Update Parameter value settings
• Simulate Parameter Usage

• Required Settings
• Run the test, examine errors
• Use the Scan for Correlations tool
• Determine which values to correlate
• Correlate
• Review the correlation functions added to the script

• Required settings
• Run the test and examine the errors to determine which commands to focus on
• Determine which of the values is the dynamic one
• Determine where the server sent the dynamic value
• Determine appropriate left and right boundaries and ordinal values
• Add the web_reg_save_param function
• Replace hard-coded dynamic values with the new parameter
• Run the test to validate Correlation during Recording
• Add a rule to the recording options
• Test the rule
• Record the script
• Use of the regenerate script option

Day 4 - Advanced LoadRunner Analysis

• Condition statements and loops
• Variable declarations
• Common string manipulation functions
• Data conversion functions
• LoadRunner specific functions (lr_eval_string, output messages, lr_save_string) Custom Checkpoints
• Examining the web_reg_find savecount option
• Capturing data using the web_reg_save_param function

Day 5 - Advanced LoadRunner Solutions

• Using the sprintf function
• strstr
• strcpy
• strcat

• Capturing multiple related items
• Randomly selecting one of the items (the old way – pre version 9)
• Randomly selecting one of the items (the new way – post version 9)

• lr_save_string and lr_save_int
• lr_save_datetime function
• lr_advance_param vs. lr_next_row

• Define a Global Verification using code
• Temporarily Pause Verification and resume it. Additional Attributes
• Using additional attributes