Explore topic-wise InterviewSolutions in .

Corelation is used to OBTAIN the DATA which are unique in every time of script run and which are generated by NESTED QUERIES.

Corelation is used to obtain the data which are unique in every time of script run and which are generated by nested queries.

LOG is level of information which we WANT to gather during run TIME.

Log is level of information which we want to gather during run time.

HOST is MACHINE which EXECUTES the VUSER SCRIPT.

Host is machine which executes the Vuser script.

LOADRUNNER PROVIDES TWO types of checkpoints:

• Text Checkpoints
• IMAGE Checkpoints

LoadRunner provides two types of checkpoints:

Web_Submit_Data();

Web_Submit_Data();

When TESTING using Web and WinSocket protocols, by default Vusers on each host machine use the host's (agent's) IP address. Since a particular server keeps serving a specific IP address, load tests would reflect network router caching and other optimizations RATHER than the real-life situation where different users ARRIVE to the server with different IP addresses. This is especially needed when the hardware configuration under test balances load across a "farm" of SEVERAL (web or database) servers. "IP spoofing" enables each host machine to "spoof" the server into thinking it is using many different IP addresses.

When testing using Web and WinSocket protocols, by default Vusers on each host machine use the host's (agent's) IP address. Since a particular server keeps serving a specific IP address, load tests would reflect network router caching and other optimizations rather than the real-life situation where different users arrive to the server with different IP addresses. This is especially needed when the hardware configuration under test balances load across a "farm" of several (web or database) servers. "IP spoofing" enables each host machine to "spoof" the server into thinking it is using many different IP addresses.

Will DEFINE the RENDEZVOUS POLICY in SCENARIO SETTINGS.

Will Define the Rendezvous Policy in Scenario settings.

lr_abort() ; lr_exit() ;

lr_abort() ; lr_exit() ;

ASYNCHRONOUS JAVASCRIPT and XML.

Asynchronous JavaScript and XML.

lr_set_debug_message(LR_MSG_CLASS_EXTENDED_LOG, LR_SWITCH_ON)
lr_set_debug_message(LR_MSG_CLASS_EXTENDED_LOG,LR_SWITCH_OFF)

lr_set_debug_message(LR_MSG_CLASS_EXTENDED_LOG, LR_SWITCH_ON)
lr_set_debug_message(LR_MSG_CLASS_EXTENDED_LOG,LR_SWITCH_OFF)

Recording Log: A Network ANALYZER would analyze the communication happing at network level and logs the events.

GENERATION Log: Logs the events happening while generating the Vuser SCRIPT after recording.

REPLAY Log: Records the events of happening when executed a function in the script. Will be LOGGED at each line level of the script.

Recording Log: A Network Analyzer would analyze the communication happing at network level and logs the events.

Generation Log: Logs the events happening while generating the Vuser script after recording.

Replay Log: Records the events of happening when executed a function in the script. Will be logged at each line level of the script.

WRITES FORMATTED OUTPUT to a STRING

Writes formatted output to a string

CORRELATION is a technique to handle the DYNAMIC values generated by the SERVER like session id's or serialization id's by REPLACING them with the CURRENT values generated during the run-time.

Correlation is a technique to handle the dynamic values generated by the server like session id's or serialization id's by replacing them with the current values generated during the run-time.

USUALLY by looking at the NUMBER of TRANSACTIONS & the no of CORRELATIONS.

Usually by looking at the number of transactions & the no of correlations.

YES we can RAMP up the VUSERS.

Yes we can ramp up the Vusers.

The HTML-based SCRIPT level GENERATES a separate STEP for each HTML user action. The steps are also INTUITIVE, but they do not reflect true emulation of the JavaScript code.

The URL-based script mode option instructs VuGen to record all browser requests and resources from the SERVER that were sent due to the user's actions. It automatically records every HTTP resource as URL steps (web_url statements). For normal browser recordings, it is not recommended to use the URL-based mode since is more prone to correlation related issues. If, however, you are recording pages such as applets and non-browser applications, this mode is ideal.

