Qtp interview questions_1

For more QTP Scripts, visit www.ramupalanki.com

Q:I have a user interface in the application which has windows with the same
labels. So when I make a recovery scenario, how do I distinguish the one with
the labels and the one without as I do not want the recovery scenarios to be
called on the wrong one?
A:When defining the identification criteria in the pop-up trigger, you can also use the
text within the window (or a substring from it) on top of the window title, as the
differentiator between the windows.

Q:Can it be confirmed that QualityCenter works with Microsoft SQL Server?
A:Yes, Quality Center supports MS SQL server 2000 Enterprise edition.

Q:What is the best approach for migrating both test cases and defect entries
from the home-grown application to QualityCenter?
A:We recommend you use the Word / Excel add-in and import the data into Quality
Center.

Q:We're using QTP v8.0 and capturing GUI with formatted numeric fields such
as currency, etc. with commas and decimal. QTP does not capture the input
(so that I can parameterize this later), but captures the formatted field after
entry. How do I make QTP capture my input instead of the formatted field?
How do I validate this formatted field that it contains valid input?
A:1. If your numeric fields are edit boxes and QTP record commands like WinEdit.Set
"1,234.56" Then just replace Set command with Type command like WinEdit.Type
"1234.56"

2. In order to check the numeric value of the formatted field use VBS functions to
convert from strings to numbers. For example:
text = WinEdit.GetROProperty("text") ' returns string "1,234.56"
num = CDbl(text) ' returns number 1234.56
num1 = CInt(text) ' returns integer number 1235

More information is needed about this issue. But it sounds like a Data Table formatting
issue where the text is being captured in one format but it shows up in QTP's data
table in another format

Q:One of the biggest highlights of the conference has been the concept of
employing the BTO strategy while utilizing outsourced resources. How is
Quality Center going to handle application security since these different
resources may not exist on a common intranet?
A:Since Quality Center utilizes HTTP communication through port 80, it works for both
intranet and the internet environments. You are correct that outsourcing adds new
security requirements. In addition, Mercury offers Quality Center as a managed
service, which has further security requirements. For Quality Center 8.2, we have
added support for Secure LDAP. And we will continue to enhance the security
capabilities of Quality Center in upcoming releases. We will implement our electronic
signature solution for Quality Center, add a more flexible security group structure, and
improve integrations with existing security and identity management infrastructure.

Q:I am trying to run tests from command line using QTPlaunch.exe with close
option after executing the test. In my driver script execution it will set results
file folder and other settings. Once the test is scheduled at the end it will ask
for save option, this causes manual interference to accept yes or no. We need
to fix this in order to execute the test unattended fashion using QTP command
line utilities.

www.ramupalanki.com Page 1

A:We suggest you try restoring the default settings at the end of the test run to
alleviate the problem. Note that in general, we recommend that using the command
line option for automation be dropped in favor of using the QTP Automation API. If
these suggestions do not resolve your issues, please do not hesitate to contact CSO for
further assistance.

Q:Is Mercury planning to improve its reporting capability in TD?
A:We believe that a tremendous amount of valuable information is generated during
the quality process, and the ability to make use of that information for better decision
making and project management is one of the key differentiators of TestDirector for
Quality Center. To that end, we do plan to continue to improve the reporting capability
of TestDirector as part of Quality Center. With Quality Center 8.2, we have enhanced
the Dashboard and updated the Advanced Reports add-in. In upcoming releases, we
will continue to enhance the dashboard, standard reports, and advanced reports.

Q:We are trying to run TD 8 through Citrix. First, we get a user login error
message when it first displays but we can move past that and login. Then all
of the colors are off - not correct and the graphics are bad. What can we do?
A:Citrix is not an officially supported environment at this time, although we are aware
of many customers who are successfully using TestDirector in a Citrix environment. It
is possible that one of these customers can give you some insight into the issues you
are experiencing and provide some suggestions. The best place to interact with other
customers is through the forums on the CSO website. We are investigating the
possibility of adding support for Citrix in the near future. Please check for news and
alerts on the CSO website.

Q:What plans are there to improve WinRunner's and LoadRunner's "behavior"
with Oracle Apps 11.5.9? Currently I cannot upgrade to WR 7.6 because the
synchronization doesn't work [with Oracle 11.5.9] and I already have 2
patches (one custom, and another on the way) to try to make LR 7.8 FP1
work with 11.5.9.
A:WinRunner 7.6 indeed had some synchronization issues with WR 7.6 Oracle Add-In
and Oracle Apps 11.5.9. These issues were resolved with WR76JP11 (Fixes
synchronization mechanism and several other minor issues).

Q:When will we have an integrated process that automatically extracts
requirements, writes and tests programs?
A:This is indeed a grand, long-term vision. Mercury is committed to improving and
automating the overall quality process. We are constantly looking at ways to integrate
with other solutions, like our own IT Governance center, and to automate additional
aspects of quality assurance. A great example is the auto-documentation feature of the
new Business Process Testing (BPT) module within Quality Center. Auto-documentation
combines the previously separate steps of documenting a test and actually executing
the test, significantly reducing the overall effort.

Q:Upgrade of Test Director from 7.x to 8.0; Discuss best approaches and
complications and pitfalls and benefits from the upgrade also things to watch
out for...
A:We have a "Best Practices" document in the KB about upgrading to TD 8.0. CSO
website - Download section or KB, you can search for "Best Practices"

