Book Image

Kotlin Programming Cookbook

By : Aanand Shekhar Roy, Rashi Karanpuria
Book Image

Kotlin Programming Cookbook

By: Aanand Shekhar Roy, Rashi Karanpuria

Overview of this book

The Android team has announced first-class support for Kotlin 1.1. This acts as an added boost to the language and more and more developers are now looking at Kotlin for their application development. This recipe-based book will be your guide to learning the Kotlin programming language. The recipes in this book build from simple language concepts to more complex applications of the language. After the fundamentals of the language, you will learn how to apply the object-oriented programming features of Kotlin 1.1. Programming with Lambdas will show you how to use the functional power of Kotlin. This book has recipes that will get you started with Android programming with Kotlin 1.1, providing quick solutions to common problems encountered during Android app development. You will also be taken through recipes that will teach you microservice and concurrent programming with Kotlin. Going forward, you will learn to test and secure your applications with Kotlin. Finally, this book supplies recipes that will help you migrate your Java code to Kotlin and will help ensure that it's interoperable with Java.
Table of Contents (21 chapters)
Title Page
Copyright and Credits
Packt Upsell
Contributors
Preface
Index

Introduction


Testing is a fundamental part of software engineering if you want your code base to be scalable and maintainable. In Android, there are basically two types of testing: one is unit testing and the other is integrated testing. Unit testing is a type of testing where individual units are tested independently, while integrated testing, which is also sometimes known as instrumentation testing, requires an Android device or an emulator for the tests to run. Since integrated testing requires real devices or an emulator, these tests are often slower to execute. Unit tests are fast because they don’t have any such need for real devices or emulators in order to run. Since unit tests are faster and instrumentation tests are slower, it is often thought that a robust test suite should have these tests in the proportion of 80% to 20%. So your code base should consist of 80% unit tests and 20% instrumentation tests.