qtp interview questions 1

8/8/2019 Qtp Interview Questions 1

1/22

For more QTP Scripts, visit www.ramupalanki.com

Q:I have a user interface in the application which has windows with the samelabels. So when I make a recovery scenario, how do I distinguish the one withthe labels and the one without as I do not want the recovery scenarios to becalled 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 thedifferentiator 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 entriesfrom the home-grown application to QualityCenter? A:We recommend you use the Word / Excel add-in and import the data into QualityCenter.

Q:We're using QTP v8.0 and capturing GUI with formatted numeric fields suchas currency, etc. with commas and decimal. QTP does not capture the input

(so that I can parameterize this later), but captures the formatted field afterentry. 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 toconvert from strings to numbers. For example:text = WinEdit.GetROProperty("text") ' returns string "1,234.56"num = CDbl(text) ' returns number 1234.56num1 = 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 datatable 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 isQuality Center going to handle application security since these differentresources may not exist on a common intranet? A:Since Quality Center utilizes HTTP communication through port 80, it works for bothintranet and the internet environments. You are correct that outsourcing adds newsecurity requirements. In addition, Mercury offers Quality Center as a managedservice, which has further security requirements. For Quality Center 8.2, we haveadded support for Secure LDAP. And we will continue to enhance the securitycapabilities of Quality Center in upcoming releases. We will implement our electronicsignature solution for Quality Center, add a more flexible security group structure, andimprove integrations with existing security and identity management infrastructure.

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

www.ramupalanki.com Page 1


2/22

For more QTP Scripts, visit www.ramupalanki.comA:We suggest you try restoring the default settings at the end of the test run toalleviate the problem. Note that in general, we recommend that using the commandline 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 forfurther assistance.

Q:Is Mercury planning to improve its reporting capability in TD? A:We believe that a tremendous amount of valuable information is generated duringthe quality process, and the ability to make use of that information for better decisionmaking and project management is one of the key differentiators of TestDirector forQuality Center. To that end, we do plan to continue to improve the reporting capabilityof TestDirector as part of Quality Center. With Quality Center 8.2, we have enhancedthe Dashboard and updated the Advanced Reports add-in. In upcoming releases, wewill 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 errormessage when it first displays but we can move past that and login. Then allof 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 awareof many customers who are successfully using TestDirector in a Citrix environment. Itis possible that one of these customers can give you some insight into the issues youare experiencing and provide some suggestions. The best place to interact with othercustomers is through the forums on the CSO website. We are investigating thepossibility of adding support for Citrix in the near future. Please check for news andalerts 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 thesynchronization doesn't work [with Oracle 11.5.9] and I already have 2patches (one custom, and another on the way) to try to make LR 7.8 FP1work with 11.5.9. A:WinRunner 7.6 indeed had some synchronization issues with WR 7.6 Oracle Add-Inand 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 extractsrequirements, writes and tests programs? A:This is indeed a grand, long-term vision. Mercury is committed to improving andautomating the overall quality process. We are constantly looking at ways to integratewith other solutions, like our own IT Governance center, and to automate additionalaspects of quality assurance. A great example is the auto-documentation feature of thenew Business Process Testing (BPT) module within Quality Center. Auto-documentationcombines the previously separate steps of documenting a test and actually executingthe test, significantly reducing the overall effort.

Q:Upgrade of Test Director from 7.x to 8.0; Discuss best approaches andcomplications and pitfalls and benefits from the upgrade also things to watchout for... A:We have a "Best Practices" document in the KB about upgrading to TD 8.0. CSOwebsite - 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 arerunning tests on j2ee application where expected response times are in milliseconds (ex 150 millisecond per method). Because rounding to sec we are



3/22

For more QTP Scripts, visit www.ramupalanki.comseeing all transactions below 1 sec. Is it possible to change response timescale as we needed in to milli seconds? We would like to see response timedistribution respective to transactions per sec for whole scenario. Which isgoing 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 inmilliseconds. We have taken both of these as enhancement requests for futurereleases.

Q:I am running an endurance test on the client using QTP. The test is set torun 500 times. Is there a way to set a counter on the number of times thescript actually ran when it quits before the 500? A:DataTable.GetCurrentRow holds the current iteration. When QTP quits, it can writethis 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. Whenthe script quits, go to the runtime data table and look at the value. If the script isbased on iterations, then you can use the built-in environment variable"ActionIteration" or "TestIteration" which will give you the current iterations for eitherthe test or the specific action.