Q:We are using Loadrunner 7.8 FP1.In that we have load distribution graph,
response time Vs transactions per sec (rounded to nearest sec). We are
running tests on j2ee application where expected response times are in milli
seconds (ex 150 millisecond per method). Because rounding to sec we are


seeing all transactions below 1 sec. Is it possible to change response time
scale as we needed in to milli seconds? We would like to see response time
distribution respective to transactions per sec for whole scenario. Which is
going to show us if there any spikes in response times.
A:Today, the Analysis UI reports in seconds, even though the raw data is available in
milliseconds. We have taken both of these as enhancement requests for future
releases.

Q:I am running an endurance test on the client using QTP. The test is set to
run 500 times. Is there a way to set a counter on the number of times the
script actually ran when it quits before the 500?
A:DataTable.GetCurrentRow holds the current iteration. When QTP quits, it can write
this value to the report.
You can use environment variables or a regular variable to keep track of the number of
times to run the script. You can then write this value to the runtime data table. When
the script quits, go to the runtime data table and look at the value. If the script is
based on iterations, then you can use the built-in environment variable
"ActionIteration" or "TestIteration" which will give you the current iterations for either
the test or the specific action.

Q:What is the future for WinRunner?
A:Mercury WinRunner® is the standard functional testing solution for enterprise IT
applications. It captures, verifies, and replays user interactions automatically, so you
can identify defects and ensure that business processes, which could span across
multiple applications and databases, work as designed upon deployment and remain
reliable.
WinRunner continues to be a fully supported product. In Q1 of 2005, we will release
WinRunner 8.0, with several enhancements, environment updates, and bug fixes.

Q:What are the differences between QTP 8.0 and Quality Center 8.0 vs. QTP
8.2 and Quality Center 8.2?
A:We have created a product alert that describes what's new in Quality Center and
QTP 8.2. You can find the alert on the CSO website. In addition, Mercury will host a
customer webinar on December 13th on Quality Center 8.2. Please see the CSO
website for registration. We will also make the recording of the webinar available on
the CSO website for subsequent viewing.

Q:With the increasing popularity of Linux as a server and lately as a desktop
platform, has Mercury considered functional testing tools for this up and
coming OS?
A:Mercury has standardized on J2EE for our server technology, which allows us to
support several popular versions of Linux. With respect to automated functional testing
on Linux clients, we are watching this market very closely. While we have had a few
customers request this functionality, we do not yet see a lot of market demand. We
continue to develop our ideas and designs, so that we can move very quickly when the
market needs us to be there.

Q:Can you provide a comprehensive statement covering all products with
regard to Windows XP SP2?
A:Microsoft's Service Pack 2 for Windows XP (XP SP2) was released on 8/10/2004.
XP SP2 corrects several security issues related to DCOM, COM+ Applications, and
Firewall ports. In addition, XP SP2 adds security improvements to Windows XP and
Internet Explorer.

TestDirector and TestDirector for Quality Center and its respective integrations may be
affected by the changes.


We are currently performing a complete evaluation of XP SP2, and full compatibility
with TestDirector, TestDirector for Quality Center, and integrations should occur by the
end of 2004. Mercury recommends all customers wait for full compatibility.

Mercury is committed to making customers successful. If an upgrade to Windows XP
SP2 is necessary, a workaround is provided for TestDirector 8.0 SP2 in knowledge base
article 33501.

QuickTest 8.2 provides full support for Windows XP SP2.

Q:What are you doing for 'existing' customer to move to the new 'Centers'?
What is my upgrade path... or am I already there?
A:The majority of our Performance Center customers today are previous LoadRunner
users. They made the decision to upgrade to a globally accessible, 24x7 load testing
platform for many reasons, including globalization of the testing team, formation of a
CoE or standardization initiatives within their company. Mercury is committed to
providing both a financial and technical migration path to all of our customers that
wish to upgrade. I would advise working with your sales representative to customize a
migration plan specific to your company and needs.

Q:How are checkpoint baseline values and the purpose of the checkpoint
communicated back to the BA in BPT ?
A:The idea is to provide these as custom keywords. The QTP engineer should create
"verification" keywords (functions) and the BA will use them in QA while defining the
component steps. These functions can be defined either using the standard checkpoint
mechanism QTP provides, or any other mechanism the QTP experts builds.

A checkpoint contains a number of properties / values and we use these properties /
values to do the comparison at runtime. We then write the status of the checkpoint
back to the QTP Report. If the report is stored in QC then it's written to QC; if the
report is stored on the file system then it's written to the file system.

Q:Several QTP scripts may be called in a BPT test. Each one may have
different data in a data table. How can the BA in BPT override and control
data tables ?
A:The data table is not used when working in BPT. Providing data for these runs should
be done only through Quality Center in an interface easily accessible by a BA.

A business component is a mini QTP test which has its own data table. Business
Process Testing does not have control of data tables used by business components. It
controls what Business Components are, how input/output parameters can be passed
among the Business Components, and the order of the components. Currently there is
no way from QC side to control it.

Q:Can users who prefer descriptive programming in QTP have the ability to
SaveAs Descriptive? If this is chosen, the OR values could be saved in the
script instead of the logical values.
A:No, this functionality is not available.

