Rehearsal of QTP in 1 Hr: Interview Questions 101 – 110
While appearing in an interview for a position on HP QuickTest Professional, do a quick rehearsal of your knowledge on this tool.
Here is a collection of 180 short questions, QTP Managers commonly use while interviewing new aspirants for their organization.
The entire rehearsal of these questions can take less than an hour.
Set of Ten Questions
Q. 101: What the differences are and best practical application of each of the Object Repositories?
Per Action: For Each Action, one Object Repository is created.
Shared: One Object Repository is used by entire application
<<<<<< =================== >>>>>>
Q. 102: Explain the difference between Shared Repository and Per Action Repository?
Shared Repository: Entire application uses one Object Repository, that similar to Global GUI Map file in WinRunner
Per Action: For each Action, one Object Repository is created, like GUI map file per test in WinRunner
<<<<<< =================== >>>>>>
Q. 103: Have you ever written a compiled module? If yes tell me about some of the functions that you wrote.
I had used the functions for capturing the dynamic data during runtime.
Function used for Capturing Desktop, browser and pages.
<<<<<< =================== >>>>>>
Q. 104: How do you hide the Add-In Manager so that it will not be displayed while launching QTP?
a) Uncheck “Show on Startup” checkbox in the Add-In Manager
b) Uncheck “Display Add-In Manager on Startup” in the General tab of Options dialog box.
<<<<<< =================== >>>>>>
Q. 105: Can you do more than just capture and playback in QTP?
I have done dynamically capturing the objects during runtime in which no recording, no playback and no use of repository is done at all.
It was done by the windows scripting using the DOM(Document Object Model) of the windows.
<<<<<< =================== >>>>>>
Q. 106: Can you quickly summarize QTP � Some of the salient features & benefits?
Although it is a bit difficult to remember so much of the information as given below, however you can just glance through the contents & present the maximum out of it as per the memory in the event such a question is asked.
Following description has been taken from the Mercury Interactive “How it Works” section of the QTP web page:
QTP provides an interactive, visual environment for test development. Mercury QTP 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.
QTP 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 QTP 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.
QTP 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.
QTP supports functional testing of all popular environments, including Windows, Web, .Net, Visual Basic, ActiveX, Java, SAP, Siebel, Oracle, PeopleSoft, terminal emulators, and Web services.
People like QTP and now prefer implementing it over WinRunner. When you get into advance testing scenarios, QTP 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 QTP and quickly become an efficient Test Automation Engineer!
We recommend that existing customers begin all new development with QTP and use the built-in feature of calling WinRunner scripts from QTP for all existing WinRunner scripts that they already have. As older scripts require updates and time permits, we recommend replacing them with QTP scripts. Eventually you will be able to convert your test script library with all QTP 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.
# QTP 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 QTP.
# Parameterization easier than WinRunner.
# Can enhance existing QTP 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 QTP 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 QTP compared to WinRunner.
# Integrates with TestDirector and WinRunner (can kick off WinRunner scripts from QTP).
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.
<<<<<< =================== >>>>>>
Q. 107: Explain the terms “TEST” and ” Business Component”
Test: A collection of steps organized into one or more actions, which are used to verify that your application performs as expected. By default each test begins with a single action.
Business Component: A collection of steps representing a single task in your application.
Business components (also known as components) are combined into specific scenarios to build business process tests in Mercury Quality Center with Business Process Testing.
A component does not contain actions, you add steps directly to a component.
<<<<<< =================== >>>>>>
Q. 108: Can you quickly tell me – What is a checkpoint?
A checkpoint checks specific values or characteristics of a page, object, or text string and enables you to identify whether or not your Web site or application is functioning correctly.
A checkpoint compares the value of an element captured in your test when you recorded your test, with the value of the same element captured during the test run.
<<<<<< =================== >>>>>>
Q. 109: What do you mean by iteration?
Each run session that uses a different set of parameterized data is called an iteration.
<<<<<< =================== >>>>>>
Q. 110: What is output value?
An output value is a value retrieved during the run session and entered into your Data Table or saved as a variable or a parameter.
Continue to Next Set of QTP Rehearsal Questions 111 – 120
An expert on R&D, Online Training and Publishing. He is M.Tech. (Honours) and is a part of the STG team since inception.