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

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

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

Agenda

Who am I?

Our mission is to help you

Win with Talent!

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

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

•  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

One Stop Shop for all Code

Populators

Developers WriHng Tests!

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

AutomaHon developers fixed bugs!

CollaboraHon

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

The Bad

One Stop Shop for all Code

Weren’t seSled before opening the flood gates

Ownership!

A lot more cooks in the kitchen!

Dependencies got entangled

•  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

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!

•  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

What QA has to say…

What development has to say…

What management has to say…

QuesHons?

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

Software

bad code case study - buildbetterbarrel › files › 25-bad-code-case-study.pdfThe following excerpt opens Swimming in a Sea of Death: A Son’s Memoir. The author David Rieff was

Back from the Dead: When Bad Code Kills a Good Server...Back from the Dead: When Bad Code Kills a Good Server Serdar Basegmez - Developi - @serdar_basegmez William Malchisky Jr. -

Detecting bad smells in source code using change history information

IS 15805-1 (2008): Straw reaper-combine - Test Code, Part

Why Everyone else writes bad code

Module 1. Introducing Course: Refactoring. Overview Definition Principles Building Tests Bad Smells in Code

How to write bad code using C#

Back from the Dead: When Bad Code Kills a Good Serverfile/engage2016.adm01.final.pdf · Back from the Dead:! When Bad Code ! Kills a Good Server Engage User Group Conference, Eindhoven!

Analyzing Code Evolution to Uncover Relations between Bad Smells

Code-Smells Detection using Good and Bad Software Design ...kdeb/papers/c2014009.pdf · Code-Smells Detection using Good and Bad Software Design Examples Usman Mansoor1, ... design

257-2012: Leave Your Bad Code Behind: 50 Ways to Make Your

Bad ,bad, bad design

Bad Smells in Software – a Taxonomy and an …mikamantyla.eu/mmantyla_thesis_final_print2.pdfIn this work, the bad code smells are studied empirically and their relationship to source

Hryszko16 Defect Prediction with Bad Smells in Code · Separate group of design metrics are metrics based on code smells, also known as bad smells or code bad smells. The term was

Automatic detection of bad smells in code

Bad I Bath. - TRUFFER VALS · Bad I Bath. Bad I Bath. Bad I Bath. Bad I Bath. Bad I Bath. Bad I Bath. Bad I Bath. Bad I Bath. Bad I Bath. Bad I Bath. Bad I Bath. Bad I Bath. Bad I

When good code goes bad

Bad Code Smells - Philipps-Universität Marburg · Was sind Bad Code Smells? ... "An exploratory study of the impact of code smells on software change-proneness." ... of software

ICONUK 2016: Back From the Dead: How Bad Code Kills a Good Server

For Entity : CITY OF COMBINE Year: 2015 State Code: