After the grant success of the C-level event "I/O: Intelligent Outsourcing", Bridge Global is conducting a free webinar under BEAM (Bridge Events And Meets) on September 6th, 2017. We designed this webinar as a must-attend event for those who are looking for a kick-start moment to lead their organization into the DevOps environment. It attracted several attendees from all parts of the world. They all sat back and learned valuable insights on DevOps culture and practices. People are tired of hearing the countless amount of suggestions and opinions while contemplating to start their DevOps journey. This webinar helped its attendees in getting rid of all kinds of apprehensions related to the topic. Topics Covered DevOps vs. Traditional Approach. Addressing the Delivery Challenges. Why Continuous Integration and Continuous Delivery is so relevant? DevOps vs Release Management. Best Practices.

1. September 25, 2015
Introduction to QASymphony
for [INSERT COMPANY NAME]
# Continues testing in AGILE
The audio for this webinar is delivered through your computer. There is no dial-in
number. Make sure your speakers are turned up or use a pair of headphones.
Don’t Forget About Testing
PRACTICAL DEVOPS
&
Continuous Delivery
#LetsTalkDevOps |
#BridgeEvents

2. AGENDA
TABLE
OF
CONTENTS
The DevOps Story1
Agile/DevOps & Testing2
Continuous Testing, Integration and Delivery3
Tools and Techniques4
Role Transitions on Demand5
#LetsTalkDevOps |
#BridgeEvents

3. DevOps – What we hear?
#LetsTalkDevOps |
#BridgeEvents

4. What is DevOps ?
#LetsTalkDevOps |
#BridgeEvents

5. DevOps – What we hear?
“It’s Development and
Operations collaboration”
“It means faster and
smaller releases”
“It’s automation”
“It’s a job title”
#LetsTalkDevOps |
#BridgeEvents

6. DevOps ?
• It’s Not (Just) Tools
• It’s Not (Just) Culture
• It’s Not (Just) Devs and Ops
• It’s Not (Just) A Job Title
• It’s Not Everything
#LetsTalkDevOps |
#BridgeEvents

7. What is DevOps ?
DevOps
Tools
Process
People
#LetsTalkDevOps |
#BridgeEvents

8. DevOps ?
“DevOps is a culture, not a role! The whole company needs to be doing DevOps
for it to work” Mike Dilworth
#LetsTalkDevOps
BridgeEvents

9. History of DevOps ?
Patrick Debois and Andrew Shcafer presented paper in Agile Conference,
Canada in 2008. They talked about applicability of Agile Principles in
Infrastructure.
John Allspaw and Paul Hammond gave the seminal “10 deploys per Day:
Dev and Ops cooperation at Flickr during Velocity conference in 2009
Patrick Debois got inspired by above idea and created the first
DevOpsDays in Ghent, Belgium in 2009.
There the term “DevOps” was coined.
#LetsTalkDevOps
BridgeEvents

10. Who is doing DevOps ?
Web Pioneers
• Amazon
• Netflix
• Etsy
• Facebook
• Google
• Twitter
• Pinterest
Academia
• Portland State University
• Seton Hill University
• Kansas State University
Financial Institutions
• BNY Mellon
• Bank of America
• World Bank
Retailers
• Target
• The Gap
• Nordstrom
• REI
• Macy’s
Insurance companies
• Nationwide
• Travelers
#LetsTalkDevOps
BridgeEvents

11. Yesterdays practices may not meet today’s demand.
Why DevOps ?
Source: https://puppet.com/resources/whitepaper/2016-state-of-devops-report #LetsTalkDevOps
BridgeEvents

12. End to End Responsibility
#LetsTalkDevOps
BridgeEvents

13. What DevOps is Not / Common Myths
DevOps is all about tools
DevOps involves only Development and Operations
There is only “One Way” to do DevOps
DevOps is about reducing the staff by half
DevOps is 100% end to end Automation
DevOps only works well with Startups
#LetsTalkDevOps
BridgeEvents

14. Agile & DevOps
Agile differs from Waterfall in creating shorter, more integrated cycles that generate code more quickly,
allowing teams to react to changes as they come and reduce risk and waste
Source: http://www.kenwayconsulting.com/wp-content/uploads/2012/03/Agile-v-Waterfall.jpg
#LetsTalkDevOps
BridgeEvents

15. Agile & DevOps
#LetsTalkDevOps
BridgeEvents

16. WHAT IT MEANS FOR QUALITY?
Agile/DevOps means more frequent development cycles,
often with more regular code delivery.
What does this mean for quality?
1. Testers must be involved and aligned with the entire development process.
2. Testing will happen much more regularly, in smaller increments.
3. Testing will follow development more closely, in tandem with coding
#LetsTalkDevOps
BridgeEvents

17. HOW TO OPTIMIZE TESTING FOR AGILE
Get Testers Involved Early
Embed testers within product or scrum teams, making sure they have a seat at the table in
planning discussions and provide insights around quality and testing considerations
Embrace Frequent, if not Continuous, Testing
As agile promotes frequent code merges, builds, and deployments, employ a process that allows
the most vital testing to be identified and executed efficiently
Decrease the Time from Design to Test
With 2-3 agile sprints, we do not have weeks (or even days) to define and automate test cases,
adopt a process for manual or automated tests that allows tests to closely follow designs
#LetsTalkDevOps
BridgeEvents

18. Thank YouWHY CONTINUOUS
TESTING?
WHY CONTINUOUS
TESTING?
#LetsTalkDevOps
BridgeEvents

19. Use Continuous Testing…
 To control side effects
 To avoid software defect snowball
 To efficiently support multiple platforms, environments and
release versions
 To get fast results in a short time cycle
 To anticipate risks
 To create an agile, reliable and repeatable process
 Release in hours not months
