UFT Tutorial 38

UFT Class 38 (UFT Test Planning)

UFT Test Process
    Test Planning
    Generating Basic Tests
    Enhancing Tests
    Running too Debugging Tests
    Analyzing Test Results
    Reporting Defects
----------------------------------

Test Planning inwards UFT

i) Get Environment (UI blueprint technology, Database) details from evolution squad too pick out appropriate Add ins.

Application Type: Web Application

Application Environment:

> HTML for spider web pages design

> Activex command for around objects

> HTML alongside 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 every bit Database Server

> IIS every bit Web server

> COM+ every bit Application Server
---------------------------------
> Select Add ins

Activex
Web
.NET for Web forms
---------------------------
ii) Analyze the AUT (Application Under Test) inwards damage of Object Identification.

How to analyze:

> By Record too Playback

> Using View options inwards Object Repository.
(Map objects inwards betwixt Object Repository too AUT)

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

    1) Object Identification Configuration

    2) Use Low score too Insight Record modes.

    3) Virtual Object Configuration

b) Organization score solution

Ask evolution squad to render proper properties information to recognize.

c) Raise Ticket to vendor

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

    a) Tests that nosotros convey to execute on every prepare (Sanity Tests)
    b) Tests that nosotros convey to execute on every modified build(Regression Tests)
    c) Tests that nosotros convey to execute using multiple sets of Test information (Data driven Tests)
--------------------------------------------
iv) Configure Tool settings too globalize

File > Settings
Tools > Options
Tools > Object Identification
---------------------------------
v) Automation Framework Implementation (Optional)
---------------------------------------------------------
Automation Framework Design too Implementation

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

Or

It is a laid of guidelines, assumptions too procedure that developed past times experts
in lodge to perform tasks inwards an effective, efficient too optimized way.
--------------------------------------------
> Why Automation Framework?
In a projection Testing nosotros practise too role unlike types resources (files) too nosotros perform different  types of tasks, inwards lodge to shop too organize them all, a systematic approach(Framework) is required.

a) Files to last created too 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 last performed:
--------------------------
1) Get Environment (UI blueprint technology, Database) details from evolution squad too pick out appropriate Add ins.

2) Analyze the AUT (Application Under Test) inwards damage of Object Identification.

3) Select Test cases for Automation

4) Configure Tool settings too globalize

5) Automation Framework Implementation

    i) Create a Folder construction to shop Automation Resources.

    ii) Create Automation Resources too 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 too Report defects

    ix) Execute Sanity Tests on modified build
   
    xi) Execute Regression Tests- Cycle 1

    xii) Analyze the Test Result too 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 shop Shared object Repository files)
    FunctionLibrary (To shop Library files)
    Recovery (To shop Recovery scenario files)
    Environment (To shop Environment variable files)
    Test Data (To shop Test Data files)
    Test Results (To shop Test Result files)
    TestScenarios (To shop Test Scenario files)
    Organizer (To shop Organizer file)
    Drivers (To shop driver scripts)
    Miscellaneous (Process guidelines doc, Approval docs, instructions past times Team atomic number 82 etc...)
    ------------------
    Initialization script (.vbs file)
----------------------------------------
Types of Automation Framework

1) Record too Playback/Linear Framework

2) Data Driven Framework

3) Modular Framework

4) Keyword Driven Framework

5) Hybrid Framework

Ex: Keyword Driven Framework & Data Driven Framework)
------------------------
Keyword Driven Framework

In this approach Tests tin terminate last created too executed using Keywords.

Keyword:

A telephone commutation to the code.

Or

It is a reserved give-and-take that refers a Command / Function/Object/Method/Statement etc...
------------------------
Keywords inwards UFT Test Automation:

a) UFT Keywords:

Ex: Test Object, Utility object, Method etc...

b) VBScript Keywords

Ex: Automation Object, Function, Method, Statements etc...
-----------------------------------------------------

Sumber http://www.gcreddy.com/
Post a Comment (0)
Previous Post Next Post