Software Testing and LoadRunner Fundamentals

When you have exactly 5 Vusers and 5 parameterized values that must each be used only once, you need unique selection to assign distinct values to each Vuser. The 'update value on: once' setting ensures each Vuser keeps their assigned value throughout the entire test execution, preventing any value from being reused. This guarantees a one-to-one mapping between Vusers and parameter values.

WinDiff is a file comparison utility that helps identify differences between two files by displaying them side-by-side with changes highlighted. During performance testing, correlation involves capturing dynamic server values like session IDs that change with each request. WinDiff helps testers identify which values change between different response recordings, indicating what needs to be correlated in the test script.

In LoadRunner's distributed architecture, a machine acts as a load injector only when the Load Generator agent process is installed and active. This agent receives instructions from the Controller and executes the Vuser scripts to generate load. VuGen is for script creation, Controller orchestrates the test, and Analyzer is for post-test analysis.

LoadRunner's core components are VuGen (for script recording), Controller (for scenario management), Load Generator (agents that inject load), and Analyzer (for results analysis). ScriptDebugger is not a standard LoadRunner component - it appears to be an invented or misnamed option in this question.

LoadRunner's goal-oriented scenarios define target metrics like number of Virtual Users, Hits per Second, and Transactions per Second (Response Time is also a common goal). HTTP responses per second is not a standard goal type - this metric is typically analyzed under Hits per Second or Transaction throughput categories.

URL-based recording mode captures each HTTP request as a separate statement, including all resources (images, CSS, JS, etc.), resulting in much larger scripts. HTML mode groups requests and uses context-sensitive functions, creating more compact scripts that mirror user actions at the browser level.

Overlay merge in LoadRunner graphs shares the same X-axis (typically time) and plots multiple data series on top of each other. This allows comparing different metrics or the same metric from different runs on a single timeline. The other options describe different merge types or are incorrect.

LoadRunner supports both Text and Image checks (also called Verification). Text checks verify specific text appears on a page, while Image checks verify that a specified image is present or that an image matches an expected baseline. Both are supported, making 'All of the Above' correct.

To answer this question, the user needs to have knowledge of the functions in LoadRunner that can send messages to the output window.

Option A: lr_output_message - This function sends a message to the LoadRunner output window during script execution. This option is correct.

Option B: lr_debug_message - This function sends a debug message to the LoadRunner output window during script execution. This option is incorrect as it sends a debug message and not a regular message to the output window.

Option C: lrd_stmt - This function is used to execute SQL statements for ODBC and Oracle databases. It does not send a message to the output window. This option is incorrect.

Option D: lrd_fetch - This function retrieves data that matches the criteria specified in the SQL statement. It does not send a message to the output window. This option is incorrect.

Therefore, the answer is:

The Answer is: A

Arc testing is another name for branch testing in software testing. It involves testing all branches in the code by ensuring that every decision point (branch) takes both true and false paths. This is distinct from agile testing, beta testing, or ad-hoc testing.

Exit criteria serve multiple purposes in testing: they define when to stop testing (A), mark the end of a test level (B), and confirm when tests have achieved specific preconditions (C). Since all three statements are valid purposes of exit criteria, 'All of the above' is the correct answer.

Equivalence partitioning is a test design technique that divides input data into groups (equivalence classes) that are expected to be processed similarly. By testing one value from each equivalence class, you achieve coverage of both valid and invalid inputs and outputs. Boundary value analysis focuses on edge cases, decision tables on complex logic combinations, and state transition on system states.

Alpha testing is conducted at the developer's site by potential users or independent test team before releasing to external users. While unit and integration testing also happen at the developer's organization, alpha testing specifically involves user acceptance testing in a controlled environment at the development site.

Software engineers typically identify, evaluate, and rank tools but recommend them to management rather than making the final selection decision themselves, as tool acquisition usually requires management approval and budget authorization. Option B oversimplifies the process, and option D incorrectly suggests engineers have final selection authority.

HP Quality Center (now known as ALM) is a comprehensive test management tool that includes both test case management and defect tracking capabilities. Caliber is primarily for requirements management, Integrator for integration testing, and TOAD is a database tool - none of these provide the combined test case and defect management functionality.

Caliber (now part of Micro Focus) is a requirements management tool that allows customers to update and track requirement details. TOAD is for database development, TIBCO is integration middleware, and QTP (QuickTest Professional) is automated testing software - none of these focus on requirements management.

When a test case is deemed invalid after review (e.g., due to requirements change, duplicate, or not applicable), it is marked as 'NA' (Not Applicable) to indicate it should not be executed. 'No Run' means it hasn't been executed yet, 'Blocked by defect' indicates it cannot be run due to a known issue, and 'Failed' means it was executed but didn't pass.

Standard defect lifecycle statuses include New, Open, Fixed, Reopen, Closed, Deferred, and others depending on the tracking system. 'Passed' is a test execution status, not a defect status - tests pass or fail, defects get fixed or deferred. The presence of 'passed' in the defect status list makes it the invalid option.

Batch testing refers to validating background, non-interactive processes. Since there is no user interface, testers must run the jobs and directly verify output files, system logs, execution resources, and database updates to ensure correct processing, rather than testing interactive web pages or using a GUI.