Q:What is the direction for Quality Center? Is it moving from a project-centric
architecture to a system-level architecture?
A:In Quality Center (and all Mercury Centers), we are building the industry's only
solutions that scale from a single project to a 24x7, globally accessible Center of
Excellence. Quality Center, for example, gives you the ability to set up a single
Foundation (server) that can support hundreds of users, or a clustered environment


that can scale to thousands of users and provides failover capabilities.

Q:Will QTP/BPT work with descriptive programming or only through the
object repository?
A:QTP/BPT will work also with descriptive programming, but if you want to utilize the
Keyword View for objects (not only operations) you must use an Object Repository.

Q:In terms of the upgrade path from Topaz 4.5FP2 to 5.1, can I run both
systems together using a single database? This is so I can migrate my lines of
business in a phased manner.
A:We have a gradual upgrade with some limitations. We can upgrade the schema w/o
upgrading the data. At that point one can view the data on both systems on most
applications and cannot change it. More information can be found in the Topaz upgrade
document available with the CD or on the Support web site.

Q:When will version control be an integrated feature of Quality Center?
A:Version Control for Automated Test Scripts has been part of TD / QC since TD 7.6.
We also continue to support integrations with many of the most popular third-party
version control products.

Q:With Topaz's web transaction breakdown, there is a measurement for
server time to first buffer. If the response time goes up for this measurement,
is it true that is could be the due to any application server or web server
involved in the transaction? It's not necessarily the web server, correct. This
is currently a Siebel thin 6.2 transaction which goes through a web server,
Resonate server, ldap server, and Siebel application server, and database
server.
A:This is true. It could be anything from the web server and behind it (i.e.. All the
components mentioned). The measurement is based on the TCP traffic so if something
is holding it behind the server (i.e. a database or ldap etc...) it will affect the
measurement.

Q:What road map can you suggest I follow towards being best prepared to
utilize LoadRunner's J2EE Monitor effectively for a customer? In other words,
what must I learn / not learn / where should I focus most?
A:LoadRunner's J2EE Diagnostics solution has was built from the ground up for the
Performance Engineer. It assumes minimal java knowledge in it's design and
implementation. That said, as next steps I would suggest some reading to make sure
you have an understanding of the app server/container architecture, standard
development terminology/components.

Q:With the incorporation of the Real User monitor into the core product of the
BAC 5.0 version, will there be an easy upgrade path to maintain data and
history? If not, will there at least be a method to leverage existing Business
Critical URLS and migrate them into the new version?
A:There is no direct upgrade path from 4.0 to 5.1. The Business Critical URLs will need
to be selected again. The same would be with the Alerts and reports. Please contact
Customer Support for more information and best practices.

Q:What is Mercury developing for SOX Compliance?
A:Many of our customers are currently leveraging the power and flexibility of the IT
Governance automation engine to digitize processes for SOX compliance. Please refer
to the Mercury SOX datasheets at
http://www.mercury.com/us/solutions/initiatives/sox/ for further details. In 2005, we
expect to make additional investments in building next generation solutions for SOX


compliance.

Q:WinRunner. The data table has excel-like functionality but is not completely
excel-like. For example you can't copy/paste like in excel. When will it have
the same excel-like functionality?
A:Unfortunately, there are no plans to add this functionality.

Q:In using the Mercury Diagnostics 3.0 what additional information can I
retrieve during my testing and performance evaluation?
A:Diagnostics 3.0 offers 360-degree monitoring ??? from end-user, application, and
system perspectives. Allowing customers to detect problems in the application as well
as in all connected systems and environments. Within the application itself, you can
get detailed visibility at the component, method, SQL statement and even line of code
levels.

Q:For Diagnostics 3.0, what is the probability of diagnosing all the way down
in the People Soft Applications?
A:Diagnostic 3.0 supports most common ERP/CRM packaged applications from the end
user and system perspectives. Within the application level, full support for detailed
data capture of PeopleSoft application is not yet available. We work with PeopleSoft
closely to extract performance information from the standard PeopleSoft APIs to
supplement our own capabilities for monitoring and diagnostics of PeopleSoft
applications.

Q:Business Availability Center. How can you support real user management in
an application where agents are not allowed to be installed at the desktop
level?
A:It depends on the specifications of the application. If this is a Web application we
can use RUM. We have a few customers in the financial sector that use this solution.

Q:WinRunner uses TSL which is a derivative of C. QuickTestPro is VBScript.
How are you going to be able to port WinRunner scripts to QuickTestPro?
A:Mercury's approach has not been to port scripts, but rather has an integrated
platform on which all tests types can work together. This is available today in Quality
Center's Test Lab. Business Process Testing will provide another avenue for our testing
products to work together.

While it is possible to port scripts, it is also possible and generally far easier to call
your WinRunner script / function from QuickTest Professional and visa versa. This
integration is available today in the Mercury Functional Testing product, which includes
full QTP and WR licenses.

Q:When will Test Director be pushed to a database and not be in the file
system any longer?
A:We are investigating various options and approaches to unify and simplify the
Quality Center repository. This is something we intend to pursue, but do not have a
date at this time.

Q:Quality Center. Is there a global deployment infrastructure or model yet?
How do you support 600 users across multiple regions in the world like Asia
Europe and America? Can we deploy across multiple regions and have them
sync up to one database?
A:We have a sizing calculator and a "best practices" document for deploying Quality
Center on the CSO site. Additionally, QC supports clustering and failover, which will
make it possible to have multiple QC servers pointing to the same database.



