Book Image

Advanced UFT 12 for Test Engineers Cookbook

Book Image

Advanced UFT 12 for Test Engineers Cookbook

Overview of this book

Related Content you might be interested in

Current Title:

Small book image
Advanced UFT 12 for Test Engineers Cookbook
Nov, 2014 | 272 pages
No titles found
Table of Contents (18 chapters)
Advanced UFT 12 for Test Engineers Cookbook
Advanced UFT 12 for Test Engineers Cookbook
Credits
Credits
About the Authors
About the Authors
About the Reviewers
About the Reviewers
www.PacktPub.com
www.PacktPub.com
Preface
Preface
Free Chapter
1
Data-driven Tests
Data-driven Tests
Introduction
Creating a DataTable parameter
Retrieving data from a DataTable
Storing data in a DataTable
Importing an Excel file to a test
Exporting a DataTable
Parameterizing Test Object properties
Defining test cases using a DataTable
Storing data in the Environment object
Retrieving data from the Environment object
Reading values from an INI file
Using a configuration file to manage test environments
Using a global dictionary for fast shared data access
Using a global dictionary for fast shared code access
2
Testing Web Pages
Testing Web Pages
Introduction
Checking whether page links are broken
Deleting cookies
Managing multiple browser windows
Handling pop-up dialogs
Downloading a file using XMLHttp
Checking whether a website is up
Uploading a file using FTP
Identifying elements based on anchors
Synchronizing a test with a web page loading
Accessing web elements through DOM
3
Testing XML and Database
Testing XML and Database
Introduction
Establishing and closing a database connection
Using SQL queries programmatically
Using a database checkpoint
Using an XML checkpoint
4
Method Overriding
Method Overriding
Introduction
Overriding a Test Object method
Registering a method to all classes
Using method overriding to support object subtypes
Adding a new method to a class
5
Object Identification
Object Identification
Introduction
Setting mandatory and assistive properties for a class
Using Descriptive Programming inline
Using the Description object
Using child objects
Using native properties for object identification
Identifying an object based on its parent
6
Event and Exception Handling
Event and Exception Handling
Introduction
Catching errors inside a function or subroutine
Creating and using a recovery scenario
Using a global dictionary for recovery
7
Using Classes
Using Classes
Introduction
Implementing a class
Implementing a simple search class
Implementing a generic Login class
Implementing function pointers
Implementing a generic Iterator
8
Utility and Reserved Objects
Utility and Reserved Objects
Introduction
Using global variables (Environment)
Customizing mouse operations (DeviceReplay)
Managing processes (SystemUtil)
Measuring time (MercuryTimers)
Resolving file locations (PathFinder)
Loading shared object repositories (RepositoriesCollection)
Loading and creating XML documents (XMLUtil)
Drawing a rectangle on the screen with Win32 API methods (Extern)
Verifying binary file contents (FileCompare)
Implementing a custom reserved object
Using remote objects
Utility statements
9
Windows Script Host
Windows Script Host
Introduction
Reading a key from the Windows system registry
Writing a key to the Windows system registry
Deleting a key from the Windows system registry
Running a process using the Windows system shell
10
Frameworks
Frameworks
Introduction to test automation frameworks
Designing a test automation framework
Building a test controller
Building a reusable component (action)
Building an event handler
Building a test reporter
Design Patterns
Design Patterns
Auxiliary classes and functions
Action patterns
Runtime data patterns
Index
Index

Introduction

The topic of exception handling is extremely important, because the robustness of an automation suite affects its reliability. An automated test may fail due to unhandled and unexpected events, such as the appearance of a pop-up dialog or window, an application crash, or a runtime error (for example, due to poor quality code or an object description that is outdated). If you do not consider such possibilities while designing your scripts, then it will reflect on your ability to rely on the suite and accordingly reduce the return on investment/effort of automation. For instance, a fragile, unstable automation suite may require attended run sessions, thus making one of the most prominent promises of automation (to free the manual tester for other tasks) void. This chapter will describe various techniques to handle events and exceptions.

Previous Section
End of Section 2
Next Section