27
Failure and Success in Software Automation Comparing 7 Projects Oleksandr Reminnyi

Failure and Success in Software Automation by Oleksandr Reminnyi

Embed Size (px)

DESCRIPTION

Oleksandr Reminnyi, System Architect at SoftServe, Inc. compared seven projects for his presentation on Failure and Success in Software Automation at the 2013 IT Weekend Ukraine conference that took place on September 14, 2013, in Kyiv, Ukraine. Here`s Oleksandr`s presentation.

Citation preview

Page 1: Failure and Success in Software Automation by Oleksandr Reminnyi

Failure and Success in Software Automation

Comparing 7 Projects

Oleksandr Reminnyi

Page 2: Failure and Success in Software Automation by Oleksandr Reminnyi

Pre word

▪ The only identification of project being successful is the fact that your customer is happy.

PMbook

Page 3: Failure and Success in Software Automation by Oleksandr Reminnyi

Understanding the goals

We want to save money and time later on manual testingWe have a corporate direction…But the main is…Automation is a BUZZ word

Page 4: Failure and Success in Software Automation by Oleksandr Reminnyi

Average Automation Reality

Page 5: Failure and Success in Software Automation by Oleksandr Reminnyi

Automation AND Skill Set

Page 6: Failure and Success in Software Automation by Oleksandr Reminnyi

HOKKU

«Let`s automate everything!», the client said. And Mount Fuji trembled.

Page 7: Failure and Success in Software Automation by Oleksandr Reminnyi

Customer skills

Should customer be mature in automation?

This is definitely not a prerequisite.

But it can influence…

Page 8: Failure and Success in Software Automation by Oleksandr Reminnyi

ХОККУ

Читаю чужі тести і торкається моїх скронь сивина…То мозок проливається

Page 9: Failure and Success in Software Automation by Oleksandr Reminnyi

Automation Dev. Team Skills

Does mature mean good automation here?

Not always.

Practices mean more.

Page 10: Failure and Success in Software Automation by Oleksandr Reminnyi

Automation AND Time line

Page 11: Failure and Success in Software Automation by Oleksandr Reminnyi

Automation and SDLC

When the automation might be successful?

Waterfall OR Agile?

Depends on automation layer;

Post release period!

Page 12: Failure and Success in Software Automation by Oleksandr Reminnyi

Implementation OF one TC

Depends on complexityDepends on number of steps

Depends on tested application instrumentation

Average 4 to 20 man hours. Happens 50

Page 13: Failure and Success in Software Automation by Oleksandr Reminnyi

Automation Toolset

Page 14: Failure and Success in Software Automation by Oleksandr Reminnyi

Automation and Backend

Unit TestsReally? Why?

Component/integration testingGood job!

Service layer automationDefinite place to automate!

Page 15: Failure and Success in Software Automation by Oleksandr Reminnyi

Automation And TOOLS

Can tool influence the success of automation?YES!

Page 16: Failure and Success in Software Automation by Oleksandr Reminnyi

Automation of Mobility

Can mobile platform automation be buried before birth?

YES!Silk Mobile -

$5000 per dev. per year,

20-30% failure rate only because of the tool issues

MonkeyTalk, Ranorex, etc.Build in the agent, then find issues

Appium maybe light in the end of the tunnel. But later

Consider out of device testing!

Page 17: Failure and Success in Software Automation by Oleksandr Reminnyi

Documentation

Page 18: Failure and Success in Software Automation by Oleksandr Reminnyi

Can automation exist without regression test Cases suite?

YES!

At least they say it’s successful…

Page 19: Failure and Success in Software Automation by Oleksandr Reminnyi

Different types of manual test cases being Automated

- Functional- Regression- Acceptance- …

Benefit is brought at once by

Smoke ones

Page 20: Failure and Success in Software Automation by Oleksandr Reminnyi

Automation Metrics

Page 21: Failure and Success in Software Automation by Oleksandr Reminnyi

HOKKU

Sacura`s leaves are destined to fall down.Once again we`ll see the Test Report in red.Not only leaves are down.

Page 22: Failure and Success in Software Automation by Oleksandr Reminnyi

What is usually Calculated?

ROI? Nothing!

Sometimes:

Failure Rate Suite Run Duration

Page 23: Failure and Success in Software Automation by Oleksandr Reminnyi

Given architecture…

SUT UI Other SUT facilities that can be hooked but not needed for automation tool accessServices …

Layer Test scriptsTest scriptsFunctional Libraries

Layer Test scriptsTest scriptsTest scripts

Fr

amew

ork

utiliti

esBa

se c

lass

esRe

porti

ng

Load

ing

confi

gura

tion

Logg

ing

Etc.

Layer Test scriptsTest scriptsUI Maps – facilities to access UI (or other services) through automation tools API

Som

etim

es jo

ined

Layer Automation Tool

DB

Hel

pers

Faci

lities

to h

ook

into

SU

T th

roug

h AF

Mul

ti - l

ayer

ed a

rchi

tect

ure

Page 24: Failure and Success in Software Automation by Oleksandr Reminnyi

Gave us possibility to collect More metrics

Page 25: Failure and Success in Software Automation by Oleksandr Reminnyi

Something obvious

Page 26: Failure and Success in Software Automation by Oleksandr Reminnyi
Page 27: Failure and Success in Software Automation by Oleksandr Reminnyi

Questions?

“I see the testing standards that do not tell me how to create a test worthy of running." 

DeMarco