Q:QuickTestProfessional with SAP. External Support with Quality Center.
Worried about future support.
A:SAP is one of our most strategic environments and we are committed to supporting
it. QuickTest Professional SAP add-in 8.2 supports the latest SAP environments,
including SAP GUI 6.40 and Enterprise Portal 6. It should be available early next year.

If the question is referring to QTSAP integration with TD/QC. We will continue to
support this integration with QC. QuickTest Professional with the SAP add-in will work
with QC as it does for all add-ins.

Q:From an ITG perspective, what out-of-the-box integrations with other
projects that enable ITG will you have?
A:We support an out of the box bi-directional integration with Microsoft Project. Other
integrations with project scheduling tools are possible, and will be driven by market
demand.

Q:How soon will TestDirector and ITG be integrated Seamlessly?
A:QC 8.5 Initial ITG / QC Integrations Mid next year

Q:What are Mercury s plans to extend the ITG footprint?
A:2005 will see many extended capabilities added to the IT Governance Center. First,
we will be focusing on leveraging the capabilities of ITG to digitize ITIL processes and
automate workflows related to SOX and Cobit. We will be focusing on integrations and
APIs within the suite - adding out-of-the-box integrations with Financial Management
applications and other systems within the BTO landscape. And finally, we will be
looking at building an ecosystem of partners around the ITG products.

Q:What are you going to do to make the integration points between all of the
optimization centers easier for the handoff within the business processes
people are going to be following?
A:We will be focusing on three main areas for integration between our optimization
centers. First, we will continue with our efforts to build Key Performance Indicators
(KPIs) for each Center in a common dashboard technology starting with Quality Center
and IT Governance Center. This common technology will adhere to standards such as
JSR 168 WSRP so any one dashboard can display and normalize metrics from other
centers. Moreover, these dashboards will be open in the future to normalize data from
outside the Mercury Centers. Common metrics in a shared view will allow better and
timelier decision making. Second, we will work towards productizing common
processes between each of the Centers (e.g., linking ITG to Quality Center via an
integration between Demand Management and the Requirements module in
TestDirector). These will link each of the centers together to support both strategic and
keep the lights on activities within IT. Lastly, we will focus on improving and building
more common assets and applications that can be shared between the centers (e.g.,
VUGen scripts shared and saved into the BAC repository or sharing and managing
scripts between Quality and Performance Center, etc.).

Q:We are migrating from a single application-environment to a multi-
application environment. How do you generate testing scripts that were in a
single-application environment, single server, to putting them into a large
dome type server?
A:Many companies have made the move from single application environments to a
shared deployment infrastructure. To mitigate the risk associated with this, you will
need to add an additional type of test to your performance testing process. In addition
to your single application load tests, you should now do system tests. These are


LoadRunner scenarios emulating traffic from multiple applications against the shared
infrastructure. This will not require rescripting, but rather, additional scenarios that
you will need to construct.

Q:What is in the planning for version control within TestDirector to be able to
follow change and configuration management processes?
A:Change and configuration management processes will be supported by an
integration between IT Governance and Quality Center. Both Centers provide
integrations to third party version control tools.

Q:TestDirector. As the database grows and grows there is no way of taking a
portion of that database out and saving it for the continuation of the project.
Is there a way to do this?
A:We do not have archiving capabilities in TD or QC, so the best way to accomplish
that is to make a copy of the project, then start removing the old data. A quick way to
remove old Runs (which is the part that can grow fast) is using "Purge Runs" feature in
TEST LAB module.

Q:How are you going to integrate all of the processes around ITIL and
software development?
A:ITG's workflow engine is ideal to define and automate the execution of IT processes.
Many of our customers have already configured the product to implement integrated
ITIL processes. We plan to release out of the box ITIL processes in 2005.

Q:Application Mapping Group. Are they working on a portal that would allow
you to build views that would be customizable by the line of business unit
people so they could visually see how their world works not in an IT
perspective but in a business perspective?
A:The Application Mapping is a core component of the Business Availability Center
which allows for custom vies to be created based on your rose. Furthermore, with the
BTO Dashboard, metrics and views will be able to be shared from Business Availability
Center with other centers (e.g. ITG).

Q:Is there a VPN Solution for the Business Availability Center?
A:BPMs can work via VPN in order to access applications. If there are other reasons to
use VPN, please contact customer support for further clarification.

Q:Do you have a solution to incorporate telecom into the BAC product?
A:There are currently no immediate plans to develop vertical specific solutions (Telco,
Healthcare, Financial Services, etc) for the Business Availability Center. However, we
are in the process of investigating solutions for wireless and we currently do have
various capabilities to monitor Call Center applications and users as well as other
various web based applications for Telco's.

Q:We use TestCenter in our development testing. We have a group that does
our full S&P (SAP?) testing that uses LoadRunner. One of the things I like
about LoadRunner is you watch the transaction flow through as you are
running the test. I would like to see this capability added to TestCenter.
A:We will be adding Diagnostics or Transaction Breakdown capability to Performance
Center early this year. Mercury is committed to functional parity between LoadRunner
and TestCenter/Performance Center.

Q:How can I print out a report of a test set including the steps of the test
before you have actually run the tests?
A:The built-in reports in TD does not have this feature, however, with the Advanced


