Friday, October 7, 2011

Load Runner & QTP Interview Questions

1. What is load testing? - 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.
2. What is Performance testing? - Timing for both read and update
transactions should be gathered to determine whether system functions are
being performed in an acceptable timeframe. 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.
3. Did u use LoadRunner? What version? - Yes. Version 7.2.
4. Explain the Load testing process? -
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 LoadRunner 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. LoadRunner 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 LoadRunner online 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, LoadRunner records the performance of the application under
different loads. We use LoadRunner’s graphs and reports to analyze the
application’s performance.
5. When do you do load and performance Testing? - 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.
6. What are the components of LoadRunner? - The components of LoadRunner are
The Virtual User Generator, Controller, and the Agent process, LoadRunner
Analysis and Monitoring, LoadRunner Books Online.
7. What Component of LoadRunner would you use to record a Script? - 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.
8. What Component of LoadRunner would you use to play Back the script in
multi user mode? - 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.
9. What is a rendezvous point? - 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.
10. What is a scenario? - 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.
11. Explain the recording mode for web Vuser script? - 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.
12. Why do you create parameters? - 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.
13. What is correlation? Explain the difference between automatic
correlation and manual correlation? - 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.
14. How do you find out where correlation is required? Give few examples
from your projects? - 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.
15. Where do you set automatic correlation options? - 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.
16. What is a function to capture dynamic values in the web Vuser script? -
Web_reg_save_param function saves dynamic data information to a parameter.
17. When do you disable log in Virtual User Generator, When do you choose
standard and extended logs? - 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.
18. How do you debug a LoadRunner script? - 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.
19. How do you write user defined functions in LR? Give me few functions you
wrote in your previous project? - 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* (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.
20. What are the changes you can make in run-time settings? - 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
multithreading and whether each step as a transaction.
21. Where do you set Iteration for Vuser testing? - We set Iterations in the
Run Time Settings of the VuGen. The navigation for this is Run time
settings, Pacing tab, set number of iterations.
22. How do you perform functional testing under load? - Functionality under
load can be tested by running several Vusers concurrently. By increasing the
amount of Vusers, we can determine how much load the server can sustain.
23. What is Ramp up? How do you set this? - This option is used to gradually
increase the amount of Vusers/load on the server. An initial value is set
and a value to wait between intervals can be
specified. To set Ramp Up, go to ‘Scenario Scheduling Options’
24. What is the advantage of running the Vuser as thread? - VuGen provides
the facility to use multithreading. This enables more Vusers to be run per
generator. If the Vuser is run as a process, the same driver program is
loaded into memory for each Vuser, thus taking up a large amount of memory.
This limits the number of Vusers that can be run on a single
generator. If the Vuser is run as a thread, only one instance of the driver
program is loaded into memory for the given number of
Vusers (say 100). Each thread shares the memory of the parent driver
program, thus enabling more Vusers to be run per generator.
25. If you want to stop the execution of your script on error, how do you do
that? - The lr_abort function aborts the execution of a Vuser script. It
instructs the Vuser to stop executing the Actions section, execute the
vuser_end section and end the execution. This function is useful when you
need to manually abort a script execution as a result of a specific error
condition. When you end a script using this function, the Vuser is assigned
the status "Stopped". For this to take effect, we have to first uncheck the
“Continue on error” option in Run-Time Settings.
26. What is the relation between Response Time and Throughput? - 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.
27. Explain the Configuration of your systems? - 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.
28. How do you identify the performance bottlenecks? - 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.
29. If web server, database and Network are all fine where could be the
problem? - The problem could be in the system itself or in the application
server or in the code written for the application.
30. How did you find web server 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.
31. How did you find 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
32. Explain all the web recording options?
33. What is the difference between Overlay graph and Correlate graph? -
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.
34. How did you plan the Load? What are the Criteria? - 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.
35. What does vuser_init action contain? - Vuser_init action contains
procedures to login to a server.
36. What does vuser_end action contain? - Vuser_end section contains log off
procedures.
37. What is think time? How do you change the threshold? - 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.
38. What is the difference between standard log and extended log? - The
standard log sends a subset of functions and messages sent during script
execution to a log. The subset depends on the Vuser type Extended log 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.
39. Explain the following functions: - lr_debug_message - The
lr_debug_message function sends a debug message to the output log when the
specified message class is set. lr_output_message - The lr_output_message
function sends notifications to the Controller Output window and the Vuser
log file. lr_error_message - The lr_error_message function sends an error
message to the LoadRunner Output window. lrd_stmt - The lrd_stmt function
associates a character string (usually a SQL statement) with a cursor. This
function sets a SQL statement to be processed. lrd_fetch - The lrd_fetch
function fetches the next row from the result set.
40. Throughput - If the throughput scales upward as time progresses and the
number of Vusers increase, this indicates that the bandwidth is sufficient.
If the graph were to remain relatively flat as the number of Vusers
increased, it would
be reasonable to conclude that the bandwidth is constraining the volume of
data delivered.
41. Types of Goals in Goal-Oriented Scenario - Load Runner provides you with
five different types of goals in a goal oriented scenario:
o The number of concurrent Vusers
o The number of hits per second
o The number of transactions per second
o The number of pages per minute
o The transaction response time that you want your scenario
42. Analysis Scenario (Bottlenecks): In Running Vuser graph correlated with
the response time graph you can see that as the number of Vusers increases,
the average response time of the check itinerary transaction very gradually
increases. In other words, the average response time steadily increases as
the load
increases. At 56 Vusers, there is a sudden, sharp increase in the average
response
time. We say that the test broke the server. That is the mean time before
failure (MTBF). The response time clearly began to degrade when there were
more than 56 Vusers running simultaneously.
43. What is correlation? Explain the difference between automatic
correlation and manual correlation? - 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.
44. Where do you set automatic correlation options? - 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.
45. What is a function to capture dynamic values in the web vuser script? -
Web_reg_save_param function saves dynamic data information to a parameter.

QTP interview questions


1. What are the Features & Benefits of Quick Test Pro (QTP 8.0)? - Operates
stand-alone, or integrated into Mercury Business Process Testing and Mercury
Quality Center. Introduces next-generation zero-configuration Keyword Driven
testing technology in Quick Test Professional 8.0 allowing for fast test
creation, easier maintenance, and more powerful data-driving capability.
Identifies objects with Unique Smart Object Recognition, even if they change
from build to build, enabling reliable unattended script execution.
Collapses test documentation and test creation to a single step with
Auto-documentation technology. Enables thorough validation of applications
through a full complement of checkpoints.
2. How to handle the exceptions using recovery scenario manager in QTP? -
There are 4 trigger events during which a recovery scenario should be
activated. A pop up window appears in an opened application during the test
run: A property of an object changes its state or value, A step in the test
does not run successfully, An open application fails during the test run,
These triggers are considered as exceptions.You can instruct QTP to recover
unexpected events or errors that occurred in your testing environment during
test run. Recovery scenario manager provides a wizard that guides you
through the defining recovery scenario. Recovery scenario has three steps:
1. Triggered Events 2. Recovery steps 3. Post Recovery Test-Run
3. What is the use of Text output value in QTP? - Output values enable to
view the values that the application talks during run time. When
parameterized, the values change for each iteration. Thus by creating output
values, we can capture the values that the application takes for each run
and output them to the data table.
4. How to use the Object spy in QTP 8.0 version? - There are two ways to Spy
the objects in QTP: 1) Thru file toolbar, In the File Toolbar click on the
last toolbar button (an icon showing a person with hat). 2) True Object
repository Dialog, In Object repository dialog click on the button object
spy. In the Object spy Dialog click on the button showing hand symbol. The
pointer now changes in to a hand symbol and we have to point out the object
to spy the state of the object if at all the object is not visible. or
window is minimized then, hold the Ctrl button and activate the required
window to and release the Ctrl button.
5. How Does Run time data (Parameterization) is handled in QTP? - You can
then enter test data into the Data Table, an integrated spreadsheet with the
full functionality of Excel, to manipulate data sets and create multiple
test iterations, without programming, to expand test case coverage. Data can
be typed in or imported from databases, spreadsheets, or text files.
6. What is keyword view and Expert view in QTP? - Quick Test’s Keyword
Driven approach, test automation experts have full access to the underlying
test and object properties, via an integrated scripting and debugging
environment that is round-trip synchronized with the Keyword View. Advanced
testers can view and edit their tests in the Expert View, which reveals the
underlying industry-standard VBScript that Quick Test Professional
automatically generates. Any changes made in the Expert View are
automatically synchronized with the Keyword View.
7. Explain about the Test Fusion Report of QTP? - Once a tester has run a
test, a Test Fusion report displays all aspects of the test run: a
high-level results overview, an expandable Tree View of the test specifying
exactly where application failures occurred, the test data used, application
screen shots for every step that highlight any discrepancies, and detailed
explanations of each checkpoint pass and failure. By combining Test Fusion
reports with Quick Test Professional, you can share reports across an entire
QA and development team.
8. Which environments does QTP support? - Quick Test Professional supports
functional testing of all enterprise environments, including Windows,
Web,..NET, Java/J2EE, SAP, Siebel, Oracle, PeopleSoft, Visual Basic,
ActiveX, mainframe terminal emulators, and Web services.
9. What is QTP? - Quick Test is a graphical interface record-playback
automation tool. It is able to work with any web, java or windows client
application. Quick Test enables you to test standard web objects and ActiveX
controls. In addition to these environments, Quick Test Professional also
enables you to test Java applets and applications and multimedia objects on
Applications as well as standard Windows applications, Visual Basic 6
applications and.NET framework applications
10. Explain QTP Testing process? - Quick Test testing process consists of 6
main phases:
11. Create your test plan - Prior to automating there should be a detailed
description of the test including the exact steps to follow, data to be
input, and all items to be verified by the test. The verification
information should include both data validations and existence or state
verifications of objects in the application.
12. Recording a session on your application - As you navigate through your
application, Quick Test graphically displays each step you perform in the
form of a collapsible icon-based test tree. A step is any user action that
causes or makes a change in your site, such as clicking a link or image, or
entering data in a form.
13. Enhancing your test - Inserting checkpoints into your test lets you
search for a specific value of a page, object or text string, which helps
you identify whether or not your application is functioning correctly. NOTE:
Checkpoints can be added to a test as you record it or after the fact via
the Active Screen. It is much easier and faster to add the checkpoints
during the recording process. Broadening the scope of your test by replacing
fixed values with parameters lets you check how your application performs
the same operations with multiple sets of data. Adding logic and conditional
statements to your test enables you to add sophisticated checks to your
test.
14. Debugging your test - If changes were made to the script, you need to
debug it to check that it operates smoothly and without interruption.
15. Running your test on a new version of your application - You run a test
to check the behavior of your application. While running, Quick Test
connects to your application and performs each step in your test.
16. Analyzing the test results - You examine the test results to pinpoint
defects in your application.
17. Reporting defects - As you encounter failures in the application when
analyzing test results, you will create defect reports in Defect Reporting
Tool.
18. Explain the QTP Tool interface. - It contains the following key
elements: Title bar, displaying the name of the currently open test, Menu
bar, displaying menus of Quick Test commands, File toolbar, containing
buttons to assist you in managing tests, Test toolbar, containing buttons
used while creating and maintaining tests, Debug toolbar, containing buttons
used while debugging tests. Note: The Debug toolbar is not displayed when
you open Quick Test for the first time. You can display the Debug toolbar by
choosing View — Toolbars — Debug. Action toolbar, containing buttons and a
list of actions, enabling you to view the details of an individual action or
the entire test flow. Note: The Action toolbar is not displayed when you
open Quick Test for the first time. You can display the Action toolbar by
choosing View — Toolbars — Action. If you insert a reusable or external
action in a test, the Action toolbar is displayed automatically. Test pane,
containing two tabs to view your test-the Tree View and the Expert View
,Test Details pane, containing the Active Screen. Data Table, containing two
tabs, Global and Action, to assist you in parameterizing your test. Debug
Viewer pane, containing three tabs to assist you in debugging your
test-Watch Expressions, Variables, and Command. (The Debug Viewer pane can
be opened only when a test run pauses at a breakpoint.) Status bar,
displaying the status of the test
19. How does QTP recognize Objects in AUT? - Quick Test stores the
definitions for application objects in a file called the Object Repository.
As you record your test, Quick Test will add an entry for each item you
interact with. Each Object Repository entry will be identified by a logical
name (determined automatically by Quick Test), and will contain a set of
properties (type, name, etc) that uniquely identify each object. Each line
in the Quick Test script will contain a reference to the object that you
interacted with, a call to the appropriate method (set, click, check) and
any parameters for that method (such as the value for a call to the set
method). The references to objects in the script will all be identified by
the logical name, rather than any physical, descriptive properties.
20. What are the types of Object Repositories in QTP? - Quick Test has two
types of object repositories for storing object information: shared object
repositories and action object repositories. You can choose which type of
object repository you want to use as the default type for new tests, and you
can change the default as necessary for each new test. The object repository
per-action mode is the default setting. In this mode, Quick Test
automatically creates an object repository file for each action in your test
so that you can create and run tests without creating, choosing, or
modifying object repository files. However, if you do modify values in an
action object repository, your changes do not have any effect on other
actions. Therefore, if the same test object exists in more than one action
and you modify an object’s property values in one action, you may need to
make the same change in every action (and any test) containing the object.
21. Explain the check points in QTP? - A checkpoint verifies that expected
information is displayed in an Application while the test is running. You
can add eight types of checkpoints to your test for standard web objects
using QTP. A page checkpoint checks the characteristics of an Application. A
text checkpoint checks that a text string is displayed in the appropriate
place on an Application. An object checkpoint (Standard) checks the values
of an object on an Application. An image checkpoint checks the values of an
image on an Application. A table checkpoint checks information within a
table on a Application. An Accessibilityy checkpoint checks the web page for
Section 508 compliance. An XML checkpoint checks the contents of individual
XML data files or XML documents that are part of your Web application. A
database checkpoint checks the contents of databases accessed by your web
site
22. In how many ways we can add check points to an application using QTP? -
We can add checkpoints while recording the application or we can add after
recording is completed using Active screen (Note : To perform the second one
The Active screen must be enabled while recording).
23. How does QTP identify objects in the application? - QTP identifies the
object in the application by Logical Name and Class.
24. What is Parameterizing Tests? - When you test your application, you may
want to check how it performs the same operations with multiple sets of
data. For example, suppose you want to check how your application responds
to ten separate sets of data. You could record ten separate tests, each with
its own set of data. Alternatively, you can create a parameterized test that
runs ten times: each time the test runs, it uses a different set of data.
25. What is test object model in QTP? - The test object model is a large set
of object types or classes that Quick Test uses to represent the objects in
your application. Each test object class has a list of properties that can
uniquely identify objects of that class and a set of relevant methods that
Quick Test can record for it. A test object is an object that Quick Test
creates in the test or component to represent the actual object in your
application. Quick Test stores information about the object that will help
it identify and check the object during the run session.
26. What is Object Spy in QTP? - Using the Object Spy, you can view the
properties of any object in an open application. You use the Object Spy
pointer to point to an object. The Object Spy displays the selected object’s
hierarchy tree and its properties and values in the Properties tab of the
Object Spy dialog box.
27. What is the Diff between Image check-point and Bit map Check point? -
Image checkpoints enable you to check the properties of a Web image. You can
check an area of a Web page or application as a bitmap. While creating a
test or component, you specify the area you want to check by selecting an
object. You can check an entire object or any area within an object. Quick
Test captures the specified object as a bitmap, and inserts a checkpoint in
the test or component. You can also choose to save only the selected area of
the object with your test or component in order to save disk Space. For
example, suppose you have a Web site that can display a map of a city the
user specifies. The map has control keys for zooming. You can record the new
map that is displayed after one click on the control key that zooms in the
map. Using the bitmap checkpoint, you can check that the map zooms in
correctly. You can create bitmap checkpoints for all supported testing
environments (as long as the appropriate add-ins are loaded). Note: The
results of bitmap checkpoints may be affected by factors such as operating
system, screen resolution, and color settings.
28. How many ways we can parameterize data in QTP? - There are four types of
parameters: Test, action or component parameters enable you to use values
passed from your test or component, or values from other actions in your
test. Data Table parameters enable you to create a data-driven test (or
action) that runs several times using the data you supply. In each
repetition, or iteration, Quick Test uses a different value from the Data
Table. Environment variable parameters enable you to use variable values
from other sources during the run session. These may be values you supply,
or values that Quick Test generates for you based on conditions and options
you choose. Random number parameters enable you to insert random numbers as
values in your test or component. For example, to check how your application
handles small and large ticket orders, you can have Quick Test generate a
random number and insert it in a number of tickets edit field.
29. How do u do batch testing in WR & is it possible to do in QTP, if so
explain? - Batch Testing in WR is nothing but running the whole test set by
selecting Run Test set from the Execution Grid. The same is possible with
QTP also. If our test cases are automated then by selecting Run Test set all
the test scripts can be executed. In this process the Scripts get executed
one by one by keeping all the remaining scripts in Waiting mode.
30. If I give some thousand tests to execute in 2 days what do u do? - Adhoc
testing is done. It Covers the least basic functionalities to verify that
the system is working fine.
31. What does it mean when a check point is in red color? what do u do? - A
red color indicates failure. Here we analyze the cause for failure whether
it is a Script Issue or Environment Issue or a Application issue.
32. What is Object Spy in QTP? - Using the Object Spy, you can view the
properties of any object in an open application. You use the Object Spy
pointer to point to an object. The Object Spy displays the selected object’s
hierarchy tree and its properties and values in the Properties tab of the
Object Spy dialog box.
33. What is the file extension of the code file & object repository

1 comment: