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.
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
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.
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.
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.
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.
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.
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
Explain QTP Testing
process?
- Quick Test testing process consists of 6 main phases:
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.
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.
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.
Debugging your test - If changes were made to the script,
you need to debug it to check that it operates smoothly and without
interruption.
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.
Analyzing the test
results - You examine the test results to pinpoint defects in your
application.
Reporting defects
- As you encounter failures in the application when analyzing test results, you
will create defect reports in Defect Reporting Tool.
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
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.
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.
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
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).
How does QTP identify
objects in the application? - QTP identifies the object in the application
by Logical Name and Class.
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.
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.
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.
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.
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.
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.
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.
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.
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.
What is the file
extension of the code file & object repository file in QTP? - Code file
extension is.vbs and object repository is.tsr
Explain the concept
of object repository & how QTP recognizes objects? - Object Repository:
displays a tree of all objects in the current component or in the current
action or entire test (depending on the object repository mode you selected).
We can view or modify the test object description of any test object in the
repository or to add new objects to the repository. Quicktest learns the
default property values and determines in which test object class it fits. If
it is not enough it adds assistive properties, one by one to the description
until it has compiled the unique description. If no assistive properties are
available, then it adds a special Ordinal identifier such as objects location
on the page or in the source code.
What are the properties you would use for identifying a
browser & page when using descriptive programming? - Name would be another
property apart from title that we can use.
Give me an example
where you have used a COM interface in your QTP project? - com interface
appears in the scenario of front end and back end. for eg:if you r using oracle
as back end and front end as VB or any language then for better compatibility
we will go for an interface. of which COM will be one among those interfaces.
Create object creates handle to the instance of the specified object so that we
program can use the methods on the specified object. It is used for
implementing Automation(as defined by Microsoft).
Explain in brief
about the QTP Automation Object Model. - Essentially all configuration and
run functionality provided via the Quick Test interface is in some way
represented in the Quick Test automation object model via objects, methods, and
properties. Although a one-on-one comparison cannot always be made, most dialog
boxes in Quick Test have a corresponding automation object, most options in
dialog boxes can be set and/or retrieved using the corresponding object
property, and most menu commands and other operations have corresponding
automation methods. You can use the objects, methods, and properties exposed by
the Quick Test automation object model, along with standard programming
elements such as loops and conditional statements to design your program.
No comments:
Post a Comment