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 Your JavaScript

In this chapter, we are going to test the code we have written in the previous chapters. We will start out with unit tests. We can write unit tests in, and for, JavaScript using Jasmine. After that, we will write UI tests using Selenium. At the end of the chapter, we will have tested our complete application so far and a little bit more.

The obvious advantage to testing your code is that you will be able to catch bugs as soon as they are introduced in any part of the application. How often have you made a change to some page only to find out another page broke because you changed some JavaScript that was shared between the two pages? The more important question: how often did you not find out about the other page breaking? Exactly! So that is why testing your JavaScript can really give you an edge in delivering high-quality software.

A less obvious advantage...