Book Image

TypeScript 2.x By Example

By : Sachin Ohri
Book Image

TypeScript 2.x By Example

By: Sachin Ohri

Overview of this book

The TypeScript language, compiler, and open source development toolset brings JavaScript development up to the enterprise level. It allows you to use ES5, ES6, and ES7 JavaScript language features today, including classes, interfaces, generics, modules, and more. Its simple typing syntax enables building large, robust applications using object-oriented techniques and industry-standard design principles. This book aims at teaching you how to get up and running with TypeScript development in the most practical way possible. Taking you through two exciting projects built from scratch, you will learn the basics of TypeScript, before progressing to functions, generics, promises, and callbacks. Then, you’ll get to implement object-oriented programming as well as optimize your applications with effective memory management. You’ll also learn to test and secure your applications, before deploying them. Starting with a basic SPA built using Angular, you will progress on to building, maybe, a Chat application or a cool application. You’ll also learn how to use NativeScript to build a cool mobile application. Each of these applications with be explained in detail, allowing you to grasp the concepts fast. By the end of this book, you will have not only built two amazing projects but you will also have the skills necessary to take your development to the next level.
Table of Contents (11 chapters)


Before we start digging deeper into testing our application and the respective testing tools, it would be useful if we take a look at why we should write test cases, and what advantages we have in comparison to relying on manual testing.

How many times has it happened where you have put in hours of effort to develop an application, and when it's about to go into production, or worse, it is launched in production, you discover a blocking issue? You and your team have done exhaustive testing; but still, how did this bug skip through?

You do the retrospection and identify that there was one scenario that was never part of your testing, and that's what caused this problem. Now, you add that scenario into your test cases but, six months down the line, the cycle repeats.