TechWell Accelerating Software Delivery with Continuous Integration feat. Dan Boutin

August 26, 2015

“Accelerate Software Delivery with Continuous Integration”Dan Boutin – Senior Product Evangelist

[email protected] (404) 304-9529@DanBoutinSOASTA

mailto:[email protected]

© 2014 SOASTA. All rights reserved. 2

In This Discussion Today

Agenda: • SOASTA Introduction• The need for “Continuous”• The “Big 3”• CI with mobile and performance testing


SOASTA – Performance Analytics

100 BillionUser Experiences Tested

10 MillionTests Performed

Actual CloudTest view





CI Offers Speed of DeliveryWhat’s not to like?


CI Offers Speed of Delivery

o Small Batch Sizes

What’s not to like?



o Small Batch Sizeso Comprehensive Version Control




o Small Batch Sizeso Comprehensive Version Controlo Simple Branch Strategies




o Small Batch Sizeso Comprehensive Version Controlo Simple Branch Strategieso Automation




o Small Batch Sizeso Comprehensive Version Controlo Simple Branch Strategieso Automation o Continuous Feedback




o Small Batch Sizeso Comprehensive Version Controlo Simple Branch Strategieso Automation o Continuous Feedbacko Emphasis on working builds




o Small Batch Sizeso Comprehensive Version Controlo Simple Branch Strategieso Automation o Continuous Feedbacko Emphasis on working buildso Consistent environments




o Small Batch Sizeso Comprehensive Version Controlo Simple Branch Strategieso Automation o Continuous Feedbacko Emphasis on working buildso Consistent environmentso Developer – Tester Collaboration






What’s Been Missing?


So, let’s break down DevOps – What is it, really?o It’s not what’s within the siloso It’s about the relationships

A typical silo’d organization lacks end-to-end integration

Performance Engineering & Continuous Integration-Full Lifecycle

Operational Configuration

Continuous Integration touchpoints

ADLC QA/Test Pre-Production

Production

QA/Test Environment

Operational Production

Environment

Application Development Environment

Development Test

Configuration management

Release management

Change management

Performance management

CI Focus Areas – The assembly line Hand-offs

Key Processes


Software is simple: It’s Manufacturing & BOMo Bill of Materials (BOM!)o The “Big 3” => Change, Configuration & Release

• That is your software assembly line conveyor belt


So, what?

• We can only test as fast as the conveyor belt allows.

• If the conveyor belt is moving slow, testing is delayed.

• The Big 3 drives testing cycle.

o Why is CI critical?• Speed

• New features, functions, etc. need to get to the customer, ASAP!


So, let’s break that down…o CI is a key component of Performance Engineeringo Performance Engineering spans the silos

BIG 3

Testing

ApplicationDevelopment Life Cycle

ITOperations

CapacityManagement

PerformanceManagement

PerformanceEngineering


Laying the FoundationA factory streamlines for quality and speed

Does it work as designed?

Does it perform under

extreme circumstance

s?

Approve materials

Real Drivers

What happens in actual conditions?

Assembly Line


Laying the FoundationCI streamlines for continuous quality

Functional validation

Performance,reliability,scalability tests

Real Users

Build

What happens in actual conditions?

Unit-tested code





Continuous QualitySOASTA’s Lifecycle


Continuous QualitySOASTA’s LifeCycle

I JUST MADE A CODE CHANGE

Jenkins runs any unit tests as usual



Run iterative load tests via Jenkins

Spin up suitable, consistent test environments in the

cloud or the lab






Mobile? Run functional automation on real devices for functional & performance validation


cloud or the lab






Daily (or more frequent) updates keep teams quality focused

Embedded failure details & bottleneck data isolate issues



cloud or the lab








Manage to a performance

baseline



cloud or the lab





Use real user data toiterate dev & test plans




Manage to a performance

baseline



cloud or the lab



SOASTA – Branch Build from CloudTest

SOASTA – Test Results

SOASTA – Drill Down (Test Failures)

SOASTA – UI Testing Bundle Results

SOASTA – UI Testing Failure Drill down into SOASTA CloudTest from Jenkins

SOASTA – Successful regression test results

SOASTA – Release Promotion


Continuous Quality for Continuous Delivery

o SOASTA’s Process Metrics• 3 Main Products

• (2) Builds per day of each product (Dev branch + Customer branch)• 8,000 tests executed per build• For Mobile (TouchTest), Over 300 fully-automated tests each for iOS &

Android

SOASTA - Takeaways


The Path to Continuous Testing

o Understand your requirements

o Identify the cloud advantages for you

o Automate the obvious and most critical

o Connect to a continuous process

o Align teams with actionable information

SOASTA - Takeaways








SOASTA - Takeaways








SOASTA - Takeaways








SOASTA - Takeaways








SOASTA - Takeaways


CONFIDENTIAL – Not for Distribution

Final TakeawayWhy is CI important?

RevenueBrandCompetitive advantage


We will close with some Mobile Trivia

@DanBoutinSOASTA


Questions?

Dan Boutin – Senior Product [email protected]

Mobile (404) 304-9529@DanBoutinSOASTA

Visit our Blog: http://goo.gl/TA2HKP

Questions? @DanBoutinSOASTA


http://goo.gl/TA2HKP

August 26, 2015

“Accelerate Software Delivery with Continuous Integration”Dan Boutin – Senior Product Evangelist

[email protected] (404) 304-9529@DanBoutinSOASTA


Technology

TechWell Accelerating Software Delivery with Continuous Integration feat. Dan Boutin