Book Image

Deno Web Development

By : Alexandre Portela dos Santos
Book Image

Deno Web Development

By: Alexandre Portela dos Santos

Overview of this book

Deno is a JavaScript and TypeScript runtime with secure defaults and a great developer experience. With Deno Web Development, you'll learn all about Deno's primitives, its principles, and how you can use them to build real-world applications. The book is divided into three main sections: an introduction to Deno, building an API from scratch, and testing and deploying a Deno application. The book starts by getting you up to speed with Deno's runtime and the reason why it was developed. You'll explore some of the concepts introduced by Node, why many of them transitioned into Deno, and why new features were introduced. After understanding Deno and why it was created, you will start to experiment with Deno, exploring the toolchain and writing simple scripts and CLI applications. As you progress to the second section, you will create a simple web application and then add more features to it. This application will evolve from a simple 'hello world' API to a web application connected to the database, with users, authentication, and a JavaScript client. In the third section, the book will take you through topics such as dependency management, configuration and testing, finishing with an application deployed in a cloud environment. By the end of this web development book, you will become comfortable with using Deno to create, maintain, and deploy secure and reliable web applications.
Table of Contents (15 chapters)
Section 1: Getting Familiar with Deno
Section 2: Building an Application
Section 3: Testing and Deploying

Creating integration tests for the application

The three tests we've written so far have been unit tests for a single module, and an integration test between two different modules. However, to be confident that our code is working, it would be cool if we could test the application as a whole. That's what we'll do here. We'll wire up our application with a testing configuration and run a few tests against it.

We'll start by calling the same function we called to initialize the web server and then create instances of all its dependencies (controllers, repositories, and so on). We'll make sure we use things such as in-memory persistence to do so. This will make sure that our tests are replicable and don't need a complex teardown phase or a connection to a real database, as that would slow down the tests.

We'll start by creating a test file that, for now, will encompass the integration tests for the application. As the application evolves...