Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • TypeScript 2.x By Example
  • Toc
  • feedback
TypeScript 2.x By Example

TypeScript 2.x By Example

By : Sachin Ohri
close
TypeScript 2.x By Example

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)
close

Folder and file structure for the test project

The common convention we have for naming the file for our test is a file that is suffixed with spec.ts. So, if you have a file named homepage.component.ts, your test file will be named homepage.component.spec.ts.

Karma does not use the filenaming conventions to find the test cases, it just scans through all the transpiled files and executes the test cases it finds in any file. This naming convention is specifically for us to manage our code in a more logical fashion.

As we are using the Angular CLI, it creates the respective test file when we generate a component or a service with the same naming convention. So, if we look at our current folder structure, you will see the files with names as *.spec.ts in your respective folders, as shown in the following screenshot:

Unlock full access

Continue reading for free

A Packt free trial gives you instant online access to our library of over 7000 practical eBooks and videos, constantly updated with the latest in tech
bookmark search playlist download font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete