LoadRunner Interview Questions
Q:What is the function to upload a file to the ftp server using Vugen/LoadRunner?
A: ftp_put is the function to upload a file to the ftp server.
Q: What is the use of web_file function in LoadRunner? How to set path for file input elements in LoadRunner?
A: web_file function is used to set the path for ‘FILE’ elements.
Q: What is IP Spoofing or IP Address Spoofing?
A: IP Spoofing is the method of concealing identity about the origin of information sent. It is done by creating IP Packets with bogus IP addresses.
Q: How to connect to database using Vugen/LoadRunner?
A: lr_db_connect function can be used to connect to database via Vugen.
Q: What is the use of web_custom_request?
A: web_custom_request is a function that allows to create a custom HTTP request using any method (POST or GET) or body. By default, VuGen generates this function only for requests that could not be interpreted with other web functions.
Q: What is network latency?
A: Network Latency is the delay in response from server because of the network connection. Network Latency is of two types:
1) One Way – The time taken for a packet to reach destination
2) Round Trip – The time taken for a packet to reach destination plus the time taken for a packet to reach source from destination.
Q: What counters do you monitor for database?
A: We can monitor below counters for database:
1) Active Transactions
2) Transactions/sec
3) Log Cache Hit Ratio
4) Percent Log Used
5) Time Taken By query to execute
Q: What is hard parsing?
A: If a session executes an SQL statement that does not exist in the shared pool, then database has to do a hard parse.
Q: What is soft parse?
A: If a session executes a SQL statement that exists in the shared pool and there is a version of the statement that can be used, then this is referred to as a soft parse.
Q: How do you count how many matches are returned by ORD=ALL in web_reg_save_param?
A: To retrieve the total number of matches you can use the following term: ParamName_count. For example, to retrieve the total number of matches saved to the parameter array, use:
TotalNumberOfMatches=atoi(lr_eval_string(“{ParamName_count}”));
Q: What are the checkpoints in Vugen or LoadRunner?
A: There are two checkpoints in Vugen:
1) Text Checkpoints
2) Image Checkpoints
Q: What is Image Check or Image Checkpoint in Vugen or LoadRunner?
A: Vugen allows to add a user-defined check that searches for an image on a web page during the run. This can be done by using function web_image_check. The web_image_check function verifies the presence of a specified image inside an HTML page.
Q: What is Text Check or Text Checkpoint in Vugen or LoadRunner?
A: Vugen allows to add a user-defined check that searches for a text on a web page during the run. This can be done by using functions web_reg_find, web_global_verification and web_find.
Q: What is web_reg_find?
A: web_reg_find is used to register a request to search for a text string on a web page.
Q: What is web_find?
A: web_find function searches a HTML page for a specified text. web_find is deprecated, web_reg_find is used instead. But still questions are asked about it in LoadRunner interviews.
Q: What is the difference between web_reg_find and web_find?
A: Below table illustrates the differences between web_reg_find and web_find:
| web_reg_find | web_find |
|---|---|
| web_reg_find is created to replace web_find | web_find is depreceated |
| web_reg_find registers the search request before the buffer arrives, as soon as the buffer arrives the searching starts, hence web_reg_find is faster | web_find searches context only after request is complete and hence slower |
| web_reg_find can be used for both HTML-based and URL-based scripting | web_find is limited to HTML-based recorded scripts |
| In scripting web_reg_find is placed before the request function | In scripting web_find is placed after the request function |
Q: What is web_global_verification?
A: web_global_verification registers a request to search for a string in page returns from all the subsequent requests. web_global_verification is similar to web_reg_find in terms of attributes and functioning, the only difference being web_reg_find searches only one request whereas web_global_verification searches all subsequent requests.
Q: What is the difference between lr_exit and lr_abort?
A: The lr_exit function allows you to exit from the script run during execution, it gives you various continuation option which include to exit vuser or just exit the iteration and continue next iteration.
A transaction in which lr_exit is called does not appear in the LoadRunner controller in the Transaction Status box. It is ignored in the count of passed and failed transactions.
If lr_exit is called several times in the same script, whether in different actions or different iterations, it is the exit status of the last call that determines the status of the Vuser group running the script.
The lr_abort function aborts the execution of a script. It stops the execution of the Actions section, executes the vuser_end section, and ends the execution. When you end a run using this function, the status is “Stopped.” lr_abort does not give any continuation option, the vuser is exited.
Q: What is rendezvous point?
A: Rendezvous point is the statement where all vusers belonging to the same Rendezvous point name would arrive and execute the subsequent transaction simultaneously. Rendezvous point is used for concurrent execution of transactions. Rendezvous point can only be used in action section of vugen.
Q: What are popular web servers?
A: 1) IIS (Internet Informatioin Services) by Microsoft
2) Apache by Apache Software
Q: What are popular app servers?
A: 1) IBM WebSphere
2) Oracle Weblogic
3) Red Hat JBoss
Q: Does LoadRunner allows to add vusers manually while running a scenario?
A: Yes, execution team can add vusers manually in manual scenario without percentage mode.
Q: What are the two common parameters to be co related for .Net apps?
A: 1) Event Validation
2) ViewState
Q: What are the components of loadrunner?
A: Loadrunner has five components:
1) Vugen
2) Controller
3) Analysis
4) Agent process
5) Agent process dispatcher (This component is on controller side, it interacts with load generators)
Q: What is the difference between web server and application server?
A: Web server serves only http requests, application server can serve non http requests as well. Web server serves pages for viewing in web browser, an application server provides method that can be called by client applications e.g. API calls.
Q: What is the relation between response time and throughput?
A: Throughput is the amount of data in bytes that the Vusers receive from the server in a second. Response time is the transaction response time. Response time is directly proportional to throughput, if throughput increases the response time would increase.
Q: What are the types of goals in goal oriented scenario?
A: LoadRunner Controller provides with five different types of goals in a goal oriented scenario:
1) The number of concurrent Vusers
2) The number of hits per second
3) The number of transactions per second
4) The number of pages per minute
5) The transaction response time that you want in your scenario
Q: What is the difference between html and url based recording?
A: Below table describes the difference between html and url based recording:
| HTML Based | URL Based |
|---|---|
| This is high level recording | This is low level recording |
| One request is generated per html page | Multiple requests can generate per page. Separate requests are generated for images, css, etc. |
| Script generated is short | Script generated is comparatively long |
| Script is easy to maintain | Script is comparatively difficult to maintain |
| You can not define timers for each component of the page | You can define timers for each component of the page |
Q: What are the scenario types in loadrunner?
A: Loadrunner has 3 scenario types:
1) Manual Scenario
2) Manual Scenario with percentage mode to distribute the vusers (In this mode vusers cannot be added when the scenario is running)
3) Goal Oriented Scenario
Q: What are different Run Modes in Manual Scenario of loadrunner?
A: Run Modes available for Schedule by Scenario:
a) Real life schedule
b) Classic schedule
Run Modes available for Schedule by Group:
a) Real life schedule
b) Run Until complete
Q: What are the different schedule types available in Manual Scenario of loadrunner?
A: There are two schedule types available:
1) Schedule by Scenario
2) Schedule by Group
Q: What is the difference between Real Life and Classic Schedule in loadrunner?
A: In Classic schedule, LoadRunner always runs all the Vusers, whether simultaneously or gradually. In a Real-life schedule, user can select how many Vusers to run. In classic schedule there is no option to control stopping of users.
Q: What are the views in controller of loadrunner?
A: There are two views in controller:
1) Design View
2) Run View
Q: What is the extension of vugen file?
A: Extension of vugen script file is .usr
Q: What is the extension of loadrunner scenario file?
A: Extension of loadrunner scenario file is .lrs
Q: What is the extension of loadrunner results file?
A: Extension of loadrunner results file is .lrr
Leave a Reply