The HTML-based script level generates a separate step for each HTML user action. The steps are also intuitive, but they do not reflect true emulation of the JavaScript code.

The URL-based script mode option instructs VuGen to record all browser requests and resources from the server that were sent due to the user's actions. It automatically records every HTTP resource as URL steps (web_url statements). For normal browser recordings, it is not recommended to use the URL-based mode since is more prone to correlation related issues. If, however, you are recording pages such as applets and non-browser applications, this mode is ideal.

Protocol ADVISOR, Parameter Simulator, Business PROCESS REPORT, USER defined TEMPLATE.

Protocol Advisor, Parameter Simulator, Business process report, User defined template.

Will LOOK into the RESPONSE LOG of the FUNCTION while RECORDED.

Will look into the Response Log of the function while recorded.

CHANGE the Event configuration LEVEL, SELECT APPROPRIATE MODE(GUI/URL/HTML) etc..

Change the Event configuration Level, Select appropriate mode(GUI/URL/HTML) etc..

Offshore

Offshore

1 CONTROLLER and 4 LOAD GENERATORS.

1 controller and 4 load generators.

Load Testing – Test objective is to find the application behaviour is terms of RESPONSE TIME under anticipated load.

Endurance – Test Objective is to simulate load on an application UPTO a period of time to MONITOR the application performance for LONGER periods.

Load Testing – Test objective is to find the application behaviour is terms of response time under anticipated load.

Endurance – Test Objective is to simulate load on an application upto a period of time to monitor the application performance for longer periods.

To SIMULATE the load on EJB applications that USES RMI protocols over IIOP.

To simulate the load on EJB applications that uses RMI protocols over IIOP.

POOR GC, constant HIGH usage of VM, connection pools, poor INDEXING and complex SQL QUERIES etc.

Poor GC, constant high usage of VM, connection pools, poor indexing and complex sql queries etc.

It varies from BUSINESS SCENARIO to business scenario, the response TIME for CRITICAL business scenario is 3 sec's.

It varies from business scenario to business scenario, the response time for critical business scenario is 3 sec's.

POOR GC, constant high usage of VM, connection POOLS, poor indexing and complex sql queries ETC.

Poor GC, constant high usage of VM, connection pools, poor indexing and complex sql queries etc.

Documents RELATED to the HIGH level and LOW level architecture of the application. Design documents and documents that descibe the USAGE of thrid party components and external COMMUNICATION components and documents that describe the communication architecture of the application and use cases and test cases of the business critical scenarios and documents related to the system service levels and documents of h/w , s/w re's etc......

Documents related to the High level and low level architecture of the application. Design documents and documents that descibe the usage of thrid party components and external communication components and documents that describe the communication architecture of the application and use cases and test cases of the business critical scenarios and documents related to the system service levels and documents of h/w , s/w re's etc......

WORKED on App servers like WEBLOGIC, Jboss, MS-IIS 6.0 and db servers like DB2 and SQL SERVER.

Worked on App servers like Weblogic, Jboss, MS-IIS 6.0 and db servers like DB2 and sql server.

I worked with VARIOUS monitors at App server LEVEL and monitors of WINDOWS resouces of the servers and few monitors at db level.

App server monitors – JVM size, Connection ppol, GC, Heap size, free memory etc.;

Windows resources – CPU utilisation, processing time, Process, Virtual memory, page faults etc.:

Db monitors – Top time consuming sql's, poor INDEXES, dead locks, etc...

I worked with various monitors at App server level and monitors of windows resouces of the servers and few monitors at db level.

App server monitors – JVM size, Connection ppol, GC, Heap size, free memory etc.;

Windows resources – CPU utilisation, processing time, Process, Virtual memory, page faults etc.:

Db monitors – Top time consuming sql's, poor indexes, dead locks, etc...

