Performance Testing with LoadRunner and Unix Monitoring

WinRunner is a functional testing tool for GUI automation, while LoadRunner, Silk Performer, and JMeter are dedicated performance/load testing tools that simulate multiple users to measure system performance under load.

Default logging in performance testing tools like LoadRunner is minimal - only errors are logged. This reduces I/O overhead during load tests, which is critical for accurate performance measurements.

Top-time transaction refers to identifying peak-performance individual transactions. Running at 20% load isolates individual transaction performance without system-wide congestion, allowing clear identification of the fastest transactions.

Performance testing tools like LoadRunner support unattended execution through scheduled scenarios. Once configured, the scenario runs automatically without human intervention, logging results for later analysis.

A scenario in performance testing defines the test configuration including number of virtual users, test duration, and ramp-up/ramp-down patterns. It orchestrates how load is applied over time.

In performance testing, the Load Generator is the component responsible for simulating multiple virtual users to generate the actual traffic and load on the target system. The Controller manages and coordinates the test execution, while VuGen is used for scripting the user behaviors.

A load generator is the machine/component that injects load into the system by simulating virtual users. It is synonymously called a load injector because it injects the load into the application under test.

The 'top' command is the standard Unix/Linux utility for monitoring processes in real-time, showing CPU usage, memory consumption, and other resource metrics for running processes. It displays processes sorted by resource usage, making it easy to identify which processes are consuming high memory and CPU. Topas (AIX-specific), nmon (another AIX tool), and 'monitor' (not a standard command) are either platform-specific or incorrect.

The netstat (network statistics) command is a standard command-line utility used to monitor network status, active connections, routing tables, and interface statistics. Distractors like nmon, netmon, and nstat are either different system monitoring utilities or not standard commands for basic network status display.

vmstat (virtual memory statistics) is the standard Unix/Linux command that reports memory statistics including user and system memory usage, along with process, swap, and CPU activity. It provides snapshots of system performance. The other options (memstat, mstat, memorystat) are not standard Unix commands - they may exist as third-party tools or are completely fictional.

iostat (Input/Output statistics) is the standard Unix/Linux command for monitoring disk I/O and system input/output statistics. It reports device utilization, throughput, and service times. The name combines 'io' (input/output) with 'stat' (statistics). The other options are either incorrect command names or too generic - 'statistics' is not a specific Unix command.

machinfo is the command that displays detailed server information in Cognos, including hardware and software configuration details.

Vugen supports HTML Mode (records at browser level showing user actions) and URL Mode (records at protocol level showing individual requests). These are the two primary recording modes available in LoadRunner. Binary Mode is not a standard recording mode.

In Vugen, F5 is the standard shortcut key for running the current script, while Shift+F5 compiles and runs the script. These are common IDE shortcuts that Vugen follows for script execution.

The scenario states that 30 users are logged into the application. Before any user can book seats, cancel tickets, or check itinerary status, they must first log in. Therefore, all 30 users (100%) must perform the login transaction.

In LoadRunner scripts, global variables that need to be accessible across all actions are declared in the globals.h file. Vuser_init and Vuser_end are for initialization and cleanup, while Action contains the main script logic.

The number of iterations is configured under the General: Run Logic tab in Runtime Settings. This tab controls how many times each action will repeat during test execution. The other tabs handle different settings like logging and attributes.

web_reg_save_param() is the function used to correlate dynamic values in HTTP/HTML scripts. It registers a request to save dynamic data from server responses to a parameter. web_reg_find() is for content verification, not parameter saving.

Vuser ID, Table file, and File are all valid parameter types in LoadRunner. Static Number is not a standard parameter type - parameters are typically dynamic or sourced from files, not static values. This makes it the odd one out.

When a block contains multiple actions, they can be executed either sequentially (in order) or randomly. Both Sequential and Random are valid execution properties. Unique applies to parameter selection, not action execution order.