keytorctesttalks #11 - berk dülger, devops tactical adaption theory
TRANSCRIPT
![Page 1: KeytorcTestTalks #11 - Berk Dülger, DevOps Tactical Adaption Theory](https://reader031.vdocuments.us/reader031/viewer/2022030311/58ef55391a28ab66578b467d/html5/thumbnails/1.jpg)
DevOps Tactical Adoption Theory
![Page 2: KeytorcTestTalks #11 - Berk Dülger, DevOps Tactical Adaption Theory](https://reader031.vdocuments.us/reader031/viewer/2022030311/58ef55391a28ab66578b467d/html5/thumbnails/2.jpg)
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
![Page 3: KeytorcTestTalks #11 - Berk Dülger, DevOps Tactical Adaption Theory](https://reader031.vdocuments.us/reader031/viewer/2022030311/58ef55391a28ab66578b467d/html5/thumbnails/3.jpg)
George Orwell’s 1984 vs
Aldous Huxley’s Brave New World
![Page 4: KeytorcTestTalks #11 - Berk Dülger, DevOps Tactical Adaption Theory](https://reader031.vdocuments.us/reader031/viewer/2022030311/58ef55391a28ab66578b467d/html5/thumbnails/4.jpg)
In 1984, which is a popular dystopian novel, Orwell feared what we hate will ruin us. People are controlled by inflicBng pain.
![Page 5: KeytorcTestTalks #11 - Berk Dülger, DevOps Tactical Adaption Theory](https://reader031.vdocuments.us/reader031/viewer/2022030311/58ef55391a28ab66578b467d/html5/thumbnails/5.jpg)
In ‘Brave New World’, another popular dystopian novel, Huxley feared what we love will ruin us. People are controlled by inflicBng pleasure.
![Page 6: KeytorcTestTalks #11 - Berk Dülger, DevOps Tactical Adaption Theory](https://reader031.vdocuments.us/reader031/viewer/2022030311/58ef55391a28ab66578b467d/html5/thumbnails/6.jpg)
"We live ‘more’ in a Brave New World"
![Page 7: KeytorcTestTalks #11 - Berk Dülger, DevOps Tactical Adaption Theory](https://reader031.vdocuments.us/reader031/viewer/2022030311/58ef55391a28ab66578b467d/html5/thumbnails/7.jpg)
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.
![Page 8: KeytorcTestTalks #11 - Berk Dülger, DevOps Tactical Adaption Theory](https://reader031.vdocuments.us/reader031/viewer/2022030311/58ef55391a28ab66578b467d/html5/thumbnails/8.jpg)
Do not force people, make them believe in
Your Managers Your Colleagues even Yourself
![Page 9: KeytorcTestTalks #11 - Berk Dülger, DevOps Tactical Adaption Theory](https://reader031.vdocuments.us/reader031/viewer/2022030311/58ef55391a28ab66578b467d/html5/thumbnails/9.jpg)
Sustainable success requires both boSom-‐up pracMces and top-‐down management support
![Page 10: KeytorcTestTalks #11 - Berk Dülger, DevOps Tactical Adaption Theory](https://reader031.vdocuments.us/reader031/viewer/2022030311/58ef55391a28ab66578b467d/html5/thumbnails/10.jpg)
Show the
Value to everyone
![Page 11: KeytorcTestTalks #11 - Berk Dülger, DevOps Tactical Adaption Theory](https://reader031.vdocuments.us/reader031/viewer/2022030311/58ef55391a28ab66578b467d/html5/thumbnails/11.jpg)
DevOps is not a goal, but a process of conMnuous
improvement
![Page 12: KeytorcTestTalks #11 - Berk Dülger, DevOps Tactical Adaption Theory](https://reader031.vdocuments.us/reader031/viewer/2022030311/58ef55391a28ab66578b467d/html5/thumbnails/12.jpg)
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.
![Page 13: KeytorcTestTalks #11 - Berk Dülger, DevOps Tactical Adaption Theory](https://reader031.vdocuments.us/reader031/viewer/2022030311/58ef55391a28ab66578b467d/html5/thumbnails/13.jpg)
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.
![Page 14: KeytorcTestTalks #11 - Berk Dülger, DevOps Tactical Adaption Theory](https://reader031.vdocuments.us/reader031/viewer/2022030311/58ef55391a28ab66578b467d/html5/thumbnails/14.jpg)
There is no DevOps without
ConMnuous TesMng
![Page 15: KeytorcTestTalks #11 - Berk Dülger, DevOps Tactical Adaption Theory](https://reader031.vdocuments.us/reader031/viewer/2022030311/58ef55391a28ab66578b467d/html5/thumbnails/15.jpg)
Business Facing
Technology Facing
![Page 16: KeytorcTestTalks #11 - Berk Dülger, DevOps Tactical Adaption Theory](https://reader031.vdocuments.us/reader031/viewer/2022030311/58ef55391a28ab66578b467d/html5/thumbnails/16.jpg)
Unit
Integration
UI High
Medium
Low
Low
Medium
High
Medium
Long / High
Short / Low
Test Type
Business Logic Coverage
Code Coverage ExecuBon Time / Costs
![Page 17: KeytorcTestTalks #11 - Berk Dülger, DevOps Tactical Adaption Theory](https://reader031.vdocuments.us/reader031/viewer/2022030311/58ef55391a28ab66578b467d/html5/thumbnails/17.jpg)
A TacBcal AdopBon Example in
ConMnuous TesMng
![Page 18: KeytorcTestTalks #11 - Berk Dülger, DevOps Tactical Adaption Theory](https://reader031.vdocuments.us/reader031/viewer/2022030311/58ef55391a28ab66578b467d/html5/thumbnails/18.jpg)
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.
![Page 19: KeytorcTestTalks #11 - Berk Dülger, DevOps Tactical Adaption Theory](https://reader031.vdocuments.us/reader031/viewer/2022030311/58ef55391a28ab66578b467d/html5/thumbnails/19.jpg)
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.