Enterprise Quality Roadmap

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 1. 2. 3. 4. Enterprise Quality Vision Strategy Jenkins Demo Questions

Why Enterprise Quality? 100 Applications 10 App Dev teams 994 deployments in 2016 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 1. People / Roles 2. Process 3. Tools

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

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

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

Communication Dev Lead Dev Meeting Developer Blog SharePoint Email Distribution(@develop ers) DUG QA Weekly QA Meeting Developer Blog QA Website QA SharePoint Email distribution: @Developers, @ QA Engineers All

Learning 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 J e n k i n s UI Telerik Integration FitNesse Postman jMeter Fortify Security Unit NUnit Jasmine/Karma FakeItEasy Ncrunch, Wallaby

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 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 !!!