Reports add-in it is possible to generate such reports. Please also check the CSO
Knowledge Base; there are many SQL statements in Knowledge Base articles that
provide data which TD reports does not give.

Q:We want the programmer to have all the things he has to do in ITG. If a bug
is detected in TestDirector we would like him to see it as a task on his
dashboard.
A:The ITG - Quality Center integration is one of the primary focus areas for BTO
integrations in early 2005. The ITG and QC R&D teams are currently working to gather
requirements for customers, and one of the main areas of focus is to reflect
TestDirector defects on the Dashboard of ITG. We expect initial releases of this
integration in the first half of 2005. QC 8.5 Initial ITG / QC Integrations Mid next year

Q:Test Director. The requirements module does not seem to allow access to
multiple projects in a streamlined way. We would like to see streamlined
accessibility to multiple projects within one requirements module within one
project.
A:We plan to continue enhancing the functionality of the Requirements module within
Quality Center. At this time, we do not have plans to create Shared Requirements for
multiple projects, but as a proxy you can manage many testing initiatives in a single
project, thus enabling you shared requirements between them.

Q:Are there any plans to make the GUI maps in WinRunner easier to work
with?
A:WinRunner 8.0 will introduce a new wizard for the GUI Map Configuration functions
that will make it easier to use. We are constantly looking for additional improvements
for this and other areas of WinRunner in future versions. If you have other specific
requirements or feedback, please submit an enhancement request.

Q:More guidance on testing matrix or reports that can come out of
TestDirector to really judge the productivity of your test script.
A:The best measures of the effectiveness of a test show how it performs over time and
against multiple releases of an application. A well-constructed test will find a variety of
defects and identify regressions, yet be resilient to minor application changes. The
Delivery Dashboard for Quality Center has specific capability to track KPI trends over
time and from one project to the next. Alternatively, you can export a standard report
to Excel and track it manually.

Q:LoadRunner. I would like the analysis tool to have multiple summary pages
so that we can have different filter levels.
A:We have taken this as an enhancement request for future releases.

Q:Are there any plans developing the tuning module for a mainframe?
A:Mainframe monitoring and tuning solutions are something that Mercury is always
looking into. I have no immediate product plans that I can share, however.

Q:When can you alleviate frustration with QuickTest Pro and LoadRunner so
that the scripts and SAP GUIs will run as recorded? They record fine but when
I go to replay they report error messages.
A:Not all recorded objects in QTP for SAP can be replayed in LR. There are some
limitations in the ActiveX's that can be run as a LoadRunner virtual user. This is a
limitation of the SAP API that we are working with them to address. Til then, please
find the list of all unsupported Active X's on the CSO website



WinRunner vs. QuickTest Pro
Quick Comparison

Shawn LoPorto

Senior Test Automation Architect / SME
Automated Solutions, Inc.
QATraining.net
Mercury SPP Gold Level Partner



Table of Contents

Overview..............................................................................................................................3
WinRunner Compared to QuickTest Pro.............................................................................4
What We Recommend.........................................................................................................6
WinRunner...........................................................................................................................8
Summary:.........................................................................................................................8
Pros:.................................................................................................................................9
Cons:................................................................................................................................9
QuickTest Pro....................................................................................................................10
Summary:.......................................................................................................................10
Pros:...............................................................................................................................11
Cons:..............................................................................................................................11



Overview
Today Mercury has two functional testing tools – WinRunner (WR) and QuickTest
Professional (QTP). WinRunner has been around since about 1995 while QuickTest Pro
has been available since about 2002. We have lots of companies asking us “What’s the
difference between WinRunner and QuickTest Pro?” and “If they are both functional
testing tools from the same company, then which one of the tools should we use?” This
document was developed as a short simple reference in helping to understand the basics
about the tools in order to answer these two questions.

Mercury’s position on the two tools is this:
•1 The strategic direction for Mercury and its customers for Functional Testing
is product integration. The new releases of QTP and WR improve already
existing integration where customers can leverage complete WinRunner assets
(scripts/functions) from QuickTest Pro without any modification to these assets.
•2 QuickTest Pro 8 has recently been released and WinRunner version 8.0 is
planned for November 2004. There are no plans to phase out WinRunner.
•3 QuickTest Pro remains Mercury’s prime product for best customer
satisfaction and experience. For customers who need both products, Mercury
continues to offer Mercury Functional Testing as a combined package of both
product offerings. The Business Process Testing system will be extended to
incorporate components designed in WinRunner for the WinRunner 8.0 release in
November.



WinRunner Compared to QuickTest Pro

Environment Coverage Comparison:

•1 Common environments shared by both WinRunner and QuickTest Pro:
Web-Related Environments IE, Netscape, AOL
JDK, Java Foundation Classes, AWT
Symantec Visual Café
ActiveX Controls
ERP/CRM Oracle: Jinitiator, 11i, NCA
Custom Client Server Windows
C++/C
Visual Basic
Operating Systems Windows 98, 2000, NT, ME, XP
Legacy 3270, 5250 Emulators
VT100

•2 WinRunner Only Environments:
Custom Client/Server PowerBuilder
Forte
Delphi
Centura
Stingray
SmallTalk
ERP/CRM Baan
PeopleSoft Windows
Siebel 5, 6 GUI Clients
Oracle GUI Forms

