If you are not doing automated testing, you are NOT ready for continuous delivery

CI as we know is closely knit to Continuous Delivery!
Continuous Integration (CI) is a development practice that requires developers to integrate code into a shared repository several times a day. Each check-in is then verified by an automated build, allowing teams to detect problems early.

It is actually a series of practices that make you ready for continuous delivery. What you need is a quick way of seeing what happened after your new code is deployed. 

You need the following:
  1. Staging environment (clone of prod) before the code hits production release.
  2. Automated tests that kick off as soon as the code is committed
  3. Some form of Iterative development - Agile 
  4. A single source repository
  5. Every commit built on an integration machine 
  6. Fast build 

Visualizations of Continuous Delivery

Nhan Ngo, a QA engineer at Spotify, made four fabulous visualizations while reading Continuous Delivery. She has very kindly agreed to make them available under a Creative Commons license so feel free to share them, download them, and print them out (click to get a higher resolution version). Thank you Nhan!


Popular posts from this blog

XPATH for IE / internet explorer

RPA - Blue Prism, OpenSpan, Automation Anywhere vs UIPath