MicroFocus Testing Tools: LoadRunner and QTP

In QTP/UFT, Shift+F2 opens the Rename Action dialog allowing you to change the name of the current action. This is distinct from F2 (edit cell in data table) and other F2 variants. The rename functionality is important for organizing test actions with meaningful names.

In QTP/UFT, Ctrl+F7 checks the syntax of the current script or test without executing it, highlighting any compilation or syntax errors. This is faster than running the test to catch errors. F7 alone may have different functionality depending on context.

In QTP/UFT, Ctrl+M toggles comments on the selected line(s) of VBScript code. This is a common debugging technique to temporarily disable code without deleting it. Ctrl+C is copy, not comment, reinforcing that Ctrl+M is the correct mnemonic for coMment.

F9 is the standard keyboard shortcut in QTP/UFT to toggle breakpoints at the current line in your code. F3 is typically used for step into debugging, F5 for continue/run, and F10 for step over in most debugging environments.

F12 is the QTP/UFT shortcut key to insert a standard checkpoint at the current cursor position. Shift+F12 is used for output values, while F11 is typically for step-into debugging operations.

Ctrl+R opens the Object Repository in QTP/UFT where you can view and manage test objects. Ctrl+O is commonly used for opening files in most applications, and Ctrl+B typically relates to bookmarks or breakpoints.

Ctrl+Shift+M is the keyboard shortcut to uncomment selected lines in QTP/UFT editor. Ctrl+M is typically used to comment lines, so uncommenting uses the same keys with the Shift modifier to reverse the operation.

Ctrl+Shift+F9 removes all breakpoints from the current action in QTP/UFT. F9 alone toggles individual breakpoints, and Ctrl+A selects all text rather than affecting breakpoints.

Shift+Alt+N is the QTP/UFT shortcut to create a new function library file. Ctrl+N is commonly used for new files in text editors, but function libraries require the modified key combination.

The General: Log category in LoadRunner's run-time settings allows developers to configure logging behavior, including the option to send messages only when an error occurs. Meanwhile, Run Logic defines the execution flow, and Miscellaneous governs error handling and threads.

In performance testing and measurement, a 'Transaction' represents the complete end-to-end time measurement of one or more steps that together accomplish a business task. Actions are individual steps within a transaction, a Business Process is a broader workflow, and Business Verification is a validation phase - none measure complete time duration.

In LoadRunner, a Scenario file defines the overall execution details of a load test, including the specific Vusers, load generators, and test goals. In contrast, Scripts contain the actions recorded for Vusers, and the Analysis tool is used to analyze results post-run.

The Time to First Buffer (TTFB) Breakdown graph specifically analyzes how much time each web page component spends on server processing versus network transfer before the first buffer is received. Throughput shows data transfer rates, Windows Resources monitors client machine performance, and Transaction Performance Summary aggregates overall transaction times.

In LoadRunner's Runtime Settings, the 'General' node contains settings that apply universally across all protocols - think, pacing, logging, and other fundamental settings. Protocol-specific nodes like Browser (for Web), Network (for network-level protocols), and Internet Protocol (for specific IP settings) are only available when those particular protocols are selected in the script.

Automated load tests can be executed repeatedly with identical conditions, ensuring consistent results. Scaling is easier because you can programmatically increase load without manual intervention. Data collection is simplified as automated tools capture metrics automatically, eliminating manual recording errors.

LoadRunner uses .usr files to define virtual user scripts that can be organized into groups. These files contain the recorded or scripted user actions that will be replayed during load testing scenarios. Other file extensions serve different purposes - .lrr is for results, .lra for analysis files, and .lrs for scenario files.

LoadRunner supports two primary SLA types: Per Time Interval SLAs monitor performance metrics within specified time windows, while Over the Whole Run SLAs evaluate performance across the entire test duration. Options B, D, E, and F are metrics that might be measured within SLAs, not SLA types themselves.

The load generator (also called the host) is the machine that actually executes Vuser scripts and collects performance metrics during the test run. It monitors system resources, response times, and other performance data locally, then sends this data to the Controller. Analysis tool processes data after the run, and Controller orchestrates but doesn't store raw monitoring data.

Goal-oriented scenarios allow LoadRunner to automatically adjust the number of Vusers based on predefined performance goals like hits per second or response time. The system increases or decreases Vuser count dynamically to achieve the target. Manual scenarios require fixed Vuser numbers, Real-Life uses predefined patterns, and User-Defined uses custom Vuser scheduling scripts.

The Ir_start transaction should be placed immediately after the rendezvous point to measure the performance of the synchronized action. Rendezvous points cause Vusers to wait until all arrive, then proceed simultaneously. Starting the transaction after this point captures the combined load impact of all concurrent users. Placing it before would measure waiting time, and end/beginning of action would miss the synchronization effect.