#LetsTalkDevOps
BridgeEvents

20. Continuous Quality Improvement
#LetsTalkDevOps
BridgeEvents

21. Thank YouWHY CONTINUOUS
TESTING?
CONTINUOUS
INTEGRATION
#LetsTalkDevOps
BridgeEvents

22. What is CI
“In short, it is an integration of code into a known or working code base”
“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.”
#LetsTalkDevOps
BridgeEvents

23. CI Workflow
#LetsTalkDevOps
BridgeEvents

24. How It Works?
• Developers check out code into their private workspaces.
• When done, the commit changes to the repository.
• The CI server monitors the repository and checks out changes when they occur.
• The CI server builds the system and runs unit and integration tests.
• The CI server informs the team of the successful build.
• If the build or tests fail, the CI server alerts the team.
• The team fix the issue at the earliest opportunity.
• Continue to continually integrate and test throughout the project.
#LetsTalkDevOps
BridgeEvents

25. Thank YouWHY CONTINUOUS
TESTING?
CONTINUOUS
DELIVERY
#LetsTalkDevOps
BridgeEvents

26. A NEW BREED OF TOOLS
Take 1 of 2
#LetsTalkDevOps
BridgeEvents

27. A NEW BREED OF TOOLS
Take 2 of 2
Continuous Deployment
Continuous Delivery
 Essentially, it is the practice of releasing every good build to users
While continuous deployment implies continuous delivery the converse is not true
 Implementing continuous delivery means making sure your software is
always production ready throughout its entire lifecycle - that any build
could potentially be released to users at the touch of a button using a fully
automated process in a matter of seconds or minutes.
 What makes continuous deployment special is deploying every change
that passes the automated tests to production
 Continuous deployment is the next step of continuous delivery. (Source: puppet)
#LetsTalkDevOps
BridgeEvents

28. Thank YouWHY CONTINUOUS
TESTING?
TOOLS
#LetsTalkDevOps
BridgeEvents

29. A NEW BREED OF TOOLS
Automation is undergoing even more dramatic changes than
manual testing, with a new breed to tools:
● Open source: to provide lower cost and allow more
members to contribute automation
● Cross Platform: to accommodate for multi channel
experience across web, mobile, & desktop
● DevOps Capable: reliable, with ability to be run quickly
and in parallel to allow for fast, frequent builds
#LetsTalkDevOps
BridgeEvents

30. OPEN SOURCE AUTOMATION
Every category of automation tool is undergoing pressure
from open source options:
Unit Testing
● jUnit
● nUnit/xUnit
UI Testing
● Selenium
● Protractor
Load/Performance
● jMeter
● Gatling
CI / Build
● Jenkins
● Travis
Orchestration
● Puppet
● Chef
Configuration
Management
● Docker
● Selenium Grid
#LetsTalkDevOps
BridgeEvents

31. Early Automation Approach
Write Acceptance Test
Cases
Decision to
Automate
Test
Define Acceptance Test Criteria
Yes
Prototype Rinse & Refine Integrate Testing
Iterative design
Design/Update proto
types for the Business
Components at UI and API
level
Develop/Update the code,
User Interface controls and
Unit test cases
Unit testing, integration
testing and do bug fixes
No
User Story
Perform Manual Testing
Coordinate each other for developing Automation suite
Execute API level
automation scripts on
continuous
integration
environment till
Acceptance criteria is
met
Execute end-to-end
automation scripts on
developed UI
Design Pseudo
codes/Classes for API
Level Automation
Build API Level automation
scripts with negative and
positive scenarios
Execute API level
automation scripts on every
component of developed
code
Design Keywords for UI
Level automation
Build automation scripts
using Keywords for UI
Level automation
Capture UI Objects
properties and integrate
with UI automation
scripts
API Level Automation Testing
UI Level Automation Testing
Application Code Development
Perform goal based
Exploratory testing
Adopt Hybrid Risk
Based Testing for Test
optimization
#LetsTalkDevOps
BridgeEvents

32. Continuous…
#LetsTalkDevOps
BridgeEvents

33. Thank You
PEOPLE
#LetsTalkDevOps
BridgeEvents

34. MOVING FROM SILOS TO EMBEDDED TESTERS
Siloed Testers Embedded Testers
#LetsTalkDevOps
BridgeEvents

35. A NEW BREED OF TESTER
Testers in the past were able to work independently,
focusing on discrete issues with less collaboration
Agile testers do not have that luxury, they must be much
more:
1. Collaborative, as they might be a single tester working
inside a product team full of developers & analysts
2. Adaptable, as they might be required to wear 4 or 5 hats
in any given day
3. Well versed, as they may be reassigned to many different
projects within one organization
#LetsTalkDevOps
BridgeEvents

36. Takeaways for the Testers
Testers should focus on learning a broader set of skills, rather
than going deep in one specific area: Staying with manual
testing is not going to be fun.
Team Skills
● Collaborating in diverse
teams
● Managing conflict across
teams
● Hiring and retaining top
talent in fast growing
companies
● Creating a team culture
of trust and buy in
Technology Skills
● Understanding and
contributing to application
code
● Understanding and
contributing to automation
(functional, unit testing)
● Expanding knowledge of
additional testing types
(performance, security,
etc.)
● Expanding knowledge of
build & release pipeline
Managerial Skills
● Motivating teams under
high pressure
● Estimating and planning
in agile organizations
● Managing agile project
on both time and budget
#LetsTalkDevOps
BridgeEvents

37. References
● QA Symphony
● Blog - DevOps Culture Shift
● Google (for images)
#LetsTalkDevOps
BridgeEvents

38. #LetsTalkDevOps
BridgeEvents