DevTestOps

DevTestOps
Cultural Change Through
Quality Assurance
Module 1 - Talk the Talk

Module Contents
What is DevOps?
What is DevTestOps?
Module Objectives
❏ Learn, comprehend and practice DevOps principles and
fundamentals
❏ Understanding of where testing plays a part
❏ Become a competent and courageous DevOps
Team member.

Module Contents...
VM Basics
https://www.virtualbox.org/
https://www.centos.org/download/
Docker Basics
https://store.docker.com/editions/community/docker-ce-server-centos
Source Code Management
https://git-scm.com/

What is DevOps?
The WIKI definition of DevOps
DevOps is a software engineering practice that
aims at unifying software development (Dev) and
software operation (Ops). The main characteristic
of the DevOps movement is to strongly advocate
automation and monitoring at all steps of
software construction, from integration, testing,
releasing to deployment and infrastructure
management. DevOps aims at shorter
development cycles, increased deployment
frequency, more dependable releases, in close
alignment with business objectives

What is DevOps? Continue...
Examples of Practices?

- Law Practice
- Accounting Practice
- Physiotherapy Practice
- Agile Practice

- DevOps Practice

The Wall of Confusion

6 Principles of DevOps
1. Customer Centric Action
➢ Meeting customer requirements through short
feedback loops
➢ Courage to act and innovate continuously
➢ Pivot When strategy is not working
➢ Invest in products and services for customer
delight

2. Create With the End In Mind
➢ Let go of waterfall process-oriented models
➢ Act as product companies selling to real
customers
➢ All members require an engineering mindset
to envision and realise the product

3. End to End Responsibility
➢ Vertically organised teams
➢ Team is responsible till end of life
➢ Full support including quality and performance

4. Cross Functional
Autonomous Teams
➢ Fully responsible
➢ T-Shaped all rounders
➢ Hotbed for growth

5. Continuous Improvement
➢ Fail Fast
➢ Minimise waste
➢ Optimise for speed costs and ease of delivery
➢ Experimentation is paramount
➢ If it hurts do it more

6. Automate Everything You Can
➢ Adopt CI culture with high cycle rates and
instant feedback
➢ Includes infrastructure and container based
cloud platforms
➢ Synonymous with drive to renew delivery
methods

Key Elements of DevOps Teams
❏ Team Building

❏ Team Building
❏ CI and Problem Solving

❏ Team Building
❏ Leadership and
Feedback

❏ Team Building
❏ Leadership and Feedback
❏ Courage and Experimentation

Traditional Organisation Model

DevOps Organisation Model

A Common Microservice example

Solution Architecture for DevOps

Teams Supporting a Monolithic Architecture

DevOps Supporting a Microservice Architecture

Stats from Puppet

Summary
History and Definition
6 Principles of DevOps
Organisational Model
Solution Architecture

Questions?
pmateos@planittesting.com
@paulconsults
https://www.linkedin.com/in/paul-mateos-213b2167/

https://blogs.msdn.microsoft.com/uk_faculty_connection/2016/06/23/devops-the-wall-of-confusion-un
derstanding-the-basics-of-devops/
https://www.mulesoft.com/resources/api/microservices-devops-better-together
https://www.devopsagileskills.org/dasa-devops-principles/
http://leanmanufacturingtools.org/77/the-seven-wastes-7-mudas/
https://www.slideshare.net/SherryChang/evolving-team-structure-in-devops
https://www.slideshare.net/DevOpstastic/support-that-devops-change-agents-need
http://www.planitdevops.com
References

https://purplegriffon.com/quizzes/devops-mini
Quiz TIme

What is DevTestOps?
DevOps with Quality Assurance as the
focul point
Bringing Planit’s Strengths in Agile,
Automation, Engineering and Quality
Assurance together
Implementation of Testing practices
throughout the DevOps End to End
process

What is DevTestOps? Continue...
Risk Appetites - Severity / Occurrence

Risk Appetites - Change of Mentality

Strategic Objective
What does the organisation want versus what they need?
● Speed To Market
● Product Quality
● Or Stability of the Production Environment

Paths To Communication - 5 Steps
1. Identify - Anyone who works outside of your team
2. Connect - Make connections with each individual
3. Invite - Widen the connection by bringing in new
people
4. Mark - Recording the communication for future
use
5. Widen - the path through activities that engage

