Book Image

DevOps Paradox

By : Viktor Farcic
Book Image

DevOps Paradox

By: Viktor Farcic

Overview of this book

DevOps promises to break down silos, uniting organizations to deliver high quality output in a cross-functional way. In reality it often results in confusion and new silos: pockets of DevOps practitioners fight the status quo, senior decision-makers demand DevOps paint jobs without committing to true change. Even a clear definition of what DevOps is remains elusive. In DevOps Paradox, top DevOps consultants, industry leaders, and founders reveal their own approaches to all aspects of DevOps implementation and operation. Surround yourself with expert DevOps advisors. Viktor Farcic draws on experts from across the industry to discuss how to introduce DevOps to chaotic organizations, align incentives between teams, and make use of the latest tools and techniques. With each expert offering their own opinions on what DevOps is and how to make it work, you will be able to form your own informed view of the importance and value of DevOps as we enter a new decade. If you want to see how real DevOps experts address the challenges and resolve the paradoxes, this book is for you.
Table of Contents (21 chapters)
20
Index
21
Packt

Behavior-driven development (BDD)

Viktor Farcic: You're big on BDD. Can you explain to us, for those who may not know, what it is?

Liz Keogh: BDD came about as a replacement for test-driven development (TDD). TDD wasn't really about testing, because anyone who's done TDD would say that you wrote the test before there was even any code. Essentially, you're not really testing anything; you're describing how the code you're about to write is going to work, why it's going to be valuable to you, while coming up with some examples of how you want to use it.

When we actually start thinking of them as just examples of behavior, that's class-level behavior. You would say, "Here's an example of how my class behaves." But then you've got your system: "Here's an example of how my system behaves, here's an example of my application in use," and we call those scenarios. It's the same. You take your scenarios,...