Enterprise Quality Roadmap

Farm Credit Services of America, based in Omaha, Nebraska, is dedicated to serving the agricultural credit, risk management and financial needs of farmers and ranchers in Iowa, Nebraska, South Dakota and Wyoming. https://www.fcsamerica.com/ www.farmcredit.com

Agenda Enterprise Quality Vision Strategy Jenkins Demo Questions

Why Enterprise Quality? 100+ Applications 994 deployments in 2016 10 App Dev teams 805 deployments in 2017

Why Enterprise Quality?

My Role As an EA my primary focus is to bring visibility and consistency to our process

Strategy People / Roles Process Tools Provide leadership and help bring focus and Visibility B2B Strategy: Basement living to Balcony Quality has been an after thought, treat as a first class citizen

1. QAE (job description)

1. Mindset Let developers test and verify their own code Let product/business owners test and validate the product Quality experts who understand software testing as well as everything else that goes into producing and delivering quality software

2. Process Are you collaborating with your QA? Is Quality efforts discussed as part of your Project planning? Continuous Integration (CI) is a development practice that requires developers to integrate code into a shared repository several times a day. Each check-in is then verified by an automated build, allowing teams to detect problems early. Continuous Delivery is a software development discipline where you build software in such a way that the software can be released to production at any time. http://martinfowler.com/bliki/ContinuousDelivery.html

2. Process Automation is our new bacon Continuous Delivery with Smarter Testing

Dev VSTS Visual Studio GIT Common lib Project Repo Source Control Use version control as the single source of truth for Automation Scripts. Dev VSTS Visual Studio GIT Common lib Project Repo QA GIT (sourcetree) QA Repo

Communication Dev Lead Dev Meeting Developer Blog SharePoint Email Distribution(@developers) DUG QA Weekly QA Meeting QA Website QA SharePoint Email distribution: @Developers, @ QA_Engineers_All

Learning QA On-Site training QA Pairing Working meetings Book club Dev Onsite-Training Dev Pairing Plural Sight Website/Blogs Tech Conferences DUG .NET user group QA On-Site training QA Pairing Working meetings Book club DUG(Jenkins)

3. Tools Jenkins Integration Unit UI Telerik FitNesse Postman jMeter Fortify Security Unit NUnit Jasmine/Karma FakeItEasy Ncrunch, Wallaby Jenkins

Jenkins CI Server Why Jenkins? Flexibility ! Jenkins is a highly configurable system by itself. Single Platform Automate the build and test Get Source code from repository Dashboard - everyone can see what’s happening Generate report and notify stakeholders of build status Plug-in extensibility: Unit test coverage, last success and failure, Build trend.

Jenkin’s Demo Main Page Project Status

QA Infrastructure

QA Image Target Install Common Software QA Group Policies Telerik Runtime/ Chrome Plugin Postman(Node/Newman) jMeter NUnit Common Software GIT Jenkins Beyond Compare Notepad++ QA Group Policies TesterM AutoLogin, Disable Screen Lock, UAC Browser Settings, Screen Resolution Base Win 10 FCSA Image Includes (Java, Nuance PDF)

Summary The problem: There was no unified approach in our Quality Practices(tooling and process) across our 10 AppDev teams. We were good at Continuous Integration but inefficient at Continuous Delivery. Solution: - Implemented the Testing Pyramid Strategy - Testing Architecture using Jenkins(Test Farm, Tool Standardization) - Increased collaboration and communication between QA and Devs. Impact: Any friction leads to lower adoption rate. We were able to automate 2300 tests suites per day from 400 per day. Increased our expertize by standardizing the toolset and collaboration across teams. Our confidence is delivering software in increasing everyday.

#teamwork

What’s next ? Enterprise Health Test Data Testing Community

Never Stop Testing… Thank you !!!