Case Study: American Family Insurance Leverages CA Service Virtualization to Accelerate Continuous Integration in Development

World®
’16
Case Study: Leveraging CA Service
Virtualization to Accelerate Continuous
Integration in Development
Jeff De Meyer - Software Engineer - American Family Insurance
DO5T04S
DEVOPS

2 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
© 2016 CA. All rights reserved. All trademarks referenced herein belong to their respective companies.
The content provided in this CA World 2016 presentation is intended for informational purposes only and does not form any type
of warranty. The information provided by a CA partner and/or CA customer has not been reviewed for accuracy by CA.
For Informational Purposes Only
Terms of this Presentation

Abstract
Jeff De Meyer (Software Engineer) discusses how leveraging Service Virtualization in Unit Testing
accelerates continuous integration in development.
Virtual services are generally more effective when put in the hands of talented developers.
Leveraging virtual services, in lieu of live systems, during continuous integration unit testing has
proven to reduce testing cycle times from 6+ hours to under 1 hour. This allows for more testing
cycles to be executed, along with new code being checked in earlier and more often, during a
sprint. The results are more testing, defects being found earlier, more rapid development, and
better application quality being produced in development tiers.
Jeff De
Meyer
American Family
Insurance
Software Engineer

Agenda
RELEASE EARLY, RELEASE OFTEN
RESEARCH TO FIND OUT WHERE IT HURTS AND WHAT CAN BE DONE
Q & A
IMPLEMENT A PLAN TO ALLEVIATE THE PAIN
EXECUTE THE PLANS AND REAP YOUR ROI
OTHER AREAS THAT HAVE BENEFIT FROM SERVICE VIRTUALIZATION
1
2
3
4
5
6

Almost all of us have heard about this before…
What is the true cost of finding a bug
early in the SDLC versus later? Almost
all of us have seen a presentation that
chronicles this very simple truth about
bugs. Finding them earlier is better
(and exponentially cheaper to fix)!
Yet how can we test more code,
earlier, when we are given less and
less time to develop and test our code?

Release Early, Release Often

Typical SDLC Release of Code
Code gets
checked into
the dev region’s
repository and
deployed to the
dev tier.
The next
deployment of
code to the dev
tier cannot take
place until the
current
deployment
finishes up its
unit tests.
Unit tests
are run.
If unit tests
pass, usually a
smoke test is
run and then
the package is
promoted to
the integration
tier.
You can only
release as early
and as often as
the speed at
which your unit
tests are run.

Research to Find out Where it Hurts and
What Can Be Done

Results of Meeting with Developers
Developers identify that a single unit test cycle takes more than 6 hours to
complete in its current state.
Developers identify that running the unit tests serially, in conjunction with
thousands of web service calls being made per cycle, adds significant time
to the length of the cycle.
Developers are concerned that as they add a few thousand more unit tests,
that unit testing will significantly impede their ability to release code at the
pace needed to meet deliverables.

Impact of Web Service Calls on Cycle
There are more than 25
web services being called
during unit tests.
Average response time of
web service calls is about
2 seconds.
There are over 3,000 unit
tests making an average of
5 web service calls per
tests. That is 15,000 web
service calls per cycle.
Total time spent on web
service calls is 30,000
seconds OR 8.3 Hours!

Implement a Plan to Alleviate the Pain

Proposed Plan
Virtualize all of
the web services and
set the think time to “0”,
making the average
response time less
than 50ms.
Run the unit
tests in parallel instead
of serially.
Developer(s)
would be assigned
to the creation/
maintenance of
the services.
1 2 3

Execute the Plan and Reap Your ROI

Execute the Plan
Developer spent 100 hours building 27 virtual services
(about 2 – 4 hours for each service)
Unit tests completed in under an hour (about 50 minutes).
Developer ran the unit tests in parallel against the dev environment
backed by virtual services.

Reap Your Service Virtualization ROI
Investment = 100 hrs
Savings = 7 hrs per cycle
ROI = 14.2 cycles (or, 15 cycles)
Given that the increase went
from one cycle a day to five
cycles a day, your ROI is
satisfied in 4 days!
If your sprint length is 2 weeks (or 10
days), you go from 10 code releases per
sprint to 50 code releases per sprint. That
is a 400% increase in the amount of code
releases in a sprint. This equates to
finding bugs sooner and fixing them
earlier in the project versus later, which
equals less expensive fixes.

Other Areas That Benefit From
Service Virtualization

Places That Benefit From Service Virtualization
Our mobile development team has taken advantage of using Service
Virtualization for virtualizing APIs using Swagger Docs,
before the APIs are even available.
Our training environments are backed by virtual services to reduce the cost and
maintenance of training environments
1
2
We have used service virtualization to create virtual ‘utilities’ used for creating
virtual service, assigning training IDs, and adding users to JIRA.
3

Recommended Sessions
SESSION # TITLE DATE/TIME
DO5T17S Nationwide Building Society's CA TDM Success Story 11/17/2016 at 01:45 pm
DO5T22S
ING Delivers Unprecedented Global Continuous Delivery
as a Service
11/17/2016 at 03:00 pm
DO5T19S
GM Financial Builds a Sustainable, Holistic, Continuous
Delivery Practice
11/17/2016 at 04:30 pm

Must See Demos
Modernize
App Delivery
Integrated CD
Theater 5 - DOV501P
Deliver Test
Data Faster
CA Test Data Manager
Theater 5 - DOV511P
Deliver
Better Apps
CA Service
Virtualization
Theater 5 - DOV507P
Orchestrate
Your Release
CA Release
Automation
Theater 5 - DOV513P

Stay connected at communities.ca.com
Thank you.

DevOps – Continuous Delivery
For more information on DevOps – Continuous Delivery, please
visit: http://cainc.to/PiTFpu

Case Study: American Family Insurance Leverages CA Service Virtualization to Accelerate Continuous Integration in Development

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

Similaire à Case Study: American Family Insurance Leverages CA Service Virtualization to Accelerate Continuous Integration in Development

Similaire à Case Study: American Family Insurance Leverages CA Service Virtualization to Accelerate Continuous Integration in Development (20)

Plus de CA Technologies

Plus de CA Technologies (20)

Dernier

Dernier (20)

Case Study: American Family Insurance Leverages CA Service Virtualization to Accelerate Continuous Integration in Development