CORRELATION is a technique to handle the dynamic values GENERATED by the SERVER like session id's or SERIALIZATION id's by replacing them with the current values generated during the run-time.

Correlation is a technique to handle the dynamic values generated by the server like session id's or serialization id's by replacing them with the current values generated during the run-time.

IDENTIFY the protocol (protocol ADVISOR) → create a new VUSER script by selecting the supporting protocol → Record the actions with appropriate recording options → Generate Script → Run the script → Identify the dynamic values and CORRELATE all the dynamic values and run the script

Identify the protocol (protocol Advisor) → create a new Vuser script by selecting the supporting protocol → Record the actions with appropriate recording options → Generate Script → Run the script → Identify the dynamic values and correlate all the dynamic values and run the script

I will look into the Log message WINDOW in controller and identify why the error is thrown & if needed I will make ENHANCEMENT to my VUSER SCRIPT in Vugen and then run the script in debug mode to make that the Vuser script does not fail and will refresh the script in controller and the START the scenario back.

I will look into the Log message window in controller and identify why the error is thrown & if needed I will make enhancement to my Vuser script in Vugen and then run the script in debug mode to make that the Vuser script does not fail and will refresh the script in controller and the start the scenario back.

AJAX (CLICK & SCRIPT) OR web (click & script) OR MS.Net PROTOCOLS.

Ajax (click & script) OR web (click & script) OR MS.Net protocols.

No.

No.

No.

No.

Identify the Scenarios → PLAN the LOAD Test → DESIGN The load Test (Scripting the Vuser) → Create the Scenario (Controller) → Design Scenario → Execute Scenario → Monitor the Scenario → GENERATE the REPORT → Analyse the Report

Identify the Scenarios → Plan the Load Test → Design The load Test (Scripting the Vuser) → Create the Scenario (Controller) → Design Scenario → Execute Scenario → Monitor the Scenario → Generate the Report → Analyse the Report

Not SURE.

Not sure.

TERM LICENSING for 1year with 500 VUSERS

Term Licensing for 1year with 500 Vusers

The standard log: it sends a subset of functions and messages sent during script execution to a log. The subset depends on the Vuser type.

Extended log: it sends a detailed script execution messages to the output log. This is mainly used during debugging when we want INFORMATION about: PARAMETER substitution. Data RETURNED by the server. Advanced TRACE.

The standard log: it sends a subset of functions and messages sent during script execution to a log. The subset depends on the Vuser type.

Extended log: it sends a detailed script execution messages to the output log. This is mainly used during debugging when we want information about: Parameter substitution. Data returned by the server. Advanced trace.

Think time is the time that a REAL USER waits between actions. Example: When a user receives data from a server, the user may wait several seconds to review the data before RESPONDING. This delay is KNOWN as the think time. Changing the Threshold: Threshold level is the level below which the recorded think time will be ignored. The default value is FIVE (5) seconds. We can change the think time threshold in the Recording options of the VuGen.

Think time is the time that a real user waits between actions. Example: When a user receives data from a server, the user may wait several seconds to review the data before responding. This delay is known as the think time. Changing the Threshold: Threshold level is the level below which the recorded think time will be ignored. The default value is five (5) seconds. We can change the think time threshold in the Recording options of the VuGen.

Vuser_end SECTION CONTAINS LOG off PROCEDURES.

Vuser_end section contains log off procedures.

Vuser_init ACTION CONTAINS PROCEDURES to LOGIN to a SERVER.

Vuser_init action contains procedures to login to a server.

LOAD test is planned to decide the number of users, what kind of machines we are going to use and from where they are run. It is BASED on 2 important documents, Task Distribution Diagram and Transaction profile. Task Distribution Diagram gives US the information on number of users for a particular transaction and the time of the load. The PEAK usage and off-usage are decided from this Diagram. Transaction profile gives us the information about the transactions name and their priority levels with regard to the scenario we are DECIDING.

