Talk from DevOpsDays Stockholm 2019

1. @SkillsForTeams

2. @SkillsForTeams

3. @SkillsForTeams
The Clash between DevOps
and Quality Assurance
John Behrens Skills-for-
Teams.com

4. @SkillsForTeams
John Behrens
John Behrens – that is me
North Germany - Holstein
Agile- Developer- Quality- Tester- Scrum- Tester-
Coach- Architect- Master- Engineer- Trainer-
Coach
Agile QA Coach
Hobbies:
Martial Arts, Liveguard, Photographie,
Cycling
Twitter:
@SkillsForTeams Skills-for-Teams.com

5. @SkillsForTeams
Tools Skills Mindset

6. @SkillsForTeams
The traditional (Dev)Ops engineer
Tools:
CLI, Automatization, Scripting, Graphana, Ansible,
Chef, Docker, Kubernetie, Clouds
Skills:
Configure environments that run software, hold it
stable, and analyze failures.
Mindset:
I am the master of the operational platform. I run
the processes and keep them stable.Deliver fast
and satisfy the customer.

7. @SkillsForTeams
The traditional QA test engineer
Tools:
JMeter, Selenium, HP Quality Center, Jira,
Cucumber, Explorative Testing
Skills:
Finding bugs, analysing code, execute
tests, write reports
Mindset:
“I proof software by bringing it to it´s limit
and improve it by showing its errors”

8. @SkillsForTeams
Project Experience
Experience from 5 Projects

9. @SkillsForTeams
Project 1: My first time DevOps with DR. Sommer
• Scrum MasterMy role:
•No Team
•No Servers
•No Infrastructure
•No Test Environment
•Rebuild an old website to Social Community
Challenges:
•„There is nothing like Sprint 0, just the
unnamed time before your project starts. „
•„Du bist auch so ein bisschen DevOps“ –
(„You are also a bit DevOps“)
Shouts:

10. @SkillsForTeams
Project 1: My first time DevOps with DR. Sommer
•Planning of QA and infrastructure before
coding begins.Clash:
•Getting something to show vs build
quality in.Clash:
•Early testing of data migration.Clash:
•Gitlab is the best tool for managing Git
repositories.
•It is useful to have showable results fast.
Learnings:

11. @SkillsForTeams
Project 2: Integration after years at the insurance company
• ISTQB TesterMy role:
•Project is already running for years.
• Integration environment has NOT been set
up.
•The operational requirments of application
needs to be documented well.
Challenges:
• „Where is our test system“
•„Ask the developer, he can tell you how to
configure your system to work on your
laptop and you can test there.“
Shouts:

12. @SkillsForTeams
Project 2: With*as code a defined environment is possible
•Developers and QA had bad relationClash:
•Operations were completly away from
Project.Clash:
•Various contracters blaming each other,
make it a role culture.Clash:
•Insurance business is slow
•You can not change everything „Dresscode“
•Fun is not everywhere
Learnings:

13. @SkillsForTeams
Project 3: One Compact Disc per Year
• Agile Quality CoachMy role:
• Implement agile quality methods
• Build was created one per year
• Legacy windows desktop software
Challenges:
• “Build will be created in October, then
we do QA until the compact disc
produced in December“
• „That new methods are working for
startup and google-like companies but
not for us“
Shouts:

14. @SkillsForTeams
Project 3: One prediction build every night
• Create a build mechanism
for predictive build and run
of basic tests.
Clash:
• Introduce new test
Methods such as ATDD,
BDD, TDD to verify quality.
Clash:
• Integrate own legacy test
framework to the new
build.
Clash:
• Just implementing
„unpossible“ stuff can
break barriers.
Learnings

15. @SkillsForTeams
Project 4: Kick the Football to the release button
• Agile and QA CoachMy role:
• Historically grown legacy Project.
• Various test systems (1 to n).
• Large test suite but too flaky
tests.
Challenges:
• „We can install the new version
on test 8 if the other test is
ready“
• „The test is red, we run it some
more times until it is green again“
Quotes:

16. @SkillsForTeams
Project 4: Renovating the test pipeline
• Configuration as code for test
environment.Clash:
• Configuration as code for test runners
(Selenium).Clash:
• Containerization of applications to make
system independent testing possible.Clash:
• Remove flaky test and automate test
run.Clash:
• Continious improvement is more
sustainable than a big change at once.Learnings:

17. @SkillsForTeams
Project 5: Migration to the „cloud“
• Agile CoachMy role:
• From own datacenter to the cloud
• From websphere to Payara
• Multiple legacy applicationss
• Ensure performance during peak
Challenges:
• „We wanna get our datacenter
empty“.
• „We don´t have time for x to do it
right “
Quotes:

18. @SkillsForTeams
Project 5: Testing and Monitoring is essential
• Performance testing before MigrationClash:
• Monitored A/B live testing in
production for QAClash:
• Also infrastructure and configuration
as code scripts need QAClash:
• Enabling Experiments
Clash:
• Resting is not testing
• Not all thinks can be tested in advanceLearnings:

19. @SkillsForTeams
Learnings

20. @SkillsForTeams
Prediction vs Production
• Keeping your predictive environment
close to the production has a great
benefit for you. DevOps tools and
mentality have great abilities for that.
• Mean time to production or mean time to
integrated test could be reduced by
joining forces of QA and DevOps.
• Fast feedback helps at all stages.

21. @SkillsForTeams
Learning from each other
• You don't have to become a DevOps
or QS professional, but if you
understand each other and know the
basic skills, you have an advantage.
• Seeing each other as friends
reaching the same gole and
accepting other focus.
• Operational requirments need to be
considered early.
• Automatization itself needs quality
assurance.

22. @SkillsForTeams
DevOps approaches mean for QA
• * as code helps to document,
requirements and ensure quality.
• * as code helps to reduce test-system
costs and affort.
• Having environments early, ensures early
testing and early and fast feedback is
possible.

23. @SkillsForTeams
Match role and Mission Mindeset
Role Mindset
• I do what my role is and others care
about other things.
Mission Mindset
• Doing everything i can do to make
the project a success

24. @SkillsForTeams
Your Clashes
Did u experience of working together from QA and DevOps roles or mindests

25. @SkillsForTeams
“
”
FOR PROJECT SUCCESS MULTIPLE PERSPECTIVES
ARE BENIFITIAL,IN MINDSET, IN SKILLS AND IN TOOLS
THE CLASH BETWEEN DEVOPS, QAAND ALL OTHER
ROLES
MAYBE ROLES WILL DISAPPEAR AND SKILLS AND MINDSET WILL
STAY
John Behrens