About Software Testing QTP (Quick Test Professional)

Keen infotech is provide HPE Unified Functional Testing (UFT) software, formerly known as HP QuickTest Professional (QTP),[1] provides functional and regression test automation for software applications and environments.[2] HPE Unified Functional Testing can be used for enterprise quality assurance. HPE Unified Functional Testing supports keyword and scripting interfaces and features a graphical user interface.[4] It uses the Visual Basic Scripting Edition (VBScript) scripting language to specify a test procedure, and to manipulate the objects and controls of the application under test. HPE Unified Functional Testing was originally written by Mercury Interactive and called QuickTest Professional.[5] Mercury Interactive was subsequently acquired by Hewlett Packard(HP) in 2006.[6] HP Unified Functional Testing 11.5 combined HP QuickTest Professional and HP Service Test into a single software package,[7] which is currently available from the HP Software Division. The integrated HPE Unified Functional Testing software allows developers to test from a single console all three layers of a program's operations: the interface, the service layer and the database layer.

HPE Unified Functional Testing is automated testing software designed for testing various software applications and environments. It performs functional and regression testing through a user interface such as a native GUI or web interface.[9] It works by identifying the objects in the application user interface or a web page and performing desired operations (such as mouse clicks or keyboard events); it can also capture object properties like name or handler ID. HPE Unified Functional Testing uses a VBScript scripting language to specify the test procedure and to manipulate the objects and controls of the application under test. To perform more sophisticated actions, users may need to manipulate the underlying VBScript. Although HPE Unified Functional Testing is usually used for "UI based" Test Case automation, it also can automate some "non-UI" based test cases, such as file system operations, database testing or Web services testing. Exception handling HPE Unified Functional Testing manages exception handling using recovery scenarios; the goal is to continue running tests if an unexpected failure occurs. Because HPE Unified Functional Testing hooks into the memory space of the applications being tested, some exceptions may cause HPE Unified Functional Testing to terminate and be unrecoverable. Data-driven testing HPE Unified Functional Testing supports data-driven testing. For example, data can be output to a data table for reuse elsewhere. Data-driven testing is implemented as a Microsoft Excel workbook that can be accessed from HPE Unified Functional Testing. HPE Unified Functional Testing has two types of data tables: the Global data sheet and Action (local) data sheets. The test steps can read data from these data tables in order to drive variable data into the application under test, and verify the expected result. Automating custom and complex UI objects HPE Unified Functional Testing may not recognize customized user interface objects and other complex objects. Users can define these types of objects as virtual objects. HPE Unified Functional Testing does not support virtual objects for analog recording or recording in low-level mode. Extensibility HPE Unified Functional Testing can be extended with separate add-ins for a number of development environments that are not supported out-of-the-box. HPE Unified Functional Testing add-ins include support for Web, .NET, Java, and Delphi.HP QuickTest Professional and the HP QuickTest Professional add-ins are packaged together in HP Functional Testing software. User interface HPE Unified Functional Testing provides two views—and ways to modify—a test script: Keyword View and Expert View. These views enable HPE Unified Functional Testing to act as an Integrated Development Environment (IDE) for the test, and HPE Unified Functional Testing includes many standard IDE features, such as breakpoints to pause a test at predetermined places. Keyword view Keyword View lets users create and view the steps of a test in a modular, table format. Each row in the table represents a step that can be modified. The Keyword View can also contain any of the following columns: Item, Operation, Value, Assignment, Comment, and Documentation. For every step in the Keyword View, HPE Unified Functional Testing displays a corresponding line of script based on the row and column value. Users can add, delete or modify steps at any point. In Keyword View, users can also view properties for items such as checkpoints, output values, and actions, use conditional and loop statements, and insert breakpoints to assist in debugging a test.

QTP Software Testing Features:

Introduction to HP Quick Test Professional (QTP)

  • 1 Benefits of Automated Testing
  • Quick Test Window

Mercury Tours Site and creating your first test

  • Exploring the Mercury Tours Web Site
  • Creating an Action
  • Different Ways to Insert Calls to Actions

Object Repository

  • Test Object Model
  • Understanding How Quick Test Identifies Objects during the Run Session
  • Learning Objects in Your Application
  • Using Multiple Object Repositories

Introducing Functions and Function Libraries

  • Creating a Function
  • Associating the Function Library with Your Test

Creating Tests

  • Deciding Which Methodology to Use - Keyword-Driven or Recording
  • 2 Preparing to Create a Test
  • Dividing an Action into Two Actions

Running and Analyzing Tests

  • Running a Test
  • Analyzing Run Results


  • About Understanding Checkpoints
  • Adding New Checkpoints to a Test /li>
  • Adding Existing Checkpoints to a Test
  • Understanding Types of Checkpoints
  • Checking Objects
  • Checking Pages
  • Checking Tables
  • Running and Analyzing a Test with Checkpoints

Parameterization Tests

  • Defining a Data Table Parameter
  • Adding Parameter Values to a Data Table
  • Modifying Steps Affected by Parameterization
  • Parameterizing an Action
  • Running and Analyzing a Parameterized Test

Outputting Values

  • About Outputting Values
  • Creating Output Values
  • Storing Output Values
  • Viewing and Editing Output Values
  • Outputting Property Values
  • To create standard output values while editing your test
  • Understanding Default Output Definitions
  • Outputting a Value to an Action Parameter
  • 9 Outputting Text Values
  • Creating Text Area Output Values
  • Defining Text and Text Area Output Values
  • Outputting Table Values
  • Outputting Table Content
  • Outputting Table Properties
  • Outputting Database Values
  • Outputting XML Values

Defining and Using Recovery Scenarios

  • About Defining and Using Recovery Scenarios
  • Deciding When to Use Recovery Scenarios
  • Defining Recovery Scenarios
  • Creating a Recovery File
  • Understanding the Recovery Scenario Manager Dialog Box
  • 6 Understanding the Recovery Scenario Wizard
  • Managing Recovery Scenarios
  • Copying Recovery Scenarios between Recovery Scenario Files
  • Associating Recovery Scenarios with Your Tests
  • Adding Recovery Scenarios to Your Test
  • Removing Recovery Scenarios from Your Test
  • 12 Enabling and Disabling Recovery Scenarios
  • #qtpsoftwaretesting
  • #softwaretestingudaipur