Q:What is the future for WinRunner? A:Mercury WinRunner is the standard functional testing solution for enterprise ITapplications. It captures, verifies, and replays user interactions automatically, so youcan identify defects and ensure that business processes, which could span acrossmultiple applications and databases, work as designed upon deployment and remainreliable.WinRunner continues to be a fully supported product. In Q1 of 2005, we will releaseWinRunner 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. QTP8.2 and Quality Center 8.2? A:We have created a product alert that describes what's new in Quality Center andQTP 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 CSOwebsite for registration. We will also make the recording of the webinar available onthe CSO website for subsequent viewing.

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

Q:Can you provide a comprehensive statement covering all products withregard 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, andFirewall ports. In addition, XP SP2 adds security improvements to Windows XP andInternet Explorer.

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



4/22


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

Mercury is committed to making customers successful. If an upgrade to Windows XPSP2 is necessary, a workaround is provided for TestDirector 8.0 SP2 in knowledge basearticle 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 LoadRunnerusers. They made the decision to upgrade to a globally accessible, 24x7 load testingplatform for many reasons, including globalization of the testing team, formation of aCoE or standardization initiatives within their company. Mercury is committed toproviding both a financial and technical migration path to all of our customers thatwish to upgrade. I would advise working with your sales representative to customize amigration plan specific to your company and needs.

Q:How are checkpoint baseline values and the purpose of the checkpointcommunicated 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 thecomponent steps. These functions can be defined either using the standard checkpointmechanism 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 checkpointback to the QTP Report. If the report is stored in QC then it's written to QC; if thereport 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 havedifferent data in a data table. How can the BA in BPT override and controldata tables ? A:The data table is not used when working in BPT. Providing data for these runs shouldbe 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. BusinessProcess Testing does not have control of data tables used by business components. Itcontrols what Business Components are, how input/output parameters can be passedamong the Business Components, and the order of the components. Currently there isno way from QC side to control it.

Q:Can users who prefer descriptive programming in QTP have the ability toSaveAs 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-centricarchitecture to a system-level architecture? A:In Quality Center (and all Mercury Centers), we are building the industry's onlysolutions 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 singleFoundation (server) that can support hundreds of users, or a clustered environment



5/22

For more QTP Scripts, visit www.ramupalanki.comthat can scale to thousands of users and provides failover capabilities.

Q:Will QTP/BPT work with descriptive programming or only through theobject repository? A:QTP/BPT will work also with descriptive programming, but if you want to utilize theKeyword 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 bothsystems 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/oupgrading the data. At that point one can view the data on both systems on mostapplications and cannot change it. More information can be found in the Topaz upgradedocument 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-partyversion control products.

Q:With Topaz's web transaction breakdown, there is a measurement forserver 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 serverinvolved in the transaction? It's not necessarily the web server, correct. Thisis currently a Siebel thin 6.2 transaction which goes through a web server,Resonate server, ldap server, and Siebel application server, and databaseserver. A:This is true. It could be anything from the web server and behind it (i.e.. All thecomponents mentioned). The measurement is based on the TCP traffic so if somethingis holding it behind the server (i.e. a database or ldap etc...) it will affect themeasurement.

Q:What road map can you suggest I follow towards being best prepared toutilize 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 thePerformance Engineer. It assumes minimal java knowledge in it's design andimplementation. That said, as next steps I would suggest some reading to make sureyou have an understanding of the app server/container architecture, standarddevelopment terminology/components.

Q:With the incorporation of the Real User monitor into the core product of theBAC 5.0 version, will there be an easy upgrade path to maintain data andhistory? If not, will there at least be a method to leverage existing BusinessCritical 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 contactCustomer 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 ITGovernance automation engine to digitize processes for SOX compliance. Please referto the Mercury SOX datasheets athttp://www.mercury.com/us/solutions/initiatives/sox/ for further details. In 2005, weexpect to make additional investments in building next generation solutions for SOX



6/22

For more QTP Scripts, visit www.ramupalanki.comcompliance.

