Book Image

Continuous Integration, Delivery, and Deployment

By : Sander Rossel
Book Image

Continuous Integration, Delivery, and Deployment

By: Sander Rossel

Overview of this book

The challenge faced by many teams while implementing Continuous Deployment is that it requires the use of many tools and processes that all work together. Learning and implementing all these tools (correctly) takes a lot of time and effort, leading people to wonder whether it's really worth it. This book sets up a project to show you the different steps, processes, and tools in Continuous Deployment and the actual problems they solve. We start by introducing Continuous Integration (CI), deployment, and delivery as well as providing an overview of the tools used in CI. You'll then create a web app and see how Git can be used in a CI environment. Moving on, you'll explore unit testing using Jasmine and browser testing using Karma and Selenium for your app. You'll also find out how to automate tasks using Gulp and Jenkins. Next, you'll get acquainted with database integration for different platforms, such as MongoDB and PostgreSQL. Finally, you'll set up different Jenkins jobs to integrate with Node.js and C# projects, and Jenkins pipelines to make branching easier. By the end of the book, you'll have implemented Continuous Delivery and deployment from scratch.
Table of Contents (15 chapters)

Testing the web shop

Let's continue to add some tests for our web shop. The first thing we should ask ourselves is which files we should test in the first place. For now, the most obvious file is the shopping cart module. When we look at the shopping cart module, it seems like it is pretty difficult to test this file. An obvious test would be to add a product and check whether the price is correctly updated. However, the Line object is private to the controller and the controller $scope represents the entire cart. We have two options here: either we find out if and how we can get access to the $scope object in our unit tests or we create an additional file that has the shopping cart object and that we can reuse in our controller (or even non-Angular.js projects). You can already see that we are forced to think about our code in a certain way, because we need to use our code...