Multiple choice technology testing

While analyzing the Vuser log files from a scenario run, you see the following log file from one of the Vusers. Start auto log message stack - Iteration 1. Starting action BookFlight. BookFlight-c(5): Notify: Transaction WT_00_Home_Page started. BookFlight.c(7): Error -27796: Failed to connect to server 27.0.0.1:1080 [10061] End auto log message stack. What was the Log Settings.

  1. Standard Logging

  2. Extended Logging

  3. Always send a message

  4. Send message only when an error occurs
Reveal answer Fill a bubble to check yourself
D Correct answer
Explanation

The log shows a connection error message (-27796) but doesn't display routine log entries that would appear with Standard or Extended logging. 'Send message only when an error occurs' setting suppresses normal output and only captures errors or warnings. Standard logging shows basic script flow, Extended shows detailed parameter data, and 'Always send' generates verbose output for all actions.

AI explanation

The log setting was "Send message only when an error occurs." In HP/Micro Focus LoadRunner, when this setting is active, the Vuser buffers step-by-step messages internally ("Start auto log message stack") without displaying them, and only flushes/prints the accumulated message stack to the log if an error is subsequently encountered during that transaction/iteration — which is exactly the pattern shown: messages are batched under "auto log message stack," then an error ("Failed to connect to server... [10061]") triggers the stack to be output. "Standard" and "Extended" logging would print messages continuously regardless of errors, and "Always send a message" would not buffer/withhold anything.

Keep practicing — related questions