•3 QuickTest Pro Only Environments:
ERP/CRM SAP
Siebel 7.x
PeopleSoft 8.x
.Net WinForms
WebForms
.Net controls
Web Services XML, HTTP
WSDL, SOAP
J2EE, .Net
Multimedia RealAudio/Video
Flash



Feature Comparison:
•4 Common features found in both WinRunner and QuickTest Pro:
Record/Replay ODBC & Excel Connectivity
Code Editor & Debugger Recovery Manager
Shared Object Repository Rapid Object Import
Numerous Checkpoints Analog
Script & Function Libraries

•5 WinRunner Only Environments:
Function Generator Database Integration
Run Wizard TSL
MDI

•6 QuickTest Pro Only Environments:
ActiveScreen TestGuard
Tree View ScriptFusion
Data Table VBScript
Function Generator* Run Wizard*
(coming in v7.0) (coming in v7.0)



What We Recommend
QuickTest Pro is our functional testing tool of choice!

Most customers are in either of two situations:
•7 Existing WinRunner customers asking “Should we switch to QuickTest Pro?”
•8 New customers asking “Which should we get, WinRunner or QuickTest
Pro?”

We have been implementing Mercury’s products since 1992 and have senior level
expertise in WinRunner. We have been implementing WinRunner since the very first
version of it. So like many existing WinRunner customers we have a huge knowledge
investment in WinRunner ourselves. However we have worked on the Mercury
development team on the QuickTest Pro 6.0 and 6.5 releases, and have solid real-world
experience in implementing QuickTest Pro since the 6.0 release. We have found it to be
a great tool to use and recommend it to all customers! Overall, we recommend using
QuickTest Pro unless for some reason you have to use WinRunner due to an unsupported
environment not existing in QuickTest Pro.

Overall, QuickTest Pro is easier to use and implement for both technical and non-
technical testers in comparison to WinRunner. QTP offers many features that are found
in WinRunner, but are easier to use. QTP also offers many features not found in
WinRunner that make test script creation, enhancement and maintenance easier.

Let’s quickly discuss some key issues:
•1 The WinRunner interface forces the user to look directly at TSL code. TSL is
the WinRunner programming language developed by Mercury. It is based on the
“C” programming language and therefore looks very similar. For testers who do
not have a technical background, they are not always comfortable with having to
always look at code. However QuickTest Pro offers a “Tree View” which is an
icon-based view of the script. This is very easy to get used to and non-technical
people adapt to it quicker and feel more comfortable working with it. For the
technical user, they can always switch over to the “Expert View” in QuickTest
and look directly at code, and program away using VBScript.

•2 WinRunner uses TSL which is a proprietary language of Mercury. These
types of languages can be very restrictive and you are limited on available
resources. QuickTest Pro use the Microsoft programming language VBScript
which is very powerful, has lots of capabilities and there are lots of resources
available.

We feel that there are many more “point and click” features in QuickTest Pro


than WinRunner. This makes its use easier.
All the same features found in WinRunner are found in QuickTest Pro plus
more.

Data Table integration is much easier and simpler with QuickTest Pro.

Data Driven Testing is easier with more options in QuickTest Pro.
Script enhancements are typically easier with QuickTest Pro because it has
the Active Screen where the windows and objects in your application are captured
for later use. Using a “point and click” capability you can easily interface with
objects, their definitions and create checkpoints after having recorded a script –
without having to navigate back to that location in your application like you have
to with WinRunner. This greatly speeds up script development.
QuickTest Pro currently has built in integration with WinRunner in order to
be able to call existing scripts, which is great for customers who already have a
large test script investment with WinRunner. Likewise WinRunner 8.0 is to have
the ability to also call QuickTest Pro scripts. This eases the transition from
WinRunner to QuickTest Pro for existing customers.
Parameterization is much easier in QuickTest Pro and basically anything in
QuickTest Pro can be parameterized (statements, checkpoints and the Object
Repository).
Capturing various output values is easier and simpler with QuickTest Pro.
Using this capability with parameterization enables you to easily develop scripts
that can do more in regards to testing.

We have been implementing QuickTest Pro in real-world environments and
have found it much easier to use, advance features are easier to implement and the
script development is quicker. We really enjoy using QuickTest Pro and highly
recommend it as the functional testing tool to use.

QuickTest Pro is our functional testing tool of choice!



WinRunner
Summary:

This product is a mature tool that has been around since approximately 1995. It interfaces with most
of the leading development toolkits using the WindowsAPI and toolkit DLLs to interface with the
“Application Under Test”.

WinRunner offers a recording feature that will watch the individual tester and generate a test script to
simulate the same actions just performed. The script is displayed as a program which can be enhanced
with checkpoints, logic and special coding/programming.

WinRunner also has integration with Excel spreadsheets for data driven testing and the ability to write
data out in Excel format or in simple text files.

