i'm looking at you to tell me, should i automate v10

I’m looking at you to tell me…

Derk-Jan de GroodTest Automation Day 2013

1

Should I Automate ?

Our old and new approach

2

Reasonable arguments

Economics

BR

IC

Increasing complexityC

ontin

ues

Del

iver

y

Shorter life cycle

Differentiation devices

Virt

ualiz

atio

n

SC

RU

M

Data mining

TiP

Test Design tools

Next generation

TA is inevitable

4

5

…and that summarizes why we should do TA

All well, but what is the financial impact ?

Message

6

Quantising benefits of TA is a

necessity

Its our task to get organisation to start with TA

7

You still do manual tests ?

Perceived benefits

8

Where does it hurt?

CoverageThroughput time (time to market)Variance in executionCosts

10

You told me testing would be fast

Yeah, but we test twice as much now

We want it all….

Succes stories are written in chapters….

Make a step plan

One goal for each step

A calculated benefit for each step

11

Quantizise

Cost of Bugs in production

Cost of go-live slippage

Cost of testing activities

12

Best

Guess

Business case

The cost of benefits of TA

13

Embedding TA in organisation

14

Vision

The need

The Goals

Tool preference

Outsourcing

Measurement of succes

15

  Regression test Backlog 

esting new functionality in e.g. projects

Design

ScriptsAction wordsDataInfrastructure/Framework

Questions that drive the BC

16Does the solution fit the vision?

What is expected PayBack period?

What is expected profit?

What does automating these tests cost?

What TA solutions are already in place?

What does this mean for the tool requirements?

What charactizes these test technically?

Automation of what tests yield most benefit?

What tests are executed?

Think out of the box!

Scenario’s

Tailor made

solutions

Technical clustering

Window(loket model)

17

Scenario’s

18

Set-up

• Tool/partner selection• Planning

Backlog

• Automating testcases• Testing the testcases

operational

• Executing• Updating

operation

al

• Executing • Updating

Estimate

Nr of releases/builds

The impact of planned changes (project portefolio)

Time to script a e.g. usecase

Define classes/action words

Create batches

Control various co-operating tools

Collect data from various tools

Set-up a reporting shell

Define and validate data

19

operational

• Executing• Updating

Estimate

PoC

Licence costs

Resources organizing the Set-up

Setting up a measurement program

20

Set-up

• Tool/partner selection• Planning

Backlog

• Automating testcases• Testing the testcases

Finalizing test

Setting up interfaces

Hooking on to Build and config management

Etc..

If you can’t predict….

21

Window not effective?

22

Session on TADAY 2012

23

1 NeedsWhy automate testing?

2 DefineWhat tests should be automated, Reuse existing test or define new tests

3 PreconditionsInfrastructure and tool selection. These are the technical constraints that need to be in order to be able to automate filled.4 Usage Embedding of test automation into existing processes necessary.5 OrganizationAre resources and knowledge available?

Window not effective

24

Other models

26

ROI model

27

The ROI depend on the number of

excutions and the amount of

maintance required to do so

Change the model: Move from maintance to instant benefit.

Pre-Condition

28

Message generator

29

30

Mirror (stub)

Test mokey

Ask John Fodeh !

31

32

Remember the questions

33

Get started !

Wrap up

35

Wrap up

36

Downloads

37

http://djdegrood.wordpress.com/2013/05/15/test-automation-is-inevitable-mind-map/

http://djdegrood.wordpress.com/2012/06/22/test-automation-day-should-we-do-ta/

http://wp.me/a1AlVM-ei

Derk-Jan

ValoriColtbaan 4a3439 NG NIEUWEGEINThe Netherlands

• derkjandegrood@valori.nl• +31(0)651807878• www.valori.nl• @DerkJanDeGrood• http://djdegrood.wordpress.com

Derk-Jan

38

Succes with getting started !