The document outlines five steps for detecting issues earlier in the software release cycle, emphasizing collaboration and effective testing practices. Key strategies include speaking the same language, writing stable tests, breaking down monoliths, increasing testing frequency, and providing context for results. The overall goal is to minimize rework and enhance the efficiency of app development.

1. Beyond
Shi+
Le+
5
Steps
to
Detec+ng
Issues
Earlier
in
Your
Release
Cycle

2. #beyondshi+le+
@perfectomobile
What
We’ll
Cover
• Our
Climate
Is
Changing
• Why
Are
Top
Performers
Winning?
• Less
Time
Fixing,
More
Time
CreaEng
• Fast
Feedback
in
5
Steps
• Speak
the
Same
Language
• Write
Stable
Tests
• Break
Up
the
Monoliths
• Test
More
in
Every
Build
• Provide
Context
with
Results
• Q
&
A

3. #beyondshi+le+
@perfectomobile
Our
Presenters
Paul
Bruce
Developer
Evangelist
@paulsbruce
Nick
Sanjines
Systems
Engineer
@NickSanjines

4. work
fast
learn
o+en

5. #beyondshi+le+
@perfectomobile
The Effect of “Climate Change” on App Development
Infrastructure
is
cheap
Releasing
is
easy
Faster
to
create
apps
Automate
everything
Release
more
frequently
People
expect
great
apps
Maintenance
is
costly
At
risk
more
o+en
Higher
stakes
for
business

6. #beyondshi+le+
@perfectomobile
#defectshappen
:

7. #beyondshi+le+
@perfectomobile
Top
Performers
● Releasing
is
run-­‐rate
more
o+en
● Manage
change
early
recovery
● Small
batch
sizes
less
lead
Eme
● Less
unplanned
work
more
new
work
State
of
DevOps
2016,
Puppet
Labs

8. quality
impacts
velocity

9. #beyondshi+le+
@perfectomobile
Less
Cme
fixing,
more
Cme
creaCng,
From
this:
● Unclear
goals
● Technical
debt
● Fire
fighEng
● Release
risk
To
this:
● User
saEsfacEon
● Be^er
decisions
● Higher
confidence
Defects
Backlog
Features
Time

10. #beyondshi+le+
@perfectomobile
How
do
we
spend
less
Cme
on
re-­‐work?
• Catch
defects
earlier
• Simplify
diagnosis
and
fixing
• Automate
repeEEve
tesEng
• Foster
fast
feedback
“As
an
engineer,
you
should
constantly
work
to
make
your
feedback
loops
shorter
in
+me
and/or
wider
in
scope.
”
—
@KentBeck
Source:
IBM
System
Science
InsEtute

11. #beyondshi+le+
@perfectomobile
5
Steps
to
DetecCng
Issues
Earlier
1.
Speak
the
Same
Language
2.
Write
Stable
Tests
4.
Test
More
in
Every
Build
3.
Break
Monoliths
Apart
5.
Provide
Context
with
Results

12. speak
the same
language

13. #beyondshi+le+
@perfectomobile
Why
speak
the
same
language?
• Simplifies
collaboraEon
on
tesEng
• Enables
tests
to
reuse
code
arEfacts
• Makes
code
and
tests
equal
ciEzens
Selenium
App
Code
Java,
Javascript,
C#,
etc.

14. 2
write
stable
tests

15. #beyondshi+le+
@perfectomobile
How
do
we
write
stable
tests?
• Reduce
technical
gaps
in
object
idenEficaEon
• Clean
setup
/
teardown
procedures
• Be
as
hermeEc
as
possible
• Soak
new
tests
before
checking
them
in

16. 3
break
monoliths
apart

17. #beyondshi+le+
@perfectomobile
Job
Total
CI
Eme
budget
Test
Time
(avg.)
Scope
Commit
(VCS)
15-­‐30
mins
<100ms
Unit,
API,
IntegraEon
Hourly
20-­‐40
mins
Varies
New
Tests,
Key
Smoke
(BVT)
MulEple/day
30-­‐60
mins
<2s
All
Smoke,
Key
FuncEonal,
Some
Data
Nightly
2-­‐7
hrs
<120s
All
FuncEonal,
All
Data
Weekend
10-­‐48
hrs
all
All
Tests
incl.
Performance
Don’t
leave
all
the
regression
tesCng
to
the
end!
An
anecdotal
example,
your
own
mileage
will
vary

18. 4
test
more
in
every
build

19. #beyondshi+le+
@perfectomobile
What
does
“more”
mean
in
terms
of
your
audience?
Digital
Test
Coverage
Index
Q4
2016,
5th
EdiEon
bit.ly/DTC-­‐index-­‐5

20. 5
provide
context
with
results

21. #beyondshi+le+
@perfectomobile
5
Steps
to
DetecCng
Issues
Earlier
1.Speak
the
Same
Language
2.
Write
Stable
Tests
4.
Test
More
in
Every
Build
3.
Break
Monoliths
Apart
5.
Provide
Context
with
Results

22. #beyondshi+le+
@perfectomobile
Q
&
A
Paul
Bruce
Developer
Evangelist
@paulsbruce
Nick
Sanjines
Systems
Engineer
@NickSanjines