Combine Test Automation Code with Product Code: The Good, the Bad, and the Lessons Learned

1

COMBINE TEST AUTOMATION CODE WITH PRODUCT CODE The Good, The Bad and The Lessons Learned May 5th 2016

Copyright © 2016, Halogen So?ware Inc. All rights Reserved. ConfidenHal.

•  Who am I? •  Who is Halogen? •  The Framework •  Why we did it? •  The Good •  The Bad •  The Lessons Learned •  QuesHons

Agenda

2


Who am I?

Our mission is to help you

Win with Talent!

3

Ranked #1 in customer saGsfacGon by every leading industry analyst.


•  Key word driven •  WriSen in Java •  Using Selenium for UI •  Rest Assured for API •  Over 2000 tests •  Over 22,000 validaHons •  Run at least once daily – working towards conHnuous integraHon •  Run is spread evenly over 30 VM’s •  Retry on failure implemented •  Used by MarkeHng to test corporate site

The Framework

4


A?er Before

The Framework

AutomaGon Resources

AutomaGon Core

Product Suite

Web AutomaGon

AutomaGon Regression

AutomaGon Services

File Compare

AutomaGon

Product Suite


The Framework

AutomaGon Resources

AutomaGon Core

Product 1

Web AutomaGon 1

AutomaGon Regression

AutomaGon Services

File Compare

Product 2

Web AutomaGon 2

Product 3

Web AutomaGon 3

5


•  With the shi? to agile, quality became the priority •  Development wanted to write Web Test Cases •  Development wanted to include Web Tests as part of their smoke test for

the build −  Become part of our CI build

•  Wanted to share page classes •  Common framework that everyone could use

−  All talk the same language •  Allow developers to run tests locally

−  Bug X causes test Y to fail −  Dev can reproduce on own machine

Why we put the code together?

The Good

6


One Stop Shop for all Code


Populators

7


Developers WriHng Tests!


ID’s and Locators – That’s right I said ID’s!!

8


AutomaHon developers fixed bugs!


CollaboraHon

9


Faith in the automaHon


•  One Stop Shop For All Code •  Populators •  Developers wriHng tests! •  ID’s and Locators •  AutomaHon developers fixed bugs! •  CollaboraHon •  Faith in the automaHon

The Good

10

The Bad


One Stop Shop for all Code

11


Weren’t seSled before opening the flood gates


Ownership!

12


A lot more cooks in the kitchen!


Dependencies got entangled

13


•  One Stop Shop For All Code •  Weren’t seSled before opening the flood gates •  Ownership •  Too many cooks in the kitchen •  Dependencies got entangled

The Bad

The Lessons Learned

14


My Baby is ugly!


More dialogue was needed

15


More complex than expected


Needed to set expectaHons

16


Increased value of automaHon


Improved Developer Mobility

17


We can work together!


•  My Baby is ugly! •  More dialogue was needed •  More complex than expected •  Needed to set expectaHons •  Increased value of automaHon •  Improved Developer Mobility •  We can work together!

The Lessons Learned

18


What QA has to say…


What development has to say…

19


What management has to say…


QuesHons?

Combine Test Automation Code with Product Code: The Good, the Bad, and the Lessons Learned

Software

Transcript of Combine Test Automation Code with Product Code: The Good, the Bad, and the Lessons Learned