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 our C# code

Now that we have our SQL covered, let's go back to our C# code for a bit. There is not really anything to unit test, as we have little to no business logic. It is all just selecting data and returning it to the frontend. Great for E2E tests; not so great for unit testing. So, just as in Node.js, let's create an Order.cs file and pretend we need it for invoicing later. I have created a new folder in the project root and named it Invoicing. In it, I have placed two files, Order.cs and OrderLine.cs. Both are pretty straightforward.

The OrderLine class is pretty much the same as in JavaScript, except we can work with the decimal data type which does not have rounding errors and so we do not need to round. The methods GetSubTotal and GetTotal could be implanted as properties with just a getter, but for some reason, our code coverage will not cover them...