Book Image

Continuous Delivery with Docker and Jenkins - Second Edition

By : Rafał Leszko
Book Image

Continuous Delivery with Docker and Jenkins - Second Edition

By: Rafał Leszko

Overview of this book

Continuous Delivery with Docker and Jenkins, Second Edition will explain the advantages of combining Jenkins and Docker to improve the continuous integration and delivery process of an app development. It will start with setting up a Docker server and configuring Jenkins on it. It will then provide steps to build applications on Docker files and integrate them with Jenkins using continuous delivery processes such as continuous integration, automated acceptance testing, and configuration management. Moving on, you will learn how to ensure quick application deployment with Docker containers along with scaling Jenkins using Kubernetes. Next, you will get to know how to deploy applications using Docker images and testing them with Jenkins. Towards the end, the book will touch base with missing parts of the CD pipeline, which are the environments and infrastructure, application versioning, and nonfunctional testing. By the end of the book, you will be enhancing the DevOps workflow by integrating the functionalities of Docker and Jenkins.
Table of Contents (18 chapters)
Title Page
Dedication
About Packt
Contributors
Preface
Index

Chapter 5: Automated Acceptance Testing


  1. Docker registry is a stateless application server that stores Docker images.
  2. Docker Hub is the best-known public Docker registry.
  3. The convention is <registry_address>/<image_name>:<tag>.
  4. The staging environment is the pre-production environment dedicated to integration and acceptance testing.
  5. The following commands: docker builddocker logindocker push.
  6. They allow us to specify tests in a human-readable format, which helps with collaboration between business and developers.
  7. Acceptance Criteria (feature scenario specification), Step Definitions, Test Runner.
  8. Acceptance test-driven development is a development methodology (seen as an extension of TDD) that says to always start the development process from the (failing) acceptance tests.