Q:WinRunner. The data table has excel-like functionality but is not completelyexcel-like. For example you can't copy/paste like in excel. When will it havethe 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 Iretrieve during my testing and performance evaluation? A:Diagnostics 3.0 offers 360-degree monitoring ??? from end-user, application, andsystem perspectives. Allowing customers to detect problems in the application as wellas in all connected systems and environments. Within the application itself, you canget detailed visibility at the component, method, SQL statement and even line of codelevels.

Q:For Diagnostics 3.0, what is the probability of diagnosing all the way downin the People Soft Applications? A:Diagnostic 3.0 supports most common ERP/CRM packaged applications from the enduser and system perspectives. Within the application level, full support for detailed

data capture of PeopleSoft application is not yet available. We work with PeopleSoftclosely to extract performance information from the standard PeopleSoft APIs tosupplement our own capabilities for monitoring and diagnostics of PeopleSoftapplications.

Q:Business Availability Center. How can you support real user management inan application where agents are not allowed to be installed at the desktoplevel? A:It depends on the specifications of the application. If this is a Web application wecan 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 integratedplatform on which all tests types can work together. This is available today in QualityCenter's Test Lab. Business Process Testing will provide another avenue for our testingproducts to work together.

While it is possible to port scripts, it is also possible and generally far easier to callyour WinRunner script / function from QuickTest Professional and visa versa. Thisintegration is available today in the Mercury Functional Testing product, which includesfull QTP and WR licenses.

Q:When will Test Director be pushed to a database and not be in the filesystem any longer? A:We are investigating various options and approaches to unify and simplify theQuality 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 AsiaEurope and America? Can we deploy across multiple regions and have themsync up to one database? A:We have a sizing calculator and a "best practices" document for deploying QualityCenter on the CSO site. Additionally, QC supports clustering and failover, which willmake it possible to have multiple QC servers pointing to the same database.



7/22

For more QTP Scripts, visit www.ramupalanki.com 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 supportingit. 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 tosupport this integration with QC. QuickTest Professional with the SAP add-in will workwith QC as it does for all add-ins.

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

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 andautomate workflows related to SOX and Cobit. We will be focusing on integrations andAPIs within the suite - adding out-of-the-box integrations with Financial Managementapplications and other systems within the BTO landscape. And finally, we will belooking 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 theoptimization centers easier for the handoff within the business processespeople are going to be following? A:We will be focusing on three main areas for integration between our optimizationcenters. First, we will continue with our efforts to build Key Performance Indicators(KPIs) for each Center in a common dashboard technology starting with Quality Centerand IT Governance Center. This common technology will adhere to standards such asJSR 168 WSRP so any one dashboard can display and normalize metrics from othercenters. Moreover, these dashboards will be open in the future to normalize data fromoutside the Mercury Centers. Common metrics in a shared view will allow better andtimelier decision making. Second, we will work towards productizing commonprocesses between each of the Centers (e.g., linking ITG to Quality Center via anintegration between Demand Management and the Requirements module inTestDirector). These will link each of the centers together to support both strategic andkeep the lights on activities within IT. Lastly, we will focus on improving and buildingmore 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 managingscripts 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 asingle-application environment, single server, to putting them into a largedome type server? A:Many companies have made the move from single application environments to ashared deployment infrastructure. To mitigate the risk associated with this, you willneed to add an additional type of test to your performance testing process. In additionto your single application load tests, you should now do system tests. These are



8/22

For more QTP Scripts, visit www.ramupalanki.comLoadRunner scenarios emulating traffic from multiple applications against the sharedinfrastructure. This will not require rescripting, but rather, additional scenarios thatyou will need to construct.

Q:What is in the planning for version control within TestDirector to be able tofollow change and configuration management processes?

A:Change and configuration management processes will be supported by anintegration between IT Governance and Quality Center. Both Centers provideintegrations to third party version control tools.

Q:TestDirector. As the database grows and grows there is no way of taking aportion 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 accomplishthat is to make a copy of the project, then start removing the old data. A quick way toremove old Runs (which is the part that can grow fast) is using "Purge Runs" feature inTEST LAB module.

Q:How are you going to integrate all of the processes around ITIL andsoftware 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 integratedITIL 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 allowyou to build views that would be customizable by the line of business unitpeople so they could visually see how their world works not in an ITperspective but in a business perspective? A:The Application Mapping is a core component of the Business Availability Centerwhich allows for custom vies to be created based on your rose. Furthermore, with theBTO Dashboard, metrics and views will be able to be shared from Business AvailabilityCenter 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 touse 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, weare in the process of investigating solutions for wireless and we currently do havevarious capabilities to monitor Call Center applications and users as well as othervarious web based applications for Telco's.

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

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



