Performance Testing and LoadRunner Quiz

To solve this question, the user needs to have knowledge of LoadRunner and its terminology.

The term for varying values defined in a placeholder that replaces hard-coded values is called a parameter.

Option A, variable, is incorrect because although variables can hold changing values, they are not specifically used to replace hard-coded values.

Option B, constant, is incorrect because constants, by definition, are values that do not change. They are not used to replace varying values.

Option D, correlation, is incorrect because correlation is a technique used to handle dynamic values in web applications, but it does not replace hard-coded values like a parameter does.

Therefore, the answer is:

The Answer is: C. Parameter

In LoadRunner's runtime settings, the Log option (under General) allows you to configure logging levels including logging only when errors occur. This is a performance testing best practice to reduce log volume while capturing critical failure information. The other options (Run Logic, Miscellaneous, Additional Attributes) control different aspects of test execution but not error-specific logging behavior.

VuGen (Virtual User Generator) is the LoadRunner component used to record user steps and generate scripts that emulate real user behavior. It captures network traffic and creates Vuser scripts that replay the recorded actions. The Controller manages the test, Analyzer analyzes results, and Load Generator executes the Vusers but does not record them.

In LoadRunner architecture, the Controller (which orchestrates load tests) can be installed on UNIX systems. This is because UNIX provides stable, high-performance environments suitable for managing complex test scenarios. While LoadRunner has cross-platform components, the Controller's UNIX support is a key architectural feature for enterprise deployments.

Explanation:
To answer this question, you need to understand the different file types and their extensions used in data analysis or software testing.

Option A) Script - The file type for scripts is often .sh, .py, .js, or .pl depending on the programming language. .lrr is not a common file extension for scripts.

Option B) Analysis - The file type for analysis is often .csv, .xlsx, .json, or .txt depending on the type of data and analysis. .lrr is not a common file extension for analysis files.

Option C) Scenario - The file type for scenarios is often .xml, .json, or .txt depending on the tool or framework used. .lrr is not a common file extension for scenario files.

Option D) Results - The file type for results is often .html, .pdf, .docx, or .csv depending on the type of output. .lrr is a file extension for results generated by LoadRunner, a performance testing tool by Micro Focus.

The correct answer is D. This option is correct because .lrr is a file extension commonly used for results generated by LoadRunner.

In LoadRunner scenarios, a 'group' is a collection of Vusers that share the same script and run with identical load parameters. Groups allow organized management of different user types (e.g., 50 Vusers running login script, 100 running browse script). Sets, profiles, and scenarios refer to different LoadRunner concepts.

Correlation is the technique used to capture dynamically generated server values (like session IDs, timestamps, or transaction IDs) and reuse them later in the script. Without correlation, scripts would fail because the recorded values become invalid. Parameters store static or user-defined data, variables hold temporary values, and constants are unchangeable - none of these capture dynamic server responses.

The question asks which command CANNOT check for response presence. lr_eval_string evaluates a parameter's value but does not search or validate response content - it's a string substitution function. The other three (lr_xml_find, web_image_check, web_reg_find) are content verification functions that actively check for text, images, or XML elements in server responses.

A Rendezvous Point causes multiple Vusers to wait at a specified point in the script until all arrive, then continue simultaneously. This creates realistic load conditions by synchronizing transactions that would normally occur together (like 100 users clicking 'Submit' simultaneously). Think time adds user-like delays, pacing controls iteration timing, and Run Logic manages script flow.

web_reg_save_param extracts dynamic data from HTML pages to save in a parameter. In the XML-based Web Services protocol, lr_xml_get_values queries and extracts values from XML responses into parameters, making it the equivalent function. lr_save_string assigns a string directly, and lr_xml_find searches for a query match rather than saving values.

Performance testing evaluates system characteristics like speed, scalability, and stability, which are non-functional aspects of software. Unit, regression, and black box testing are functional testing types because they verify if the software functions correctly according to its business logic and specification requirements.

Non-functional testing evaluates software quality attributes rather than specific behaviors. Performance testing checks how well the system performs under various conditions, which is a non-functional requirement. Unit testing, black box testing, and regression testing can test functional or non-functional aspects.

Performance testing types include endurance testing (long-term stability), stress testing (breaking point), and baseline testing (performance benchmark). Component testing tests individual units/modules, making it a functional testing type, not a performance testing type.

Performance testing should focus on critical, high-risk, and highly frequented business scenarios rather than all functional flows. Testing every single functional flow is impractical, time-consuming, and cost-prohibitive, as many low-use features do not present a significant performance risk to the overall application infrastructure.