Q51.
What Is .lrs?
Answer
:
Load
Runner save the information in a scenario files.
Q52.
What Is Scenario Wizard?
Answer
:
Through
scenario wizard we can create a new scenario.
Q53.
What Is Filtering And Sorting?
Answer
:
We
can filter the information display only those items that meet the
selected criteria(filter box) .exam you can filter vuser only those
who are in ready state. Sorting - we can sort all the vuser in the
vuser list. In order to their vuser ID(1,2,3,4,5,6,7,8,9).
Q54.
What Are The Information Crating For Each Host?
Answer
:
1-the
status of the host.
2-the platform type of the
host(windows/Unix).
3-details of the scenario.
Q55.
How To Create A Host List For A Scenario?
Answer
:
1-install
remote command luncher on every machine.
2-add the name of the
host to the host lists.
3-set attributes for each host.
4-select
which hosts will take part in the scenario.
Q56.
What The Host Attributes Determine?
Answer
:
1-the
maximum number of vuser that host can run.
2-the initialization
quota .
3-the location of the Win-runner configuration file.
4.
the location of the file during run-time.
Q57.
How You Set Maximum Number Of Vuser That A Host Can Run?
Answer
:
We
can modify the maximum number of vuser according to the (available
resource , the needs of your scenario, Load Runner license
agreements).
Q58.
What Do You Mean By Initialization Of Quota?
Answer
:
Capabilities
of the host that at a time how many vuser Are initialize .
Q59.
What Is Scenario Default?
Answer
:
Instruct
the vuser to use the Win-runner configuration file.
Q60.
What Is Local Configuration File?
Answer
:
Instruct
the vuser to use hosts Win-runner configuration file.
Q61.
What Do You Mean By Path?
Answer
:
Use
Win-runner configuration file that is in a specific location on the
network.
Q62.
During Run Time Where The Hosts Saves The Files?
Answer
:
In
temporally in the local drive of each host.
Q63.
What Is Script List?
Answer
:
It
contain all the vuser script that vuser can run.
Q64.
What Are The Information Contain By Script Windows For Each Script In
The List?
Answer
:
1-name
of the vuser script .
2-the type of the vuser.
3-the
location(path).
4-command line option.
Q65.
How To Modify The Script?
Answer
:
Using
vuser script information dialog box.
Q66.
What Is The Purpose Of Running The Scenario?
Answer
:
To
check the response time of the client/server system under load.
Q67.
Why We Insert The Rendezvous Point While Running The Scenario?
Answer
:
If
a multiple vuser to perform a tasks at exactly the same time.
Q68.
When A Scenario Run Exactly What Happened?
Answer
:
1-The
controller check the scenario configuration information.
2-then
next it invoke the application that you select to run with the
scenario .
3- then transform each script to its related hosts,
when the vuser are ready they start execution.
Q69.
How To Run A Scenario?
Answer
:
Open
an existing scenario .
Configure the scenario.
Set the
result directory.
Run the scenario.
Q70.
When You Initialize The Vuser What Happen?
Answer
:
The
vuser status change from DOWN to PENDING to INITIALIZING to READY. If
vuser fails to initialize , the vuser status changes to ERROR.
Q71.
What Is Pause Command?
Answer
:
It
changes the status of the vuser from RUNNING TO PAUSE.
Q72.
What Is Running Virtual User Graph?
Answer
:
It
displays the number of the vuser that execute vuser script during
each second of the scenario run. Only running and rendez state are
include.(loading, ready and pause are not displayed).
Q73.
What Is Report Viewer?
Answer
:
Each
report viewer contain the report header and report viewer tool bar.
Q74.
What Is Report Header And What Are The Information Contains?
Answer
:
It
display general scenario information and it contain the information
like (title, scenario, result start time, end time and duration).
Q75.
What Is Rendezvous Graph?
Answer
:
It
indicate when vuser were released from rendezvous point and how many
vuser are released from each point. it help the transaction
performance time .
Q76.
What Is Transaction Per Second Graph(pass)?
Answer
:
It
display the number of completed , successful transaction perform
during each second of scenario run.
Q77.
What In Percentile Graph?
Answer
:
The
percentage of transaction that were performed within a given time
range.
Q78.
What Is Transaction Performance Graph?
Answer
:
Display
the average time taken to perform transaction during each second of
the scenario run.
Q79.
What Are All The Types Of Correlation?
Answer
:
Manual
& Automatic Co-relation
Manual
correlation - Correlation is used to obtain data which are unique for
each run of the script and which are generated by nested queries.
Automatic
correlation is where we set some rules for correlation. It can be
application server specific. Here values are replaced by data, which
are created by these rules.
Q80.
What Is Load Testing?
Answer
:
Load
testing is to test that if the application works fine with the loads
that result from large number of simultaneous users, transactions and
to determine weather it can handle peak usage periods.
Q81.
What Is Performance Testing?
Answer
:
Timing
for both read and update transactions should be gathered to determine
whether system functions are being performed in an acceptable
time-frame. This should be done standalone and then in a multi user
environment to determine the effect of multiple transactions on the
timing of a single transaction.
Q82.
Did U Use Load Runner? What Version?
Answer
:
Yes.
Version 12.60
Q83.
Explain The Load Testing Process?
Answer
:
Step
1: Planning the test. Here, we develop a clearly defined test plan to
ensure the test scenarios we develop will accomplish load-testing
objectives.
Step
2: Creating Vusers. Here, we create Vuser scripts that contain tasks
performed by each Vuser, tasks performed by Vusers as a whole, and
tasks measured as transactions.
Step
3: Creating the scenario. A scenario describes the events that occur
during a testing session. It includes a list of machines, scripts,
and Vusers that run during the scenario. We create scenarios using
Load Runner Controller. We can create manual scenarios as well as
goal-oriented scenarios. In manual scenarios, we define the number of
Vusers, the load generator machines, and percentage of Vusers to be
assigned to each script. For web tests, we may create a goal-oriented
scenario where we define the goal that our test has to achieve. Load
Runner automatically builds a scenario for us.
Step
4: Running the scenario. We emulate load on the server by instructing
multiple Vusers to perform tasks simultaneously. Before the testing,
we set the scenario configuration and scheduling. We can run the
entire scenario, Vuser groups, or individual Vusers.
Step
5: Monitoring the scenario. We monitor scenario execution using the
Load Runner on-line runtime, transaction, system resource, Web
resource, Web server resource, Web application server resource,
database server resource, network delay, streaming media resource,
firewall server resource, ERP server resource, and Java performance
monitors. Step 6: Analyzing test results. During scenario execution,
Load Runner records the performance of the application under
different loads. We use Load Runner’s graphs and reports to analyze
the application’s performance.
Q84.
When Do You Do Load And Performance Testing?
Answer
:
We
perform load testing once we are done with interface (GUI) testing.
Modern system architectures are large and complex. Whereas single
user testing primarily on functionality and user interface of a
system component, application testing focuses on performance and
reliability of an entire system. For example, a typical
application-testing scenario might depict 1000 users logging in
simultaneously to a system. This gives rise to issues such as what is
the response time of the system, does it crash, will it go with
different software applications and platforms, can it hold so many
hundreds and thousands of users, etc. This is when we set do load and
performance testing.
Q85.
What Are The Components Of Load Runner?
Answer
:
The
components of Load Runner are the Virtual User Generator, Controller,
and the Agent process, Load Runner Analysis and Monitoring.
Q86.
What Component Of Load Runner Would You Use To Record A Script?
Answer
:
The
Virtual User Generator (VuGen) component is used to record a script.
It enables you to develop Vuser scripts for a variety of application
types and communication protocols.
Q87.
What Component Of Load Runner Would You Use To Play Back The Script
In Multi User Mode?
Answer
:
The
Controller component is used to playback the script in multi-user
mode. This is done during a scenario run where a Vuser script is
executed by a number of Vusers in a group.
Q88.
What Is A Rendezvous Point?
Answer
:
You
insert rendezvous points into Vuser scripts to emulate heavy user
load on the server. Rendezvous points instruct Vusers to wait during
test execution for multiple Vusers to arrive at a certain point, in
order that they may simultaneously perform a task. For example, to
emulate peak load on the bank server, you can insert a rendezvous
point instructing 100 Vusers to deposit cash into their accounts at
the same time.
Q89.
What Is A Scenario?
Answer
:
A
scenario defines the events that occur during each testing session.
For example, a scenario defines and controls the number of users to
emulate, the actions to be performed, and the machines on which the
virtual users run their emulations.
Q90.
Explain The Recording Mode For Web Vuser Script?
Answer
:
We
use VuGen to develop a Vuser script by recording a user performing
typical business processes on a client application. VuGen creates the
script by recording the activity between the client and the server.
For example, in web based applications, VuGen monitors the client end
of the database and traces all the requests sent to, and received
from, the database server. We use VuGen to: Monitor the communication
between the application and the server; Generate the required
function calls; and Insert the generated function calls into a Vuser
script.
Q91.
Why Do You Create Parameters?
Answer
:
Parameters
are like script variables. They are used to vary input to the server
and to emulate real users. Different sets of data are sent to the
server each time the script is run. Better simulate the usage model
for more accurate testing from the Controller; one script can emulate
many different users on the system.
Q92.
What Is Correlation? Explain The Difference Between Automatic
Correlation And Manual Correlation?
Answer
:
Correlation
is used to obtain data which are unique for each run of the script
and which are generated by nested queries. Correlation provides the
value to avoid errors arising out of duplicate values and also
optimizing the code (to avoid nested queries). Automatic correlation
is where we set some rules for correlation. It can be application
server specific. Here values are replaced by data which are created
by these rules. In manual correlation, the value we want to correlate
is scanned and create correlation is used to correlate.
Q93.
How Do You Find Out Where Correlation Is Required? Give Few Examples
From Your Projects?
Answer
:
Two
ways: First we can scan for correlations, and see the list of values
which can be correlated. From this we can pick a value to be
correlated. Secondly, we can record two scripts and compare them. We
can look up the difference file to see for the values which needed to
be correlated. In my project, there was a unique id developed for
each customer, it was nothing but Insurance Number, it was generated
automatically and it was sequential and this value was unique. I had
to correlate this value, in order to avoid errors while running my
script. I did using scan for correlation.
Q94.
Where Do You Set Automatic Correlation Options?
Answer
:
Automatic
correlation from web point of view can be set in recording options
and correlation tab. Here we can enable correlation for the entire
script and choose either issue online messages or offline actions,
where we can define rules for that correlation. Automatic correlation
for database can be done using show output window and scan for
correlation and picking the correlate query tab and choose which
query value we want to correlate. If we know the specific value to be
correlated, we just do create correlation for the value and specify
how the value to be created.
Q95.
What Is A Function To Capture Dynamic Values In The Web Vuser Script?
Answer
:
Web_reg_save_param
function saves dynamic data information to a parameter.
Q96.
When Do You Disable Log In Virtual User Generator, When Do You Choose
Standard And Extended Logs?
Answer
:
Once
we debug our script and verify that it is functional, we can enable
logging for errors only. When we add a script to a scenario, logging
is automatically disabled. Standard Log Option: When you select
Standard log, it creates a standard log of functions and messages
sent during script execution to use for debugging. Disable this
option for large load testing scenarios. When you copy a script to a
scenario, logging is automatically disabled Extended Log Option:
Select extended log to create an extended log, including warnings and
other messages. Disable this option for large load testing scenarios.
When you copy a script to a scenario, logging is automatically
disabled. We can specify which additional information should be added
to the extended log using the extended log options.
Q97.
How Do You Debug A Load Runner Script?
Answer
:
VuGen
contains two options to help debug Vuser scripts-the Run Step by Step
command and breakpoints. The Debug settings in the Options dialog box
allow us to determine the extent of the trace to be performed during
scenario execution. The debug information is written to the Output
window. We can manually set the message class within your script
using the lr_set_debug_message function. This is useful if we want to
receive debug information about a small section of the script only.
Q98.
How Do You Write User Defined Functions In Lr? Give Me Few Functions
You Wrote In Your Previous Project?
Answer
:
Before
we create the User Defined functions we need to create the external
library (DLL) with the function. We add this library to VuGen bin
directory. Once the library is added then we assign user defined
function as a parameter. The function should have the following
format: __declspec (dllexport) char* <function name> (char*,
char*) Examples of user defined functions are as follows: GetVersion,
GetCurrentTime, GetPltform are some of the user defined functions
used in my earlier project.
Q99.
What Are The Changes You Can Make In Run-time Settings?
Answer
:
The
Run Time Settings that we make are: a) Pacing - It has iteration
count. b) Log - Under this we have Disable Logging Standard Log and
c) Extended Think Time - In think time we have two options like
Ignore think time and Replay think time. d) General - Under general
tab we can set the Vusers as process or as multi-threading and
whether each step as a transaction.
Q100.
Where Do You Set Iteration For Vuser Testing?
Answer
:
We
set Iterations in the Run Time Settings of the VuGen. The navigation
for this is Run time settings, Pacing tab, and set number of
iterations.
No comments:
Post a Comment