9/22

For more QTP Scripts, visit www.ramupalanki.comReports add-in it is possible to generate such reports. Please also check the CSOKnowledge Base; there are many SQL statements in Knowledge Base articles thatprovide 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 bugis 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 BTOintegrations in early 2005. The ITG and QC R&D teams are currently working to gatherrequirements for customers, and one of the main areas of focus is to reflectTestDirector defects on the Dashboard of ITG. We expect initial releases of thisintegration 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 tomultiple projects in a streamlined way. We would like to see streamlinedaccessibility to multiple projects within one requirements module within oneproject. A:We plan to continue enhancing the functionality of the Requirements module withinQuality Center. At this time, we do not have plans to create Shared Requirements formultiple projects, but as a proxy you can manage many testing initiatives in a singleproject, thus enabling you shared requirements between them.

Q:Are there any plans to make the GUI maps in WinRunner easier to workwith? A:WinRunner 8.0 will introduce a new wizard for the GUI Map Configuration functionsthat will make it easier to use. We are constantly looking for additional improvementsfor this and other areas of WinRunner in future versions. If you have other specificrequirements 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 andagainst 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. TheDelivery Dashboard for Quality Center has specific capability to track KPI trends overtime and from one project to the next. Alternatively, you can export a standard reportto Excel and track it manually.

Q:LoadRunner. I would like the analysis tool to have multiple summary pagesso 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 alwayslooking into. I have no immediate product plans that I can share, however.

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



10/22


WinRunner vs. QuickTest Pro

Quick Comparison

Shawn LoPorto

Senior Test Automation Architect / SMEAutomated Solutions, Inc.

QATraining.net

Mercury SPP Gold Level Partner



11/22


Table of Contents

Overview .............................................................................................................................. 3WinRunner Compared to QuickTest Pro ............................................................................. 4What We Recommend ......................................................................................................... 6WinRunner ........................................................................................................................... 8

Summary: ......................................................................................................................... 8Pros: ................................................................................................................................. 9Cons: ................................................................................................................................ 9

QuickTest Pro .................................................................................................................... 10Summary: ....................................................................................................................... 10Pros: ............................................................................................................................... 11Cons: .............................................................................................................................. 11

http://www.asi-test.com/#_Toc76181590http://www.asi-test.com/#_Toc76181590http://www.asi-test.com/#_Toc76181591http://www.asi-test.com/#_Toc76181591http://www.asi-test.com/#_Toc76181592http://www.asi-test.com/#_Toc76181592http://www.asi-test.com/#_Toc76181593http://www.asi-test.com/#_Toc76181593http://www.asi-test.com/#_Toc76181594http://www.asi-test.com/#_Toc76181594http://www.asi-test.com/#_Toc76181595http://www.asi-test.com/#_Toc76181595http://www.asi-test.com/#_Toc76181596http://www.asi-test.com/#_Toc76181596http://www.asi-test.com/#_Toc76181597http://www.asi-test.com/#_Toc76181598http://www.asi-test.com/#_Toc76181598http://www.asi-test.com/#_Toc76181599http://www.asi-test.com/#_Toc76181599http://www.asi-test.com/#_Toc76181600http://www.asi-test.com/#_Toc76181600http://www.asi-test.com/#_Toc76181590http://www.asi-test.com/#_Toc76181591http://www.asi-test.com/#_Toc76181592http://www.asi-test.com/#_Toc76181593http://www.asi-test.com/#_Toc76181594http://www.asi-test.com/#_Toc76181595http://www.asi-test.com/#_Toc76181596http://www.asi-test.com/#_Toc76181597http://www.asi-test.com/#_Toc76181598http://www.asi-test.com/#_Toc76181599http://www.asi-test.com/#_Toc76181600


12/22


Overview

Today Mercury has two functional testing tools WinRunner (WR) and QuickTestProfessional (QTP). WinRunner has been around since about 1995 while QuickTest Prohas been available since about 2002. We have lots of companies asking us Whats thedifference between WinRunner and QuickTest Pro? and If they are both functionaltesting tools from the same company, then which one of the tools should we use? Thisdocument was developed as a short simple reference in helping to understand the basicsabout the tools in order to answer these two questions. Mercurys position on the two tools is this:

