Book Image

TypeScript High Performance

By : Ajinkya Kher
Book Image

TypeScript High Performance

By: Ajinkya Kher

Overview of this book

<p>In a world where a tiny decrease in frames per second impacts customer engagement greatly, writing highly scalable code is more of a necessity than a luxury. Using TypeScript you get type checking during development. This gives you the power to write optimized code quickly. This book is also a solid tool to those who’re curious to understand the impact of performance in production, and it is of the greatest aid to the proactive developers who like to be cognizant of and avoid the classic pitfalls while coding.</p> <p>The book will starts with explaining the efficient implementation of basic data Structures, data types, and flow control. You will then learn efficient use of advanced language constructs and asynchronous programming. Further, you'll learn different configurations available with TSLint to improve code quality and performance. Next, we'll introduce you to the concepts of profiling and then we deep dive into profiling JS with several tools such as firebug, chrome, fiddler. Finally, you'll learn techniques to build and deploy real world large scale TypeScript applications.</p>
Table of Contents (17 chapters)
Title Page
Credits
Foreword
About the Author
Acknowlegement
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface
7
Profile Deployed JS with Developer Tools and Fiddler

Unit tests


Unit tests are a key part of writing quality code in any language. The idea behind unit tests is to test the smallest atomic piece of your code and test it with all possible inputs and ensure that it produces the right output. The goal with writing unit tests is to ensure that all the building blocks of your application are well tested and that when they begin to function as one big cohesive unit, there is some sort of certainty established that the application will behave well.

Often, you will see in real-world applications, unit tests are integrated into the build process. This means that each time you push a change to your source code, the unit tests are run and your change is merged with the source code based on the results of the testing. This ensures that the code quality is maintained in the source code.

Developers are encouraged to write new unit tests for the new features they introduce to the source code. The reason behind this is simple. As the creator of a feature, you...