GMF’s journey began last year at our parent company GM in the 4 quarter 2015. With the need to meet project demands for SSP, automation of IT activities became critical for all teams. We started from the beginning of the software development pipeline to improve application build and release. Come learn how we leveraged some open-source software for code build automation and how we were able to hook other enterprise software for automation to deploy applications quickly and consistently between environments. Using this software we were able to run over 10,000 deployments since the beginning of the year as well as integrate many of QA releases into our ticketing system for approvals and automated deployments. Not only did users quickly realize the stability of the application under test was more reliable; the savings produced by removing this dependency was significant enough to further expand these efforts into other environments. Though the initiative and collaboration from all IT parties involved, our groups were able to quickly and confidently meet the business needs. As we continue to grow as a financial corporation, we plan to continuously improve our IT processes through these enterprise software. SPEAKER BIO: Wesley Miller has more than 30+ years in IT, specifically in automation. Wesley is currently the AVP Quality Engineering at GM Financial for the last 2 years. Wesley Miller and his team in 2016 was the award recipient of the CA’s Continuous Delivery V.I.P. (Vision, Impact, Progress) Award for Progress.

1. GM Financial' s Service Virtualization Management and
Automated Testing Journey
Wesley Miller, AVP Quality Assurance
DO5X09S
DEVOPS

2. 2 © 2016 CA. ALL RIGHTS RESERVED.
© 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

3. 3 © 2016 CA. ALL RIGHTS RESERVED.
Abstract
Case Study: GM Financial' s Service Virtualization Management and Automated
Testing Journey
The CA engagement at GM Financial built an interface for a future application
allowing development and QA to test 6 months before the interface availability. The
engagement incorporated TDM as a future repository of loan parameters supplying
DevTest and SV necessary values for performance. The engagement also allows for
dynamic loan data generation coupled with virtual services that guarantees new
loan parameters. This story is how we are using automated testing to ensure
development builds utilizing CA Test Data Manager for data, CA Service
Virtualization to supplement 3rd party inquiries necessary to approve a loan or
trigger loan attributes for business rules validation.
Wesley Miller
GM Financial
AVP Quality Assurance

4. 4 © 2016 CA. ALL RIGHTS RESERVED.
Agenda
ABOUT GM FINANCIAL
SERVICE VIRTUALIZATION MANAGEMENT AND AUTOMATED TEST JOURNEY
QUESTIONS
IMPLEMENTATION
SUMMARY
1
2
3
4
5

5. 5 © 2016 CA. ALL RIGHTS RESERVED.
About GM Financial

6. 6 © 2016 CA. ALL RIGHTS RESERVED.
About Me
AUTOMATION EFFORTS
GM Financial for ~2
years leading
DevOps, Automation
& Agile Teams
Responsible for the automation tools &
technologies for Quality Assurance needs
to deliver customer satisfaction and
retention
Test harness technology framework that will
facilitate data demand requests coupled
with virtual services & test automation.
Author of
two books

7. 7 © 2016 CA. ALL RIGHTS RESERVED.
GM Financial’s Need for Data Management &
Automation for an Agile World
Rapid expansion for funded loans
led to noticeable gaps
 Knowledge gaps in new resources to fund
loans
 Inconsistencies in 3rd party environments
 Inability to meet new test data demands
More comprehensive test
data requirements
Agile project timelines
and new 3rd party
platform needs for
Virtualization

8. 8 © 2016 CA. ALL RIGHTS RESERVED.
Phases of Service Virtualization

9. 9 © 2016 CA. ALL RIGHTS RESERVED.
Phases of Implementing CA Service Virtualization
No automation in QA
and environment.
Single business
service virtualization
with CA DevTest from
development to test
- Setup & Config
- SV of 1 Service
- TDM feeds SV
Collaborating and
integration
applications within
release pipeline
Pre-CA SV/TDM
Automation
Proof of
Concept
SV/TDM
Integration
Continuous
Updates

10. 10 © 2016 CA. ALL RIGHTS RESERVED.
Phase Implementation Timeline
TITLE
OCT
2015
NOV
2015
DEC
2015
JAN
2016
FEB
2016
MAR
2016
APR
2016
MAY
2016
JUN
2016
JUL
2016
AUG
2016
SEPT
2016
OCT
2016
NOV
2016
DEC
2016
Pre-CA SV/TDM
Automation
Proof of
Concept
SV/TDM
Integration
Continuous
Updates
No Automation in Most Environments
Service Virtualization
Phase 1 (CA)
Continuous Service Updates
Phase 2 (CA)
Phase 3 (GMF)

11. 11 © 2016 CA. ALL RIGHTS RESERVED.
Implementation

12. 12 © 2016 CA. ALL RIGHTS RESERVED.
Current System Architecture Overview
Transformation
Engine
Dealer Portal
Credit Platform
Credit Bureaus
Fraud
Funding Platform
Dealers
Vendors
Business Bridge
GM Financial
Payment Gateway
Banks

13. 13 © 2016 CA. ALL RIGHTS RESERVED.
Current System Architecture Overview
Transformation
Engine
Dealer Portal
HTTP/SOAP
Credit Platform
Credit Bureaus
Fraud
Funding Platform
Dealers
Vendors
DB
Business Bridge
GM Financial
Payment Gateway
Banks
Virtual Credit Bureaus
Decision Engine
Virtual
Credit Data
Payments
File
Contract
Files
Funding
File
Deals from Dealers
Portals
TDM
DevTest
DevTestVirtual Business Platform

14. 14 © 2016 CA. ALL RIGHTS RESERVED.
GM Financial’s Automated SDLC
Design
Dev designs
Business code
request
Build/Scan Test
CA Service Virtualization
Perfecto
Deploy
CA Release Automation
Business
Request
Application
Servers
Developer
submits request
for code package
to move to QA
Customer gets
Product
Project is
completed
Deploying
DEV/QA/TRN/PRD
Testing QA
Tickets
send
to QA
Moving
to release
automation
Code Checked into TFS

15. 15 © 2016 CA. ALL RIGHTS RESERVED.
Summary

16. 16 © 2016 CA. ALL RIGHTS RESERVED.
Outcome of
Automation
As we increased stability in our
environments our team was
given more resources to
continue development efforts
in CA Release Automation
allowing us to update and
optimize our deployment
processes.
Phasing Automation
Phasing in automation helped
our team evaluate CA Release
Automation in our environment
and determine best practices
for long-term use.
Benefits with
Automation
Using CA Release Automation
has helped improve software
development stability by
creating repeatable processes
to minimize inconstancies and
show visibility into the
deployment pipeline.
Summary
Using Release Automation’s shared component feature allows for repeatable processes
in software development.

17. @CAWORLD #CAWORLD © 2016 CA. All RIGHTS RESERVED.17 @CAWORLD #CAWORLD © 2016 CA. All RIGHTS RESERVED.17
Pathology of IT