1 The strategic direction for Mercury and its customers for Functional Testingis product integration. The new releases of QTP and WR improve alreadyexisting 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 Mercurys prime product for best customer satisfaction and experience. For customers who need both products, Mercurycontinues to offer Mercury Functional Testing as a combined package of both

product offerings. The Business Process Testing system will be extended toincorporate components designed in WinRunner for the WinRunner 8.0 release in

November.



13/22


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, AWTSymantec Visual Caf

ActiveX ControlsERP/CRM Oracle: Jinitiator, 11i, NCA

Custom Client Server WindowsC++/C

Visual BasicOperating Systems Windows 98, 2000, NT, ME, XP

Legacy 3270, 5250 EmulatorsVT100

2 WinRunner Only Environments:

Custom Client/Server PowerBuilder Forte

DelphiCenturaStingray

SmallTalk ERP/CRM Baan

PeopleSoft WindowsSiebel 5, 6 GUI Clients

Oracle GUI Forms 3 QuickTest Pro Only Environments:

ERP/CRM SAPSiebel 7.x

PeopleSoft 8.x.Net WinForms

WebForms

.Net controlsWeb Services XML, HTTPWSDL, SOAP

J2EE, .NetMultimedia RealAudio/Video

Flash



14/22


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 TSLMDI

6 QuickTest Pro Only Environments:ActiveScreen TestGuard

Tree View ScriptFusionData Table VBScript

Function Generator*(coming in v7.0)

Run Wizard*(coming in v7.0)



15/22


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 Mercurys products since 1992 and have senior levelexpertise in WinRunner. We have been implementing WinRunner since the very firstversion of it. So like many existing WinRunner customers we have a huge knowledgeinvestment in WinRunner ourselves. However we have worked on the Mercurydevelopment 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 bea great tool to use and recommend it to all customers! Overall, we recommend usingQuickTest Pro unless for some reason you have to use WinRunner due to an unsupportedenvironment 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 foundin WinRunner, but are easier to use. QTP also offers many features not found inWinRunner that make test script creation, enhancement and maintenance easier. Lets quickly discuss some key issues:

1 The WinRunner interface forces the user to look directly at TSL code. TSL isthe WinRunner programming language developed by Mercury. It is based on theC programming language and therefore looks very similar. For testers who donot have a technical background, they are not always comfortable with having toalways look at code. However QuickTest Pro offers a Tree View which is anicon-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 thetechnical user, they can always switch over to the Expert View in QuickTestand look directly at code, and program away using VBScript.

2 WinRunner uses TSL which is a proprietary language of Mercury. Thesetypes of languages can be very restrictive and you are limited on availableresources. QuickTest Pro use the Microsoft programming language VBScriptwhich is very powerful, has lots of capabilities and there are lots of resourcesavailable.

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



16/22

For more QTP Scripts, visit www.ramupalanki.comthan WinRunner. This makes its use easier.

All the same features found in WinRunner are found in QuickTest Pro plusmore.

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 capturedfor later use. Using a point and click capability you can easily interface withobjects, their definitions and create checkpoints after having recorded a script without having to navigate back to that location in your application like you haveto 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 alarge test script investment with WinRunner. Likewise WinRunner 8.0 is to have

the ability to also call QuickTest Pro scripts. This eases the transition fromWinRunner 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 ObjectRepository).

Capturing various output values is easier and simpler with QuickTest Pro.Using this capability with parameterization enables you to easily develop scriptsthat can do more in regards to testing.

We have been implementing QuickTest Pro in real-world environments andhave 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 highlyrecommend it as the functional testing tool to use.

QuickTest Pro is our functional testing tool of choice!



17/22


WinRunner

Summary:

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

WinRunner offers a recording feature that will watch the individual tester and generate a test script tosimulate the same actions just performed. The script is displayed as a program which can be enhancedwith checkpoints, logic and special coding/programming. WinRunner also has integration with Excel spreadsheets for data driven testing and the ability to writedata 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 GUIobject, 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 withnumerous GUI objects and their functionality.

Verify data integrity in your back-end database: Built-in Database Verification confirms values stored in the database andensures 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, recordsand displays the properties of standard GUI objects, ActiveX controls, as well as Java objects and methods. This ensures thatevery 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 needto 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 andscripts. 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 multipleverifications for text, GUI, bitmaps, URLs, and databases. This ensures stable functionality and execution of businesstransactions when the application is released into production.

