uft automation framework introduction

17
UFT Automation Framework By Himal Bandara

Upload: himal-bandara

Post on 17-Jan-2017

131 views

Category:

Documents


3 download

TRANSCRIPT

UFT Automation Framework

By Himal Bandara

Preface

While there are several frameworks that provide support for

automated software testing using HP UFT, this document introduces

one particularly effective type.

Objective

  To create a framework which supports test automation work done by UFT in QA environment by working as a tool chain.

considerations : UFT tool will be integrated and used with HP ALM. UFT Project solution, resources and test cases are stored in ALM. ALM is used as the version control repository for both test cases and test

scripts. ALM test cases will include both UFT test scripts and other test cases

related details.

Framework Architecture

Features 1. Folder Hierarchy

2. Config

Config File which use to store the Test Environment Data .In this configuration file is xml file which include system url , browser type, test data path etc.

Function Library

Contains necessary functions that needs to create and execute the test cases

This Framework has two main components Generic function library Application specific function library

Generic function library

Generic Function library is .vbs or .qfl file which include application independent common scenarios like (“Reading and writing excel data , logging functionality ”)

Application specific function library

Generic Function library is .vbs or .qfl file which include application dependent common scenarios and module like (login module , Add Course module)

Logging

Logs are captured as a text file and stored in a windows location Logs can be enabled in ALM at the execution time

Object Repository

Object repository is a collection of objects and properties Shared object repository is maintained(.tsr)

Recovery Scenarios

In order to recover the test and continue execution Can be crucial feature for large tests This framework has two recovery scenarios

Webelement is not visible Webelement  doesn’t exist

Test data

External test data is given as inputs to the test scripts to perform the same operations on the application using different set of data

The best practice here is to keep the data sheet in a common place, preferably in the test management tool.

Advantages

Increase the quality Reusability Better utilization of tools Maintenance Minimum effort High ROI

Limitations

Property files(.txt or .properties) can’t be stored in ALM as it only supports XML and MS Office documents

It is a must to have the browser extension installed and enabled to execute a test in a particular web browser

Learning resources are rare in certain areas (e.g- recovery scenarios)

Learnings And Next Ste

Support for descriptive programming Customize test reports Make the generic function library more comprehensive by adding

more generic methods Mobile, API testing support

THANKS !!!!!!!