Introduction to Testing

Chapter overview

Code isn’t created until the respective tests have been written. After reading the previous chapters, we can probably agree on that statement. However, we might be wondering, why haven’t we written any tests? Fair enough.

We chose not to do this because we believe it would make the content harder to absorb. Since we wanted to focus on learning Deno while building an application, we decided not to do this. The second reason is that we truly wanted a full chapter focused on testing, that is, this one.

Testing is a very important part of the software lifecycle. It can be used to save time, to clearly state requirements, or just because we want to feel confident in rewriting and refactoring later. Independent of the motivation, one thing is certain: we’ll write tests. We truly believe that testing plays a big role in software design. Code that is easy to test is likely easy to maintain.

Since we’re great advocates of the importance of testing, we couldn’t consider this a complete guide to Deno without learning about it.