A story of real implementation of Shift Left
This is a real story of how we implemented Shift Left by influencing, mindset change, creating champions and with the help of technology at Expedia Group.
In every software company in the world, at the nucleus of it, all we are trying to do is, take a code change and move it to production, faster with quality. There couldn't be any disagreement over this!
Sometimes when we repeatedly follow a practice, even when there are new better alternatives, it is difficult to change our mindset because we think "Why change? it is working". Moving your pipelines to follow Shift Left is one of them.
In US alone, $113B is spent annually on identifying and fixing production defects!
Shift Left not only increases developer productivity, but allows you to go to production faster, more frequently and reduce production incidents. End of the day, it makes both developers and customers happy!
The biggest frustrations for developers in a team is, CI/CD pipeline being blocked and no one can merge their PR, everyone has to wait for it to be fixed and pipeline becomes green again. And as all the validation and verifications happening to the right side of the pipeline, it is going to take more time to fix issues as well, involving many engineers, because the failure could have been caused by any code change. This is true, especially when an issue happens in production, not only everyone has to be involved to figure out the problem, but there is going to be lot of unhappy customers and loss of revenue.
What if you have something where pipeline blockage is not possible. What if you can can run the same set of checks you run in main pipeline but you run them against your branch itself and when you merge your PR, it is already 'production ready', what if every PR can go to production directly? what if you have a mechanism where it actually reduces production incidents ?
Welcome to Shift Left!
Outline/Structure of the Case Study
Presentation : 35mins
Key ingredient of CICD Pipeline (2mins)
Problem Definition (7mins)
Why Shift Left
Regular Pipeline
Problems
How a developer cycle looks like?
5 different teams' PR stats for 1 year
Shift Left Pipeline Big Picture (3mins)
Advantages (12mins)
Key Stats
Implementation Details
How to implement Shift Left?
Container Orchestration Platforms
Github Actions / Jenkins
Github Actions work flow
Micro-services and Shift Left (2min)
Return on Investment (3min)
Productivity
Reduction in Revenue Loss
How to cost optimise Shift Left? (2min)
Canary vs Shift Left (1min)
Best Practices (3min)
Q &A = 10mins
Learning Outcome
Whether you know this concept or not, after this presentation, you will have a clear idea on not just how to implement Shift Left, but how to make the mindset change within a team by creating change agent champions and successfully implement it.
Target Audience
Everyone in a software engineering team
Prerequisites for Attendees
Understand general CI/CD pipeline
Video
Links
Dan's Blog on Shift Left - - Jan 2022 - https://medium.com/expedia-group-tech/shifting-left-empowering-teams-with-faster-feedback-aa3fd67c7af8
https://youtu.be/iax0UHD0bcA - 2021 BrowserStack Breakpoint - Shift Left - How to create ‘Production-ready’ changes
https://www.youtube.com/watch?v=qi7id81RanY - 2021 Appium Conference (Online) - Cross browser and device platforms are ripe for disruption
https://www.youtube.com/watch?v=MmdGyqNqs9w - 2019 Selenium Camp, Kyiv (Distributed Automation using Kubernetes, Docker, Traefik)
https://www.youtube.com/watch?v=cbIfU1fvGeo - 2015, Selenium Conference, Oregon. (Distributed Automation Using Selenium Grid / AWS)
schedule Submitted 10 months ago
People who liked this proposal, also liked:
-
keyboard_arrow_down
Robin Gupta - TestZeus: Open source UI automation framework built specifically for Salesforce with Auto-locators
45 Mins
Demonstration
Beginner
Automation for Salesforce is tough (no , seriously). And every platform release brings the lightning and thunder for UI Automation tests (Winter21 caused even our tests to shiver). So we present TestZeus to end this madness and create a simple (and robust) Open source framework for Salesforce Test Automation. And solve the problem of flaky tests, while accelerating the development of automation .
-
keyboard_arrow_down
Eran Kinsbruner - Comparing Selenium 4, Cypress and Playwright Frameworks
45 Mins
Talk
Intermediate
As the cross-browser testing landscape evolves, there is a stabilization around 3 main leading frameworks that are used the most. Some are more adopted by frontend developers, while some are adopted by SDETs. To better make a selection or even choose more than a single framework you need to realize the core differences and use cases as well as benefits each framework provides to the practitioner.
In this session, Eran Kinsbruner, Chief DevOps evangelist, best-selling author from Perforce (Perfecto and Blazemeter specifically) will go through the core differences and advantages of all 3 frameworks with focus on Selenium 4 vs. the latest versions of Cypress and Playwright and provide a nice outline to better guide test automation engineers as they look for their next test framework.
-
keyboard_arrow_down
Parasar Saha - Cloud First Automation Approach – Road to Scalable and Faster Test Automation Pipelines
45 Mins
Talk
Advanced
Cloud has changed the way the software world works. Companies have accelerated their development and deployment cycles with 3x or more speed by adopting the cloud. But Testing in most organizations either is running locally or not taking advantage of the full potential of cloud infrastructure. Testing is the home-alone kid, left to spend the Christmas weekend without the bells the whistles that cloud has to offer.
Digital transformation in IT and Agile delivery model are pushing the testing teams to complete their testing in shorter testing windows. 26 % of the organization are moving to daily releases. 70% of the organization have adopted Agile in delivery. Even after having a high amount of automation coverage teams are struggling to keep up with the pace of testing asked by the business teams.
This talk is about how you can change the story and accelerate cloud adoption in your testing organization with Selenium-based frameworks. Through cloud adoption you benefit from box features of the cloud: On-demand scaling, Cost optimation, Security, Reliability, Geo -routing of your test infrastructure. Cloud adoption doesn’t need to limit to the execution of selenium tests but can help you in test management of automated selenium tests, test data generation, test reporting, test artifact store, and many more. It is not enough to have an Automation First Approach these days, you also need to have Cloud-First Approach for test infrastructure to get the best value from automation.
The talk elaborates on factors to consider while building up the cloud-based testing pipeline and how they will benefit your organization in terms of time to market, cost optimization, and raising the bar of quality.
Finally talks about the moonshot of having a Testing Cloud – AWS of Testing and what will it take to reach there as a testing community.
Take your testing to the cloud, and fly your flag high in quality!
-
keyboard_arrow_down
Divya Cheekati / Kavitha Bellam Konda - RPA using Power Automate Desktop Tool >> Changed our Automation Perspective from Complex code to Simple flows
Divya CheekatiQA Lead EngineerS&P GlobalKavitha Bellam KondaLead QA EngineerS&P Globalschedule 9 months ago
20 Mins
Case Study
Beginner
Spreadsheets have a dominant way of managing multiple business processes.
Validating these spreadsheets data points manually is very hectic and automating them needs knowledge on scripting. Also automating spread sheet actions like handling excel popups ,clicking macro buttons etc., will require more efforts.
RPA Power Automate for desktop provides an extensive variety of Microsoft Excel Spreadsheet actions to help you read and manipulate Excel files. With this RPA ,we handled spreadsheet actions using simple flows with out complex scripts. Simple drag and drop flows changed our view from the usual mind juggling of code/scripting concepts to simple business actions. This indeed saved lot of time and efforts.