Validate applications across browsers: WinRunner enables the same test to be used to validate applications in InternetExplorer, Netscape, and AOL. This saves testing time and reduces the number of scripts that must be developed andmaintained.

Automatically recover tested applications from a crash: Unexpected events, errors, and application crashes during a test runcan disrupt the testing process and distort results. WinRunner's Recovery Manager enables unattended recovery and provides awizard that guides the process of defining a recovery scenario.

Leverage investments in other testing products: WinRunner fully integrates with our other testing solutions, includingLoadRunner for load testing and TestDirector for global test management. Moreover, organizations can reuse WinRunner testscripts with QuickTest Professional.

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

http://www.mercury.com/us/products/quality-center/functional-testing/winrunner/features.htmlhttp://www.mercury.com/us/products/quality-center/functional-testing/winrunner/features.html


18/22

For more QTP Scripts, visit www.ramupalanki.com 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 programminglanguage, 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.



19/22


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 Proweb page:

Mercury QuickTest Professional allows even novice testers to be productive in minutes. You can create a test script bysimply 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 rearrangetest steps in the Keyword View.

QuickTest Professional can automatically introduce checkpoints to verify application properties and functionality, for exampleto validate output or check link validity. For each step in the Keyword View, there is an ActiveScreen showing exactly how theapplication under test looked at that step. You can also add several types of checkpoints for any object to verify thatcomponents 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 manipulatedata 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-standardVBScript that QuickTest Professional automatically generates. Any changes made in the Expert View are automaticallysynchronized 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, anexpandable Tree View of the test script specifying exactly where application failures occurred, the test data used, applicationscreen shots for every step that highlight any discrepancies, and detailed explanations of each checkpoint pass and failure. Bycombining TestFusion reports with Mercury Quality Management , you can share reports across an entire QA and developmentteam.

QuickTest Professional also facilitates the update process. As an application under test changes, such as when a Login buttonis renamed Sign In, you can make one update to the Shared Object Repository, and the update will propagate to all scriptsthat reference this object. You can publish test scripts to Mercury Quality Management, enabling other QA team members toreuse 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 advancetesting scenarios, QuickTest Pro has more options and they are easier to implement compared toWinRunner in our opinion. Do to the similarities in concept and features, an experienced WinRunner user can easily convert toQuickTest 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

http://www.mercury.com/us/products/quality-center/quality-management/http://www.mercury.com/us/products/quality-center/functional-testing/quicktest-professional/works.htmlhttp://www.mercury.com/us/products/quality-center/quality-management/http://www.mercury.com/us/products/quality-center/functional-testing/quicktest-professional/works.html


20/22

For more QTP Scripts, visit www.ramupalanki.comthat they already have. As older scripts require updates and time permits, we recommend replacingthem with QuickTest Pro scripts. Eventually you will be able to convert your test script library withall 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 (Microsofts 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.0TESTDIRECTOR v 8.0Learn the way Fortune 100 Companies work with Test Director. Real Time Projects, Certified Instructors, OnlineHelp.Will show different examples which is followed by major Financial/Insurance/Pharmaceutical/Banking Companies.



21/22

For more QTP Scripts, visit www.ramupalanki.com100 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 arequirements structure Entering requirements

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

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

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

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

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

Manual test executionAutomated test executionAdding test hostsRunning a test setSetting run timesAnalyzing test results

Defect Tracing The Defect Life Cycle Reporting defectsSearching for similar defects

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

This class covers Controller and Analysis components of LoadRunner. This course is your first step towards successas 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 willgain 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. Thelesson 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 theconcepts 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 againstthe Mercury Tours application to achieve the given performance goals.



22/22

For more QTP Scripts, visit www.ramupalanki.comThis activity will validate your newly acquired knowledge on LoadRunner and on techniques for load testing Websystems.

You will use the LoadRunner Analysis component to interpret load test results. The information gathered duringplanning 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 yourapplications in the Web environment. The last day involves you to work on a comprehensive project designed totest 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 againstthe Mercury Tours application to achieve the given performance goals. This activity will validate your newlyacquired knowledge on LoadRunner and on techniques for load testing Web systems.


qtp interview questions 1

Documents