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)

Adding Selenium tests

Next, we are going to add Selenium tests to our application. You could, of course, use the JavaScript tests we wrote in the previous chapters. After all, Selenium tests your frontend and that has nothing to do with our C# backend. Our routing changed a bit so they will not work until we fix the URLs in the tests, but apart from the routing, everything should be as expected. However, Selenium has a C# implementation, so let's keep this project as much C# as possible and explore the Selenium C# API.

To make this work, we need yet another project. Strictly speaking, we do not need a new project and we could simply put our Selenium tests in our regular test project. However, your test project depends on your web-shop project and needs to access it in order to build. Your Selenium tests are going to need your web-shop project to run. And here is the problem...