Making the leap to continuous delivery is precarious for any organization, but the concerns are greatly exacerbated when your organization services approximately 45 million bank accounts. Committed to maintaining flawless user experiences while accelerating release cadence, Capital One faced a daunting challenge as it transformed culture, processes, and technical infrastructure in its evolution to continuous delivery. Join this session with Capital One's Michael Bonamassa and Parasoft's Wayne Airole and learn from their insights on what DevTest changes are critical for responding to extreme digital disruption. Key takeaways: o The changing responsibilities of DevTest in a "continuous everything" world o What skill sets software testers need to ride the wave of digital transformation o How service virtualization and continuous testing measure the risk of a release candidate o How to evolve the culture and process to support continuous delivery o What technical infrastructure is required for real-time test automation and continuous delivery maturation For more information, go to: www.appdynamics.com

1. How Capital One transformed DevTest
or continuous delivery
With Capital One and Parasoft
Michael Bonamassa
Director | Capital One
Mark Lambert
Parasoft

2. Parasoft Proprietary and Confidential 2Parasoft Proprietary and Confidential 2
Increased delivery requires accelerated testing
Adoption of Agile for
SDLC Speed; the
difference between a
first mover and a
follower
Damages associated with
software failure are
increasing and very real
Defects impact Brand
Quality and Regulatory
Compliance (e.g. Safety
Critical)
&

3. Parasoft Proprietary and Confidential 3Parasoft Proprietary and Confidential 3
Agile = “I don’t have time to test EVERYTHING”
2-4 weeks
Can’t Test Everything!?!

4. Parasoft Proprietary and Confidential 4Parasoft Proprietary and Confidential 4
An application is not just “one application” …

5. Parasoft Proprietary and Confidential 5Parasoft Proprietary and Confidential 5
… it’s made up of „several components” …

6. Parasoft Proprietary and Confidential 6Parasoft Proprietary and Confidential 6
How to test without dependent components?
API
testing

7. Parasoft Proprietary and Confidential 7Parasoft Proprietary and Confidential 7
How to test without dependent components?
API
testing
Reusable
Virtual
Assets

8. Parasoft Proprietary and Confidential 8Parasoft Proprietary and Confidential 8
Test as soon as the components are ready

9. Parasoft Proprietary and Confidential 9Parasoft Proprietary and Confidential 9
How Do We Increase Testing Scope and Frequency?
Today, complexity of networked applications, including the array of different APIs
and system dependencies, renders the “more hardware” approach obsolete
HTTP
JMS
SOAP
REST
RSSCICS
MQ
SAP
EDI
JSON
In the past, more hardware and more test lab capacity was the only answer

10. Parasoft Proprietary and Confidential 10Parasoft Proprietary and Confidential 10
Service Virtualization Solves the Problem
“Service Virtualization” creates simulated test
environments that are 100% complete and accurate
Application testing can happen any time
and anywhere without adding additional
test environment hardware
Mainframe transactions
Databases calls
Message Queues and ESBs
API Interactions

11. Parasoft Proprietary and Confidential 11Parasoft Proprietary and Confidential 11
Using Service Virtualization to Accelerate Agile
1. Turning Automated Testing into Continuous Testing
 Remove test environment dependencies to enable complete
automated validation as part of Continuous processes
2. Decoupling parallel development streams
 Eliminate intra-team roadblocks and deliver on schedule
3. Shift-left Performance Testing
 Emulate extremes in production SLAs to expose risks early in the SDLC

12. Parasoft Proprietary and Confidential 12Parasoft Proprietary and Confidential 12
 The Challenge
 Performance issues found late in the SDLC resulting in large rework and cost
 Middleware component able to handle large load but available downstream
dependent systems were unable to provide throughput needed
Reduced testing time by 27-days using shift-left
Performance Testing
Capacity Constrained staged environments
Database
Service
Mainframe
Application
1000 tps

13. Parasoft Proprietary and Confidential 13Parasoft Proprietary and Confidential 13
Database
Service
Mainframe
Application
Reduced testing time by 27-days using shift-left
Performance Testing
 The Solution
 Identified key use-cases and emulate the behavior of dependent systems.
Interrogate APM to configure asset performance to match production load
response values
 Parasoft SOAtest and LoadTest used to validate system under test. Virtual assets
changed to model different scenarios
Capacity Constrained staged environments
1000 tps
Virtual
Asset
Virtual
Asset
Virtual
Asset
Virtual
Asset

14. Parasoft Proprietary and Confidential 14Parasoft Proprietary and Confidential 14
Reduced testing time by 27-days using shift-left
Performance Testing
 The Business Benefit
 Team able to predict performances issues and resolve before full Performance
testing.
 Able to run different scenarios not easily achieved with production
environment (excessive response times).
 Setup for ‘performance test’ reduced to near zero
Capacity Constrained staged environments
1000 tps
Virtual
Asset
Virtual
Asset
Virtual
Asset
Virtual
Asset
Virtual
Asset
Virtual
Asset
Virtual
Asset
Virtual
Asset
Virtual
Asset
Virtual
Asset
Virtual
Asset
Virtual
Asset
Different
data/behavior/
performance
profiles

15. How Capital One is Shifting Left DevTest so
that Applications are Engineered to Perform

16. 16
About Me
Director of Technology at Capital One
• Tweet me @mbonamassa | Michael.Bonamassa@capitalone.com
Responsible for Capital One’s Performance EngineeringTeams, which include:
• Performance Testing Core Technology
• Performance Analysis
• Performance Simulation
• Feature Team Performance Enablement
• Performance Engineering Strategy & Consulting
Before joining Capital One in 2014 Mr. Bonamassa has worked with other
Financial and Technology companies, in various leadership positions, with a
focus on Product Development, General Management and Agile practices.

17. 17
Our view of Continuous Delivery

18. 18
Performance Analysis Establish the Baseline and Insights
Production Environment
(On Premise, Cloud, Hybrid)
AppDynamics APM Parasoft Virtualize
Analysis

19. 19
Our Baseline Provides the Blueprint for Simulation and Validation
MRE Non-Production Environments
(On Premise, Cloud, Hybrid)
AppDynamics APMParasoft Virtualize
Hercules
Simulation, Validation
& Testing

20. 20
We are embedding Specialization Knowledge into technologies that enable full
stack software engineers to perform with specialist skills
Robotic
Process
Automation
Cognitive
Automation
Robotic
Social
Automation

21. 21
What does this mean for me?
Developer
• Accountable for writing
“automatable” code
• Responsible for passing tests
(all tests)
• Become fungible in all aspects
of testing
Tester
• Must learn a programing
language
• Understand how to use CI
tools
• Be able to apply enablers
based on current constraints
Everyone
• Work in Pairs or at least communicate like a pair.
• Take accountability for “Done” being working code and passing tests
• No more “throwing it over the fence”

22. Please give us your feedback—Session B7791
• Complete the online survey you'll receive via
email later today or via text at:
Text this number: 878787
Text this word: APPSPHERE
• Every time you submit a session survey, your
name will be entered in a random drawing.
We're giving away Amazon Echos
to 5 lucky winners!
• Thank you for your input
APPDYNAMICS CONFIDENTIAL AND PROPRIETARY 22
Win!

23. Thank you