Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

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

PhoneGap By Example

By : Andrew Kovalenko
close
PhoneGap By Example

PhoneGap By Example

By: Andrew Kovalenko

Overview of this book

PhoneGap is a free and open source framework that allows you to create mobile apps using standardized web APIs for the platforms you care about. It is one of the first and fastest spreading tools to develop hybrid applications using CSS, JavaScript, and HTML, without losing the advantages of native applications. If you are already a web developer, this book will provide you with the skills you need to create, customize, test, and deploy hybrid mobile applications. Starting from the beginning, this book will cover how to set up your PhoneGap development environment, add mobile web frameworks and plugins, design and customize the application layout, and utilize the embedded features of the PhoneGap framework. By working through the steps in each chapter, you will quickly master a variety of mobile applications with totally different approaches. You will then learn how to develop a PhoneGap plugin with native interfaces for iOS and Android, as well as common approaches to test PhoneGap applications. With ample screenshots that show you how to build a phenomenal application, PhoneGap by Example will ensure your success with this cutting-edge mobile development framework for hybrid applications.
Table of Contents (12 chapters)
close
11
Index

Unit testing frameworks and test runners


There are a lot of testing frameworks nowadays. In general, when we use a framework for testing, we need two things:

  • Test runner: This is the part of the framework that runs our tests and displays messages telling us whether they have passed or failed.

  • Assertions: These methods are used for the actual checks. For example, if you need to see whether an active variable is true, then you may write expect(active).toBe(true) instead of just if(active === true). It's just better for the reader of the test, and it also prevents some strange situations, for example, if you want to see whether a variable is defined. The if statement in the following code returns true because the status variable has a value, and this value is null. In fact, we are asking "is the status variable initialized", and if we leave the test like that, we will get wrong results. That's why, we need an assertion library that has proper methods for testing, as shown in the following code...

bookmark search playlist 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