Software Testing and LoadRunner Fundamentals

Functional testing can be performed at any test level - unit, integration, system, or acceptance testing. Each level tests functional requirements at its scope. Option A is incorrect because functional testing isn't limited to just system and acceptance levels. Option C is incorrect because functional testing also happens at unit and integration levels.

Debugging, which involves finding and fixing the root cause of defects or unexpected code behavior, is primarily performed by developers during the coding and unit testing phases.

Coverage measurement tools and dynamic analysis tools are typically used directly by developers during coding and unit testing to analyze code structure and execution. Distractors include tools like test comparators or performance tools, which are primarily geared toward dedicated testers.

In risk-based testing, identified risks directly inform: (i) the selection of appropriate test techniques based on risk type, (ii) the depth and extent of testing allocated to high-risk areas, and (iii) prioritization to uncover critical defects early. However, (iv) project cost determination is a project management function outside the testing scope, making it the only false statement.

System Testing uses its own test data specifically created for testing purposes, while End-to-End (E2E) Testing uses production-like data to simulate real-world scenarios. E2E testing validates the entire system flow with realistic data volumes and patterns, whereas System testing focuses on individual components with controlled test data.

The default sections in a VuGen (Virtual User Generator) script are vuser_init (initialization code that runs once per user before iterations), Action (the main business logic that repeats during iterations), and vuser_end (cleanup code that runs once after all iterations complete). Options like V_init or Vuser_Start are not standard VuGen section names.

web_reg_save_param is the LoadRunner function used for correlation - it captures dynamic values from server responses (like session IDs, CSRF tokens) and stores them in parameters for reuse in subsequent requests. web_report_data_point is for reporting, web_save_param_length gets parameter length, and web_set_max_html_param_len sets size limits - none handle correlation.

Pacing in LoadRunner refers to the time delay added between consecutive iterations of a VuGen script. It controls the rate at which each virtual user repeats its actions, independent of other users. It's not about delays between transactions (that's think time), between users (that's ramp-up), or between load tests (that's scheduling).

Throughput and response time are key performance metrics measuring system capacity and speed. While throughput determines the volume of transactions processed per unit of time, response time measures individual transaction latency. User injection limits represent load capacity rather than system performance metrics.