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)

Running tests with Karma

Karma, as mentioned, is a test runner (and it is spectacular, according to the Karma team). So a test runner really does what the name implies: it runs tests. So, instead of having to refresh your test page, Karma just runs them for you. Karma can be easily configured to run your tests on multiple browsers, such as IE (or some specific version), Edge, Firefox, Chrome, Safari, and Opera. After running your tests, Karma can generate reports on your tests and your code coverage. You can set minimum coverage thresholds and make your test runs fail when your code is not sufficiently covered. On top of that, Karma is a layer of abstraction. You can configure your test framework, such as Jasmine, and then switch to something else, such as Mocha, and everything will still work. You only have to change your tests, of course, and a single line in your Karma configuration...