Here is the description from the Mercury “Features and Benefits” section of the WinRunner web page:
Significantly increase power and flexibility of tests without any programming: The Function Generator presents a quick
and error-free way to design tests and enhance scripts without any programming knowledge. Testers can simply point at a GUI
object, and WinRunner will examine it, determine its class and suggest an appropriate function to be used.
Use multiple verification types to ensure sound functionality: WinRunner provides checkpoints for text, GUI, bitmaps,
URL links and the database, allowing testers to compare expected and actual outcomes and identify potential problems with
numerous GUI objects and their functionality.
Verify data integrity in your back-end database: Built-in Database Verification confirms values stored in the database and
ensures transaction accuracy and the data integrity of records that have been updated, deleted and added.
View, store and verify at a glance every attribute of tested objects: WinRunner's GUI Spy automatically identifies, records
and displays the properties of standard GUI objects, ActiveX controls, as well as Java objects and methods. This ensures that
every object in the user interface is recognized by the script and can be tested.
Maintain tests and build reusable scripts: The GUI map provides a centralized object repository, allowing testers to verify
and modify any tested object. These changes are then automatically propagated to all appropriate scripts, eliminating the need
to build new scripts each time the application is modified.
Test multiple environments with a single application: WinRunner supports more than 30 environments, including Web,
Java, Visual Basic, etc. In addition, it provides targeted solutions for such leading ERP/CRM applications as SAP, Siebel,
PeopleSoft and a number of others.
Simplify creation of test scripts: WinRunner's DataDriver Wizard greatly simplifies the process of preparing test data and
scripts. This allows for optimal use of QA resources and results in more thorough testing.
Automatically identify discrepancies in data: WinRunner examines and compares expected and actual results using multiple
verifications for text, GUI, bitmaps, URLs, and databases. This ensures stable functionality and execution of business
transactions when the application is released into production.
Validate applications across browsers: WinRunner enables the same test to be used to validate applications in Internet
Explorer, Netscape, and AOL. This saves testing time and reduces the number of scripts that must be developed and
maintained.
Automatically recover tested applications from a crash: Unexpected events, errors, and application crashes during a test run
can disrupt the testing process and distort results. WinRunner's Recovery Manager enables unattended recovery and provides a
wizard that guides the process of defining a recovery scenario.
Leverage investments in other testing products: WinRunner fully integrates with our other testing solutions, including
LoadRunner for load testing and TestDirector for global test management. Moreover, organizations can reuse WinRunner test
scripts with QuickTest Professional.

- WinRunner “Features and Benefits” webpage from Mercury:
http://www.mercury.com/us/products/quality-center/functional-testing/winrunner/features.html


Pros:
• Mature product that has been around since about 1995.
• Simple interface.
• Many features.
• Many consultants and user group/forums for support.
• Decent built in help.
• Fewer features to have to learn and understand compared to QuickTest Pro.
• Interfaces with the Windows API.
• Integrates with TestDirector.

Cons:
• Has basically been superceded by QuickTest Pro.
• Looking at “program code” for the test case.
• Coding is done in a proprietary language (TSL).
• Very few resources available on TSL programming (it is based on the C programming
language, but is not C).
• Need to be able to program to a certain extent in order to gain flexibility and parameterization.
• Need training to implement properly.
• The GUI Map can be difficult to understand and implement.



QuickTest Pro

Summary:
QuickTest Professional provides an interactive, visual environment for test development.

Here is the description from the Mercury Interactive “How it Works” section of the QuickTest Pro
web page:
Mercury QuickTest Professional™ allows even novice testers to be productive in minutes. You can create a test script by
simply pressing a Record button and using an application to perform a typical business process. Each step in the business
process is automated documented with a plain-English sentence and screen shot. Users can easily modify, remove, or rearrange
test steps in the Keyword View.

QuickTest Professional can automatically introduce checkpoints to verify application properties and functionality, for example
to validate output or check link validity. For each step in the Keyword View, there is an ActiveScreen showing exactly how the
application under test looked at that step. You can also add several types of checkpoints for any object to verify that
components behave as expected, simply by clicking on that object in the ActiveScreen.

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.

Advanced testers can view and edit their test scripts in the Expert View, which reveals the underlying industry-standard
VBScript that QuickTest Professional automatically generates. Any changes made in the Expert View are automatically
synchronized with the Keyword View.

Once a tester has run a script, a TestFusion report displays all aspects of the test run: a high-level results overview, an
expandable Tree View of the test script 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 TestFusion reports with Mercury Quality Management, you can share reports across an entire QA and development
team.

QuickTest Professional also facilitates the update process. As an application under test changes, such as when a “Login” button
is renamed “Sign In,” you can make one update to the Shared Object Repository, and the update will propagate to all scripts
that reference this object. You can publish test scripts to Mercury Quality Management, enabling other QA team members to
reuse your test scripts, eliminating duplicative work.

QuickTest Professional supports functional testing of all popular environments, including Windows, Web, .Net, Visual Basic,
ActiveX, Java, SAP, Siebel, Oracle, PeopleSoft, terminal emulators, and Web services.

- QuickTest Pro “How it Works” webpage from Mercury:
http://www.mercury.com/us/products/quality-center/functional-testing/quicktest-professional/works.html

We like QuickTest Pro and now prefer implementing it over WinRunner. When you get into advance
testing scenarios, QuickTest Pro has more options and they are easier to implement compared to
WinRunner in our opinion.

Do to the similarities in concept and features, an experienced WinRunner user can easily convert to
QuickTest Pro and quickly become an efficient Test Automation Engineer!

We recommend that existing customers begin all new development with QuickTest Pro and use the
built-in feature of calling WinRunner scripts from QuickTest Pro for all existing WinRunner scripts


that they already have. As older scripts require updates and time permits, we recommend replacing
them with QuickTest Pro scripts. Eventually you will be able to convert your test script library with
all QuickTest Pro scripts.

