A couple of weeks ago, I read A Practical Guide to Testing in DevOps
The book explained and described DevOps x Testing with many references and keywords.
you can see why people struggle to understand where testing fits in a model that doesn’t mention it at all. For me, testing fits at each and every single point in this model.
> by Dan Ashby
In the book, we can see many words, beyond the team boundary. We can see explanations about separated test teams and activities in many traditional style world. But recent Agile and DevOps culture breaks the separations. It is the natural thing.
We can see some concrete steps about pair work and test activities. For example, first 10 min …, next 20 min is… etc. We can image how to work them in our activity quickly, I believe.
Comparing testing too deeply or too shallow also helps us.
The book is useful to understand recent development and testing culture. And almost stories were very proper for my current environment. I had some unknown words, but we’ve been working such things and knew the word and definitions.
I’d love to recommend this book to other guys who would like to catch up with recent development style include testing.