Book Image

The Node Craftsman Book

By : Manuel Kiessling
Book Image

The Node Craftsman Book

By: Manuel Kiessling

Overview of this book

The Node Craftsman Book helps JavaScript programmers with basic Node.js knowledge to now thoroughly master Node.js and JavaScript. This book dives you deeper into the craft of software development with Node.js and JavaScript, incuding object-orientation, test-driven development, database handling, web frameworks, and much more. The Node Craftsman Book shows you how to work with Node.js and how to think deeply about how you build your Node projects. You'll master how to build a complete Node.js application across six crafting milestones, and you'll learn many specific skills to achieve that mastery. These skills include how to work with the Node Package Manager in depth, how to connect your Node applications to databases, and how to write unit tests and end-to-end tests for your code. You'll experience the full Node.js development picture, and learn how to craft and control your Node.js applications - right through to fully-fledged web applications using REST, and integration with Angular applications.
Table of Contents (17 chapters)
Free Chapter
1
Part 1: Node.js Basics in Detail
2
Working with NPM and Packages
3
Test-driven Node.js Development
11
Milestone 1 – A First Passing Test Against the Server
13
Milestone 3 – Setting the Stage for a Continuous Delivery Workflow

Milestone 3 – Setting the Stage for a Continuous Delivery Workflow

We are already growing our application driven by tests, however, there are still some inconveniences that hinder us from going fully continuous. If the goal is to put every change we make into production automatically (safeguarded by our tests, of course), then we need to automate the things we still do manually: starting the server and changing the database structure.

Let's tackle the server startup first. It would be great if each test case would start and stop the server process as needed. This is possible by refactoring the server code a bit.

We need to split into two files what is currently handled in src/backend/index.js. The goal here is to have the server logic in one file, and the server startup in another one. This way, our tests can start the server logic up by themselves, and for production, we still have a file we can execute...