Book Image

NativeScript for Angular Mobile Development

By : Anderson, Nathan Walker
Book Image

NativeScript for Angular Mobile Development

By: Anderson, Nathan Walker

Overview of this book

NativeScript is an open source framework that is built by Progress in order to build truly native mobile apps with TypeScript, JavaScript or just Angular which is an open source framework built by Google that offers declarative templates, dependency injection, and fully featured modules to build rich applications. Angular’s versatile view handling architecture allows your views to be rendered as highly performant UI components native to iOS and Android mobile platforms. This decoupling of the view rendering layer in Angular combined with the power of native APIs with NativeScript have together created the powerful and exciting technology stack of NativeScript for Angular. This book focuses on the key concepts that you will need to know to build a NativeScript for Angular mobile app for iOS and Android. We’ll build a fun multitrack recording studio app, touching on powerful key concepts from both technologies that you may need to know when you start building an app of your own. The structure of the book takes the reader from a void to a deployed app on both the App Store and Google Play, serving as a reference guide and valuable tips/tricks handbook. By the end of this book, you’ll know majority of key concepts needed to build a successful NativeScript for Angular app.
Table of Contents (17 chapters)
13
Integration Testing with Appium

Unit testing

Unit tests are used to test small pieces of application code functionality for correctness. This also allows us to verify that the functionality continues to work as expected, when you refactor code and/or add new features. Both NativeScript and Angular offer unit testing frameworks. We will explore both types of unit testing, as they both have pros and cons.

Developing tests at any time is good. However, it is preferable to develop them alongside your development of the project's code. Your mind will be fresh on the new features, modifications, and all the new code you just added. In our case, because we are presenting lots of new concepts throughout this book, we haven't followed the best practice since it would have complicated the book even more. So, although adding tests later is good, adding them before or while adding your new code is considered the...