As a part of performance testing activity, it is a tester’s role to debug all the scripts before it reaches the execution phase. In LoadRunner we can make use of the logging options provided in the runtime settings for the same. It allows us to select the level of details about script playback that are to be displayed at the replay log.
- There two types of logs available in load runner to specify the level of information to be logged during the replay,
1. Standard Log
2. Extended Log
- A standard log displays the details about the set of functions executed and the messages displayed
- This can be used to validate whether the functions are executed as expected
- This is used for logging not only the function calls but also additional details such as parameter substitution, request headers, request body, response headers and the response body. The extended log has three log levels;
1. Parameter Substitution
It adds the details about the parameters substituted and the dynamic values that were captured.
2. Data returned by server
The response header and the response body details for each request is contained in the replay log if this option is selected, i.e. it captures the data that is returned from the server.
3. Advanced trace
With this option enabled, the replay log almost looks like a generation log as it contains details about every request and response that has been sent to and received from the server.
Manual Correlation with extended log
- Extended logging feature is preferred for debugging a script as we can inspect the values to be correlated
To conclude the above, logging the function calls, requests, and responses will be helpful for debugging the script but they utilize the system resources heavily. So the logging is to be disabled for long scenarios. Besides, when going for an execution with very large number of vusers, it is recommended that we disable the logging feature altogether by unchecking the enable logging option.