Load test is planned to decide the number of users, what kind of machines we are going to use and from where they are run. It is based on 2 important documents, Task Distribution Diagram and Transaction profile. Task Distribution Diagram gives us the information on number of users for a particular transaction and the time of the load. The peak usage and off-usage are decided from this Diagram. Transaction profile gives us the information about the transactions name and their priority levels with regard to the scenario we are deciding.

OVERLAY Graph: It overlay the content of two graphs that shares a common x-axis. LEFT Y-axis on the merged graph show’s the current graph’s VALUE & RIGHT Y-axis show the value of Y-axis of the graph that was merged.

Correlate Graph: PLOT the Y-axis of two graphs against each other. The active graph’s Y-axis becomes X-axis of merged graph. Y-axis of the graph that was merged becomes merged graph’s Y-axis.

Overlay Graph: It overlay the content of two graphs that shares a common x-axis. Left Y-axis on the merged graph show’s the current graph’s value & Right Y-axis show the value of Y-axis of the graph that was merged.

Correlate Graph: Plot the Y-axis of two graphs against each other. The active graph’s Y-axis becomes X-axis of merged graph. Y-axis of the graph that was merged becomes merged graph’s Y-axis.

By running “Database” MONITOR and help of “Data RESOURCE Graph” we can FIND database related ISSUES. E.g. you can specify the resource you want to measure on before running the controller and than you can see database related issues.

By running “Database” monitor and help of “Data Resource Graph” we can find database related issues. E.g. you can specify the resource you want to measure on before running the controller and than you can see database related issues.

USING Web resource monitors we can find the PERFORMANCE of web servers. Using these monitors we can analyze throughput on the web server, NUMBER of hits per second that OCCURRED during scenario, the number of http responses per second, the number of downloaded pages per second.

Using Web resource monitors we can find the performance of web servers. Using these monitors we can analyze throughput on the web server, number of hits per second that occurred during scenario, the number of http responses per second, the number of downloaded pages per second.

The PROBLEM could be in the SYSTEM itself or in the APPLICATION SERVER or in the code written for the application.

The problem could be in the system itself or in the application server or in the code written for the application.

Performance Bottlenecks can be detected by USING monitors. These monitors might be application SERVER monitors, web server monitors, DATABASE server monitors and NETWORK monitors. They help in finding out the troubled area in our scenario which CAUSES increased response time. The measurements made are usually performance response time, throughput, hits/sec, network delay graphs, etc.

Performance Bottlenecks can be detected by using monitors. These monitors might be application server monitors, web server monitors, database server monitors and network monitors. They help in finding out the troubled area in our scenario which causes increased response time. The measurements made are usually performance response time, throughput, hits/sec, network delay graphs, etc.

The configuration of our systems refers to that of the client machines on which we run the Vusers. The configuration of any client machine includes its hardware settings, MEMORY, operating SYSTEM, software applications, development TOOLS, etc. This system component configuration should match with the overall system configuration that would include the network infrastructure, the web server, the database server, and any other components that GO with this larger system so as to achieve the LOAD testing objectives.

The configuration of our systems refers to that of the client machines on which we run the Vusers. The configuration of any client machine includes its hardware settings, memory, operating system, software applications, development tools, etc. This system component configuration should match with the overall system configuration that would include the network infrastructure, the web server, the database server, and any other components that go with this larger system so as to achieve the load testing objectives.

The Throughput graph shows the amount of data in bytes that the Vusers RECEIVED from the server in a second. When we compare this with the TRANSACTION RESPONSE time, we will NOTICE that as throughput decreased, the response time also decreased. Similarly, the peak throughput and highest response time would occur approximately at the same time.

The Throughput graph shows the amount of data in bytes that the Vusers received from the server in a second. When we compare this with the transaction response time, we will notice that as throughput decreased, the response time also decreased. Similarly, the peak throughput and highest response time would occur approximately at the same time.