Google News
logo
QTP/UFT Interview Questions
Unified Functional Testing (UFT), originally known as QuickTest Professional (QTP), is software that automates functional and regression testing in software applications and environments.  
 
UFT = QTP + Service Tools
 
QTP (QuickTest Professional) supports Graphical User Interface(GUI) Windows and Web-based Testing only, but UFT Supports GUI and API Testing.
 
QTP is an automated functional testing tool that assists testers in running automated tests to find any flaws, defects, or gaps in the application under the test's expected outcomes. Mercury Interactive created it, which was eventually acquired by HP and is now MicroFocus.
Web, Java (Core and Advanced),.Net, WPF, SAP, Oracle, Siebel, PeopleSoft, Delphi, Power Builder, Stingray 1, Terminal Emulator, Flex, Web Services, Windows Mobile, VisualAge Smalltalk, Silverlight and mainframe terminal emulator.
This view is a tabular representation of all the objects and the actions that are performed on them. Every row in the table is a step performed on the AUT and can be modified. Some of the most common columns displayed are items, operations, values, and documentation.

Expert view : As the name indicates, this view is for technical users who would like to tweak the source code as per their requirements.
* UFT has record and playback capabilities.
* UFT has a very good object recognition technique.
* It records scripts on an active screen and assists testers in referring to screen object characteristics.

Integration and Support: 
 
* It facilitates continuous integration by connecting with Jenkins, Git, and other similar tools.
* The tool's integration with various platforms, such as .net and mainframe, is fantastic. It works with both new and old web technologies, as well as terminal emulators and Windows thick-client apps.
* UFT enables cross-browser testing and works with all major browsers, including Internet Explorer, Firefox, Chrome, and Apple Safari. d)Its connection with ALM allows us to store automation execution results in ALM and even schedule automation execution at a specific date and time.

* It works with XML.
*
It has an integrated development environment (IDE).
* It works with test management software such as Quality Center, Test Director, and Winrunner.
* Smoke, Regression, and Sanity are examples of suites that can be simply maintained.
* QTP allows for test reporting for analysis purposes.
* Through an active screen, you can improve existing tests even if you don't have Automated Ultrasonic Testing (AUT).
* It supports a variety of automation frameworks, including keyword-driven testing, modular testing, data-driven testing, and so on.
* UFT supports Business Process Testing (BPT), a component-based testing framework that provides a strong and efficient platform for manually and automatically testing complete business processes. Its component reusability feature makes the testing process very fast, and it combines manual and automation tests with less duplication.
QTP Supports 2 types of Object Repository
 
* Per-Action Object Repository, (also called Local)
*
Shared Object Repository (also called Global)

Local Object Repository : The default object repository is the Local Object Repository. It is action-specific and can only be used for one action at a time. When the application is not time-sensitive, a local object repository is preferred. The Local Object Repository can't be utilised again. In the local object repository, you can do a variety of things, including  :
* On the application under test, highlight an object saved in a repository.
* Check to see if a specific object in your AUT is saved in the Object Repository.
* Objects can be cut, copied, pasted, modified, and deleted.
* If you mistakenly changed the value of a property, you can edit its description using the update function in the application.

Shared Object Repository : When an application is dynamic and object descriptions change frequently, a global or shared object repository is preferred. In automation projects, shared object repositories are more typically utilised than local object repositories. However, when compared to a local object store, it has higher maintenance and administration costs.
QTP identifies any GUI Object based on its corresponding properties. While recording, QTP will identify and store peculiar properties (as defined in the Object Identification settings) in the object repository of the GUI object . At run-time, QTP will compare the stored property values with the on-screen properties, to uniquely identify the GUI object.
QTP supports 3 types of recording modes :
 
1. Normal mode also called Contextual
2. Low-level recording mode
3.Analog mode
 
Normal Mode : It is the default recording mode and takes full advantage of QTP’s Test Object Model. It recognizes objects regardless of their position on -screen. This is the preferred mode of recoding and is used for most of the automation activities.

Low-level recording mode : This mode records the exact x,y co-ordinates of your mouse operations. It is helpful in testing hashmaps. It is useful for recording objects not identified by normal mode of QTP.
 
Analog mode : This mode records exact mouse and keyboard “movements” you perform in relation to the screen / application window. This mode is useful for the operation such as drawing a picture, recording signature., drag and drop operations.
* Determine Testing needs : Define Testing Environment, Analyze Your Applications and Plan Actions
* Set up repositories : Local or Shared OR
* Define function libraries
* Generate test steps : Add steps, Add checkpoints
* Data drive your tests
* Run the tests
* SystemUtil.Run
SystemUtil.Run ( FileName, Parameters, Path, Operation )
Example : SystemUtil.Run(“iexplorer.exe”,http://www.google.com)
SystemUtil.Run(“test.txt”, “”,”C:\”,”1”)
 
* InvokeApplication
Example : InvokeApplication “C:\Program Files\Internet Explorer\IEXPLORE.EXE http://www.google.com”
 
* Creating a shell object using VB Script
Example : Create a “WScript.shell” object.
Dim testshell
Set testshell= CreateObject (“Wscript.shell”)
testshell.run "%windir%\notepad"
We can call an action in 2 ways
 
* Call to copy of Action : In this ,the Action Object Repository , Script and Datable will be copied to the destination Test Script.

* Call to Existing Action : In this, Object Repository , Script and Datable will NOT be copied but a call (reference) would be made to the Action in the source script.