keytorctesttalks #11 - berk dülger, devops tactical adaption theory
TRANSCRIPT
DevOps Tactical Adoption Theory
Berk Dülger Professional Consultant & Project Manager, 2013-‐ ….. So;ware Engineer in Test, Atos InternaBonal 2011-‐2013 So;ware Engineer, Huawei TelecommunicaBon 2009-‐2011 So;ware Engineer, FreeLance 2008-‐2009 Intern, Microso;, Turk.Net 2007-‐2009 Academic Msc. Management, Boğaziçi University, 2016 Bsc. Computer Engineering, Dokuz Eylül University, 2009 Karşıyaka Anadolu High School, 2005
George Orwell’s 1984 vs
Aldous Huxley’s Brave New World
In 1984, which is a popular dystopian novel, Orwell feared what we hate will ruin us. People are controlled by inflicBng pain.
In ‘Brave New World’, another popular dystopian novel, Huxley feared what we love will ruin us. People are controlled by inflicBng pleasure.
"We live ‘more’ in a Brave New World"
Newton's Laws of MoMon Law III: To every acBon there is always opposed an equal reacBon: or the mutual acBons of two bodies upon each other are always equal, and directed to contrary parts.
Do not force people, make them believe in
Your Managers Your Colleagues even Yourself
Sustainable success requires both boSom-‐up pracMces and top-‐down management support
Show the
Value to everyone
DevOps is not a goal, but a process of conMnuous
improvement
The idea here, it is not required to add the tools/processes to stack from sequenBal beginning to end, but seeking benefit.
DevOps TacMcal AdopMon Theory hypothesis each step towards DevOps maturity should bring a visible business value empowering management and team commitment for the next step.
The reason behind the theory is to encourage(make believe) pracBBoners to
apply each step one-‐by-‐one and then having the benefits in projects.
Consequently, each step will be tested in terms of uBlity and proved method validity
for the further steps.
There is no DevOps without
ConMnuous TesMng
Business Facing
Technology Facing
Unit
Integration
UI High
Medium
Low
Low
Medium
High
Medium
Long / High
Short / Low
Test Type
Business Logic Coverage
Code Coverage ExecuBon Time / Costs
A TacBcal AdopBon Example in
ConMnuous TesMng
UI Testing (End-to-End Tests), where you test the entire system together to ensure it does what it is supposed to do under real life conditions.
Unit Testing aims to test small chunks of your code in isolation from the rest of the world.
You need both of these in most of projects, but at different times: unit testing during development (ideally from the very
beginning, TDD!!!), and ui testing later, once you actually have some complete end-to-end functionality.
If you already have a system running, having no tests,
practically you have legacy code. Start to get the best test coverage achievable with the least effort first, which means
high level functional(end-to-end) tests.
Adding unit tests is needed too, but it takes much more effort and starts to pay back later.
