The document discusses combining test automation code with product code. It describes the reasons for combining the code, including development wanting to write web test cases and include them in smoke tests. Both benefits and challenges of combining the code are provided. The benefits included collaboration between teams and developers writing tests. Challenges included not setting expectations properly initially, which led to issues with ownership and dependencies becoming tangled. Overall lessons centered around needing more dialogue upfront to set expectations for what was a more complex effort than anticipated.

1. 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. 2
Copyright
©
2016,
Halogen
So?ware
Inc.
All
rights
Reserved.
ConfidenHal.
Who
am
I?
Our
mission
is
to
help
you
Win
with
Talent!

3. 3
Ranked
#1
in
customer
saGsfacGon
by
every
leading
industry
analyst.
Copyright
©
2016,
Halogen
So?ware
Inc.
All
rights
Reserved.
ConfidenHal.
• 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. 4
Copyright
©
2016,
Halogen
So?ware
Inc.
All
rights
Reserved.
ConfidenHal.
A?er
Before
The
Framework
AutomaGon
Resources
AutomaGon
Core
Product
Suite
Web
AutomaGon
AutomaGon
Regression
AutomaGon
Services
File
Compare
AutomaGon
Product
Suite
Copyright
©
2016,
Halogen
So?ware
Inc.
All
rights
Reserved.
ConfidenHal.
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. 5
Copyright
©
2016,
Halogen
So?ware
Inc.
All
rights
Reserved.
ConfidenHal.
• 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. 6
Copyright
©
2016,
Halogen
So?ware
Inc.
All
rights
Reserved.
ConfidenHal.
One
Stop
Shop
for
all
Code
Copyright
©
2016,
Halogen
So?ware
Inc.
All
rights
Reserved.
ConfidenHal.
Populators

7. 7
Copyright
©
2016,
Halogen
So?ware
Inc.
All
rights
Reserved.
ConfidenHal.
Developers
WriHng
Tests!
Copyright
©
2016,
Halogen
So?ware
Inc.
All
rights
Reserved.
ConfidenHal.
ID’s
and
Locators
–
That’s
right
I
said
ID’s!!

8. 8
Copyright
©
2016,
Halogen
So?ware
Inc.
All
rights
Reserved.
ConfidenHal.
AutomaHon
developers
fixed
bugs!
Copyright
©
2016,
Halogen
So?ware
Inc.
All
rights
Reserved.
ConfidenHal.
CollaboraHon

9. 9
Copyright
©
2016,
Halogen
So?ware
Inc.
All
rights
Reserved.
ConfidenHal.
Faith
in
the
automaHon
Copyright
©
2016,
Halogen
So?ware
Inc.
All
rights
Reserved.
ConfidenHal.
• 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. 10
The
Bad
Copyright
©
2016,
Halogen
So?ware
Inc.
All
rights
Reserved.
ConfidenHal.
One
Stop
Shop
for
all
Code

11. 11
Copyright
©
2016,
Halogen
So?ware
Inc.
All
rights
Reserved.
ConfidenHal.
Weren’t
seSled
before
opening
the
flood
gates
Copyright
©
2016,
Halogen
So?ware
Inc.
All
rights
Reserved.
ConfidenHal.
Ownership!

12. 12
Copyright
©
2016,
Halogen
So?ware
Inc.
All
rights
Reserved.
ConfidenHal.
A
lot
more
cooks
in
the
kitchen!
Copyright
©
2016,
Halogen
So?ware
Inc.
All
rights
Reserved.
ConfidenHal.
Dependencies
got
entangled

13. 13
Copyright
©
2016,
Halogen
So?ware
Inc.
All
rights
Reserved.
ConfidenHal.
• 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. 14
Copyright
©
2016,
Halogen
So?ware
Inc.
All
rights
Reserved.
ConfidenHal.
My
Baby
is
ugly!
Copyright
©
2016,
Halogen
So?ware
Inc.
All
rights
Reserved.
ConfidenHal.
More
dialogue
was
needed

15. 15
Copyright
©
2016,
Halogen
So?ware
Inc.
All
rights
Reserved.
ConfidenHal.
More
complex
than
expected
Copyright
©
2016,
Halogen
So?ware
Inc.
All
rights
Reserved.
ConfidenHal.
Needed
to
set
expectaHons

16. 16
Copyright
©
2016,
Halogen
So?ware
Inc.
All
rights
Reserved.
ConfidenHal.
Increased
value
of
automaHon
Copyright
©
2016,
Halogen
So?ware
Inc.
All
rights
Reserved.
ConfidenHal.
Improved
Developer
Mobility

17. 17
Copyright
©
2016,
Halogen
So?ware
Inc.
All
rights
Reserved.
ConfidenHal.
We
can
work
together!
Copyright
©
2016,
Halogen
So?ware
Inc.
All
rights
Reserved.
ConfidenHal.
• 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. 18
Copyright
©
2016,
Halogen
So?ware
Inc.
All
rights
Reserved.
ConfidenHal.
What
QA
has
to
say…
Copyright
©
2016,
Halogen
So?ware
Inc.
All
rights
Reserved.
ConfidenHal.
What
development
has
to
say…

19. 19
Copyright
©
2016,
Halogen
So?ware
Inc.
All
rights
Reserved.
ConfidenHal.
What
management
has
to
say…
Copyright
©
2016,
Halogen
So?ware
Inc.
All
rights
Reserved.
ConfidenHal.
QuesHons?