What is DevTestOps?
Testing pyramid
● The reality is Test Automation is
expensive and takes a long time to
implement
● Micro service testing is quick to execute
but still costly to develop
● Unit testing requires dedication, discipline
and a FAITH

What is DevTestOps?
The Bug filter
● Bugs move between layers
● A good start but not complete

The Bug filter - Unit Sorting
Smaller bugs are caught by smaller filters while larger bugs are caught by larger
filters

The Bug filter - Unit Sorting
● Six layers to the DevOps bug filter.
● Top three are for testing that occurs in the development
environment
○ unit testing
○ integration testing
○ and end-to-end testing
● Bottom three are for the information that is captured in production
that can be used to detect bugs and determine product quality
○ Alerting
○ Monitoring
○ and logging

Creating Tests At Each Filter
Unit Testing
● TDD (Test Driven Development) is a crucial foundation
● Unit test frameworks for specific code
● Mocking services to isolate integrations
● Powerful when implemented within a CI/CD pipeline and run
against integration environments
● Can be difficult to implement is some circumstances
● GUI interactions
● Databases
● Legacy code
● As DevOps engineers, this is not optional

Integration Testing
● Runs unit tests in a complex context (component)
● Bugs can be introduced from indirect interactions with other
services and applications. (System)
● Manual testing can provide great value
● Microservices is a must have architecture
● Knowledge of tools is a must for all testers
● SOUPUI
● POSTMAN
● Concept regarding NFR’s should be introduced here
● CI/CD tooling becomes essential to build, test, deploy and
then test again
● Product fitness rather than code quality

End-to-End Testing
● Is more efficient through DevOps principles
● Strongly supported by automation
● Scalable environments
● Coded change and deployments
● Coded tests and failure highlighting
● Planit champions this phase
● The fork in the road. Where DevOps can be introduced
● DevOps brings more exploratory and targeted testing ability
to satisfy customer feedback

Monitoring and Alerts Testing
● Issues should be detected by monitors
● Real or Mocked data can be used
● Controlled data easier to distinguish
● Rules based so standard testing practices apply
● Ensure alerts are sent and received successfully
● Ensure they are also fixable
● Ensure they detail the issue clearly

Log Testing
● Records everything that is happening
● At application, Server and Cloud
level
● Errors that generate no logs
highlights issues with logging
● Reveals user behavior and hidden
issues

Testing in Production
● A/B Testing - Multiple versions released for
feedback
● Beta Testing - Released to a subset of users
● Feature Toggles - Change configuration in the
application
● Cannery Servers - Adjust deployment if too many
issues
● “TIP” is a hot topic on the interwebs

Classical Costs Still Rings True

Other Tests within DevOps
● Orchestration Pipeline Testing
● Code Quality Gates
● Infrastructure Configuration Testing
● Bug Bash
● Crowdsourced
● Infrastructure Resilience Testing - chaos
monkey
● Repeatable Performance and Security Tests

Summary
Risk Appetite
Strategic Objective
Paths To Communication
Testing Pyramid
Bug Filter
Testing In Production and Other Tests in DevOps

Questions?
pmateos@planittesting.com
@paulconsults
https://www.linkedin.com/in/paul-mateos-213b2167/

A Practical Guide To Testing in DevOps - Katrina Clokie
http://www.belatrixsf.com/blog/an-introduction-to-testing-in-production/
http://infiniteundo.com/post/158179632683/abandoning-the-pyramid-of-testing-in-favor-of-a
https://www.slideshare.net/dhelper/benefit-from-unit-testing-in-the-real-world
https://test.io/software-testing-guide/devops-best-practices-integrating-qa-devops/
References

VM and Docker Basics
● Setting up a centos VM
● Installing Docker
● Pull Jenkins Docker image and start it up

VM and Docker Basics Continue...
● Oracle Virtualbox installed
○ Developer Tools
○ Networking Tools
● Create new RedHat linux vm
● 50GB HDD, 2048MB RAM
● Networking: NAT with port forwarding
○ Host Port: 8080 Guest Port: 8080

● Docker CE installed
Difference between VM and Docker?
- VM’s are complete machines while
docker is a collection of libraries sharing
the host’s kernel
- There are now vSphere Containers

● Create Docker Container with Jenkins
Master
● Create Docker Container with Jenkins
Slave
● Use Docker compose to start up both
services

DevTestOps

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Was ist angesagt?

Was ist angesagt? (20)

Ähnlich wie DevTestOps

Ähnlich wie DevTestOps (20)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

DevTestOps