Pros:
• Will be getting the initial focus on development of all new features and supported technologies.
• Ease of use.
• Simple interface.
• Presents the test case as a business workflow to the tester (simpler to understand).
• Numerous features.
• Uses a real programming language (Microsoft’s VBScript) with numerous resources available.
• QuickTest Pro is significantly easier for a non-technical person to adapt to and create working
test cases, compared to WinRunner.
• Data table integration better and easier to use than WinRunner.
• Test Run Iterations/Data driving a test is easier and better implement with QuickTest.
• Parameterization easier than WinRunner.
• Can enhance existing QuickTest scripts without the “Application Under Test” being available;
by using the ActiveScreen.
• Can create and implement the Microsoft Object Model (Outlook objects, ADO objects,
FileSystem objects, supports DOM, WSH, etc.).
• Better object identification mechanism.
• Numerous existing functions available for implementation – both from within QuickTest Pro
and VBScript.
• QTP supports .NET development environment (currently WinRunner 7.5 does not).
• XML support (currently WinRunner 7.5 does not).
• The Test Report is more robust in QuickTest compared to WinRunner.
• Integrates with TestDirector and WinRunner (can kick off WinRunner scripts from QuickTest).

Cons:
• Currently there are fewer resources (consultants and expertise) available due to QTP being a
newer product on the market and because there is a greater Demand than Supply, thus fewer
employee/consulting resources.
• Must know VBScript in order to program at all.
• Must be able to program in VBScript in order to implement the real advance testing tasks and
to handle very dynamic situations.
• Need training to implement properly.
• The Object Repository (OR) and “testing environment” (paths, folders, function libraries, OR)
can be difficult to understand and implement initially.

Introduction to Mercury Test Director 8.0
TESTDIRECTOR v 8.0
Learn the way Fortune 100 Companies work with Test Director. Real Time Projects, Certified Instructors, Online
Help.
Will show different examples which is followed by major Financial/Insurance/Pharmaceutical/Banking Companies.
100 Questions Prepared by Venkat for Test Director (Real time FAQ's asked in interviews)


Adding Test Requirement. Characteristics of a useful requirement Example of a Test Requirement Building a
requirements structure Entering requirements

Manually Importing requirementsRequirements graphs and reports Adding Test Cases. Test case coverage.
Characteristics of a useful test case
Test Case Example Building a test case structure Creating manual test cases Parameters Importing test cases
Linking test cases to requirements

Test case graphs and reports Test Sets and Test Execution Creating test sets Defining test dependencies and
running tests conditionally Setting test set properties

TESTDIRECTOR v 8.0
Adding Test RequirementCharacteristics of a useful requirementExample of a Test RequirementBuilding a
requirements structureEntering requirements

manuallyImporting requirementsRequirements graphs and reportsAdding Test CasesTest case
coverageCharacteristics of a useful test case
Test Case ExampleBuilding a test case structureCreating manual test cases ParametersImporting test cases
Linking test cases to requirements

Test case graphs and reportsTest Sets and Test ExecutionCreating test sets Defining test dependencies and
running tests conditionallySetting test set properties

Manual test execution
Automated test execution
Adding test hostsRunning a test setSetting run timesAnalyzing test results

Defect Tracing The Defect Life Cycle Reporting defects
Searching for similar defects

Using grid filters Defect graphs and reports Reports Creating reports with the Document Generator
LOADRUNNER v 8.0
Fundamentals of Laod Runner and Loadtesting

This class covers Controller and Analysis components of LoadRunner. This course is your first step towards success
as a LoadRunner expert, designed to give you a firm foundation in basic load testing tasks.

In this class, you will learn how to plan, create, and run a simple load test effectively and efficiently. Students will
gain understanding of how the LoadRunner components work and interact with one another.

Students will also learn how to interpret LoadRunner analysis graphs and achieve the set load testing goals. The
lesson topics are reinforced with structured hands-on labs.

VuGen Scripts for Web - This class covers the VuGen component of LoadRunner. This course gives students an in-
depth introduction to all aspects of script creation for load testing in a Web environment. Students learn to record,
organize the script using actions and add checkpoints to verify functionality under load.

They also learn to troubleshoot the script they build by parameter zing, correlation and adding custom code.
Hands on Lab: LoadRunner - This hands-on lab is designed to provide comprehensive understanding of all the
concepts learned in the LoadRunner suite course.

This hands-on lab involves students in building an effective load testing script and then running a load test against
the Mercury Tours application to achieve the given performance goals.

This activity will validate your newly acquired knowledge on LoadRunner and on techniques for load testing Web
systems.


You will use the LoadRunner Analysis component to interpret load test results. The information gathered during
planning is used to create and enhance scripts specific to Web applications using the Virtual User Generator
(VuGen) component of LoadRunner.

All topics are supported by hands-on exercises designed to provide you with the knowledge to load test your
applications in the Web environment. The last day involves you to work on a comprehensive project designed to
test your understanding of all the concepts learned in the LoadRunner Web suite course.

This hands-on lab involves students in building an effective load testing script and then running a load test against
the Mercury Tours application to achieve the given performance goals. This activity will validate your newly
acquired knowledge on LoadRunner and on techniques for load testing Web systems.


Qtp interview questions_1

More Related Content

What's hot (20)

Viewers also liked (14)

Similar to Qtp interview questions_1 (20)

More from Ramu Palanki (20)

Qtp interview questions_1