Book Image

Hands-On TypeScript for C# and .NET Core Developers

By : Francesco Abbruzzese
5 (1)
Book Image

Hands-On TypeScript for C# and .NET Core Developers

5 (1)
By: Francesco Abbruzzese

Overview of this book

Writing clean, object-oriented code in JavaScript gets trickier and complex as the size of the project grows. This is where Typescript comes into the picture; it lets you write pure object-oriented code with ease, giving it the upper hand over JavaScript. This book introduces you to basic TypeScript concepts by gradually modifying standard JavaScript code, which makes learning TypeScript easy for C# ASP.NET developers. As you progress through the chapters, you'll cover object programming concepts, such as classes, interfaces, and generics, and understand how they are related to, and similar in, both ES6 and C#. You will also learn how to use bundlers like WebPack to package your code and other resources. The book explains all concepts using practical examples of ASP.NET Core projects, and reusable TypeScript libraries. Finally, you'll explore the features that TypeScript inherits from either ES6 or C#, or both of them, such as Symbols, Iterables, Promises, and Decorators. By the end of the book, you'll be able to apply all TypeScript concepts to understand the Angular framework better, and you'll have become comfortable with the way in which modules, components, and services are defined and used in Angular. You'll also have gained a good understanding of all the features included in the Angular/ASP.NET Core Visual Studio project template.
Table of Contents (16 chapters)

Testing

Angular unit tests are performed with Jasmine that was described in the Testing your library with Jasmine section of Chapter 8, Building TypeScript Libraries. Angular uses Karma to run all tests in a browser, and adds some facilities to handle component compilation, Dependency Injection, and HTML manipulation.

When an Angular entity is generated, Angular automatically generates a test file skeleton to unit test that entity. All existing tests may be run by launching the ng test command in a Windows console rooted in the ClientApp folder. Once the command is activated, the browser opens and Karma displays the results of all tests. Since some tests are incomplete, or not aligned to the modifications done to some components, Karma, for sure, will signal a number of errors. The counter.component.spec.ts file contains tests that should pass, so let's open it. It contains...