Now more than ever, engineering teams of all sizes are under pressure to deliver quality code more frequently. With the DevOps ecosystem growing larger every day, it might seem overwhelming to fully understand how to create an end-to-end solution that allows developers to continually commit new code with confidence, without having to slow down due to rollbacks. Achieving this true Continuous Deployment pipeline is difficult, but not impossible. Join Neil Manvar, Solutions Architect from Sauce Labs, as he demonstrates a full CD pipeline containing a Pull Request build which will be used to test changes in isolation before code is merged into the master codebase. Using a JS based code tech stack, with AngularJS for the source code, Karma/Jasmine for unit tests and Protractor for functional (Selenium) tests, he will safely push quality code to production leveraging the following tools: - Jenkins for CI / orchestration - Github for Source Code Management - Docker for creating/deploying container running the application - Sauce Labs for running tests in various browser/OS combinations By running through all of the various steps involved in deploying code changes safely and automatically to production, Neil will discuss the ways in which the PR Build creates a real time developer feedback and enforcement mechanism, thus eliminating bottlenecks. He will also discuss the implementation strategies, as well as challenges, along with results and culture changes that come with truly embracing DevOps methodologies.

1. Building a CD Pipeline with Testing in
Mind
Neil Manvar, Solutions Architect

2. • Solutions Architect
• Front End Software Engineer @ Yahoo
• Bachelors in CSE @ UC Davis
About Neil
Neil Manvar
neil@saucelabs.com

3. • The Importance of Testing
• The Need to Test in Isolation
• Demo: How to Test in Isolation
• Tips on How to Get Started
Agenda

4. CD Pipeline Without Testing In Mind?

5. CD Pipeline Without Testing…

6. CD Pipeline With Inverted Testing Pyramid
Functional
Testing
API Testing
Unit Testing
Functional Testing
API Testing
Unit
Testing

7. Flaky Tests…?

8. Need: Isolated, Developer Feedback

9. Testing In Isolation – A Pull Request Build
Keep the codebase and pipeline pristine
PR Build
(UT and Func Tests)
QA Build
(UT and Func
Tests)
PR
PR
Kick off build
against PR
branch
Safe to merge?
Only review and merge
if marked as safe
PR Build

10. Demo
Testing in Isolation + Continuous Deployment

11. Example Pipeline
CD Pipeline
PR Build
QA Build Pilot Staging Prod
PR
PR Build
PR
1
2
3

12. • Deploy on the fly
– “Production-like” environment
• A + A tests
– Atomic
– Autonomous
• Enforcement mechanisms
– Code Coverage
• CI (scaling)
Requirements For Testing In Isolation

13. Enforce, Not Police

14. Questions?
neil@saucelabs.com