8/9/2019 Automation Estimation

1/4

www.gcreddy.com

Automation Estimationand Analysis

Visit:

www.gcreddy.com

for QTP scripts and Documents

Automation Estimation andAnalysis

1

http://www.gcreddy.com/http://www.gcreddy.com/

8/9/2019 Automation Estimation

2/4

www.gcreddy.com

Approach (2 types) Functionality based (one to many) Scripts (Test case) based(one to one)

Should attend (take) Knowledge Transfer sessionon the given task

Automation Process 2 StagesFirst stage

a. Analyzing the scripts (Test cases)b. Preparing analysis sheetc. Estimating the timed. Sending summary for Approvale. Confirmation

Second stage

a. Preparing strictureb. Preparing OR

c. Creating re-usable components and functionsect.

d. Creating scripts and Enhancing scriptse. Dry runf. Final Executiong. Peer Executionh. Delivery of scripts

2

8/9/2019 Automation Estimation

3/4

www.gcreddy.com

Detailed study of stage oneAnalyzing scripts: with out manual execution we cant saywhether scripts is automatable or not

It is a critical and important stage Entire task lay on this stage

How many Scripts we can analyze in a day?

As an automation engineer we have to decide scriptcomplexity for automation.

How can we decide whether the script is high or medium

or low?

In order to decide that we will see a single script forexample

Analysis summaryScript

IDDescription

Re- UseableModule

Category

AccountType

AccountStatus

Verification

# of ReusableScreens /

Transactions

# of EffectiveScreens /

Transactions

# ofSteps

# ofInput

Parameters

# ofCheckPoints

# ofOutputParame

ters

# ofRecover

yScenario

s

Remark

ScriptComplexit

y

3

8/9/2019 Automation Estimation

4/4

www.gcreddy.com

Estimation:

SNO Complexity No of Scripts Days of Estimation

1 Very High 0NA

2 High 8 8 * 4 hr =32 (4 Days)

3 Medium 12 12 * 2.5 hr = 30 (3.75 Days)

4 Low 10 10 * 2 hr = 20 (2.5 Day)

Total Scripts 30 Total 10.25 Days (82 hrs)

10.25 / 1 = 10.25

Feasible 30

Script Clarification 0

Waiting for Data 0

Non-Feasible 20

Total 50

3 Types of Maintenances (Modifications)

1. Corrective maintenance (Fixes): involved correctingsoftware failures, performances failures andimplementation failures in order to keep the systemworking properly.

2. Adapting the system in response to changing datarequirements or processing environments constitutescalled as adaptive maintenance.

3. Perfective maintenancecovers any enhancement tothe system where the objective may be to provideadditional functionality, increased processingefficiency or improved maintainability.

4