Book Image

Advanced Node.js Development

By : Andrew Mead
Book Image

Advanced Node.js Development

By: Andrew Mead

Overview of this book

Advanced Node.js Development is a practical, project-based book that provides you with all you need to progress as a Node.js developer. Node is a ubiquitous technology on the modern web, and an essential part of any web developer’s toolkit. If you're looking to create real-world Node applications, or you want to switch careers or launch a side-project to generate some extra income, then you're in the right place. This book was written around a single goal: turning you into a professional Node developer capable of developing, testing, and deploying real-world production applications. There's no better time to dive in. According to the 2018 Stack Overflow Survey, Node is in the top ten for back-end popularity and back-end salary. This book is built from the ground up around the latest version of Node.js (version 9.x.x). You'll be learning all the cutting-edge features available only in the latest software versions. This book delivers advanced skills that you need to become a professional Node developer. Along this journey you'll create your own API, you'll build a full real-time web app and create projects that apply the latest Async and Await technologies. Andrew Mead maps everything out for you in this book so that you can learn how to build powerful Node.js projects in a comprehensive, easy-to-follow package designed to get you up and running quickly.
Table of Contents (17 chapters)
Title Page
Copyright and Credits
Packt Upsell
Contributors
Preface
Index

Testing GET /todos/:id


In this section, we're going to create three test cases for this route, the one that fetches an individual Todo item. One is going to make sure that when we pass in an invalid ObjectID, we get a 404 response code. Another one is going to verify that when we pass in a valid ObjectID, but it doesn't match a doc, we get a 404 response code back, and lastly we'll write a test case that makes sure that when we pass in an ObjectID that does match a doc, that doc actually comes back in the response body.

We're going to write the test case for the valid call together, then you'll be writing two test cases on your own. That will be the challenge for this section.

 Writing test cases for GET/todos/:id

Over inside of server.test.js we can get started down at the very bottom by adding a describe block. I'm going to call describe, and this describe block will be named GET /todos/:id, and we can add our arrow function (=>) as the callback function. Inside of our describe callback...