UFT Class 38

(UFT Test Planning)

UFT Test Process

Test Planning
Generating Basic Tests
Enhancing Tests
Running and Debugging Tests
Analyzing Test Results
Reporting Defects

Test Planning in UFT

i) Get Environment (UI design technology, Database) details from development team and select appropriate Add ins.

Application Type: Web Application

Application Environment:

> HTML for web pages design

> Activex control for some objects

> HTML with Java Script for Client side validations

> XML for Data transportation

> ASP (.NET) for Service side container

> VBScript for Server side validations

> C#, VB (.NET) for components development

> ADO (.NET) for Database connectivity

> SQL Server as Database Server

> IIS as Web server

> COM+ as Application Server
———————————
> Select Add ins

Activex
Web
.NET for Web forms

ii) Analyze the AUT (Application Under Test) in terms of Object Identification.

How to analyze:

> By Record and Playback

> Using View options in Object Repository.
(Map objects in between Object Repository and AUT)

> Using Object Spy.
——————————-
Solutions:
——————-
a) Tool level solutions

1) Object Identification Configuration

2) Use Low level and Insight Record modes.

3) Virtual Object Configuration

b) Organization level solution

Ask development team to provide proper properties information to recognize.

c) Raise Ticket to vendor

After analyzing the issues then Vendor provides solution
———————————————-
iii) Select Test cases for Automation

a) Tests that we have to execute on every build (Sanity Tests)
b) Tests that we have to execute on every modified build(Regression Tests)
c) Tests that we have to execute using multiple sets of Test data (Data driven Tests)
——————————————–
iv) Configure Tool settings and globalize

File > Settings
Tools > Options
Tools > Object Identification
———————————
v) Automation Framework Implementation (Optional)

Automation Framework Design and Implementation

> What is Automation Framework?
It is a systematic approach to automate Software Test Process.

It is a set of guidelines, assumptions and process that developed by experts
in order to perform tasks in an effective, efficient and optimized way.
——————————————–
> Why Automation Framework?
In a project Testing we create and use different types resources (files) and we perform different types of tasks, in order to store and organize them all, a systematic approach(Framework) is required.

a) Files to be created and used:
——————————-
1) Shared object Repository files (.tsr)

2) Function Library files (.vbs)

3) Environment variables files (.XML)

4) Test batch files (.mtb)

5) Recovery Scenario files (.qrs)

6) Test Data files (.txt/.xls/any other supporting files)

7) Test Results (.txt/.xls/any other supporting files

8) AOM Script files (.vbs)
—————-
b) Tasks to be performed:
————————–
1) Get Environment (UI design technology, Database) details from development team and select appropriate Add ins.

2) Analyze the AUT (Application Under Test) in terms of Object Identification.

3) Select Test cases for Automation

4) Configure Tool settings and globalize

5) Automation Framework Implementation

i) Create a Folder structure to store Automation Resources.

ii) Create Automation Resources and store.

iii) Create Organizer file (Excel file)

iv) Create Driver Script (UFT Test)

v) Create Initialization Script (AOM Script, vbs file)

vi) Execute Sanity Tests

vii) Execute Comprehensive Tests

viii) Analyze the Test Result and Report defects

ix) Execute Sanity Tests on modified build

xi) Execute Regression Tests- Cycle 1

xii) Analyze the Test Result and Report defects

xiii) Execute Sanity Tests on modified build

xiv) Execute Regression Tests- Cycle 2
.
.
.
***) Final Regression

***) Modify Automation Resources (If required)
***) Maintenance of Automation Resources

Folder Structure:

MainFolder
ObjectRepository (To store Shared object Repository files)
FunctionLibrary (To store Library files)
Recovery (To store Recovery scenario files)
Environment (To store Environment variable files)
Test Data (To store Test Data files)
Test Results (To store Test Result files)
TestScenarios (To store Test Scenario files)
Organizer (To store Organizer file)
Drivers (To store driver scripts)
Miscellaneous (Process guidelines doc, Approval docs, instructions by Team lead etc…)
——————
Initialization script (.vbs file)