Android UnitTest

Android UnitTest

Table of Contents

  • kinds of Unit Tests in Android
  • Android Instrument Test
  • Junit Test
  • the Demo
Unit Test was always the most import part of a project, especially for Object-oriented programming like Java codes, and also was the necessary part of Test-Driven Development technology. But how to process test-driven technology in Android app developement, we all know that android app is based on Java code, and the thought of TDD was in the blood of Java. There are must be some ways to do TDD in Android, and this article will guide you to the Unit test in Android Development.

1 kinds of Unit Tests in Android

There are two levels of Unit Test in Android, Android Instrument Test, which running in the Android Devices; and Junit Test, which running without any Android environment.

The key difference between two of them are the dependency on the android.jar, in other word, the Android API. We develop android app by import the dependency of android.jar, which collected all the Android API. So what the API is? short for Application Programming Interface, yeah, it is the interface without the implementation, and the implementation was inside the Android device, that's why we need to install the test app, in order to run it.

So if your code is just pure java code without dependency on android.jar, you can run your test code in Junit framework in every where.

In sum, Android Test Instrument is to test Android component behaver, and the Junit test case is used to test logical and functional parts of the App.

2 Android Instrument Test

The Android doc described it very well. so following it.

Android Studio support this kinds of test very well, all you need to do is to configure run dialog in the right way. After I code the unit test, following is the mistakes I met to run it.
  • make sure the unit test item in Run/Debug Configurations is in the Android Tests part instead of the Junit part.
  • remember to unlock the phone's screen when you wanna test the UI interaction.

3 Junit Test

As described in the first section, Junit test can be running in the command line directly. 

./gradlew test

add following lines into build.gradle to disable the unimportant android.jar reference. 

android {
    ...

    testOptions {
        unitTests.returnDefaultValues = true
    }
}

dependencies {
   testCompile 'junit:junit:4.12'
   testCompile 'org.mockito:mockito-core:1.9.5'
}

If your code imported the utils classes in the Android.jar like android.util.Log, you need to add above line to let junit ignore the class unfounded exception.

Also noticed is that the keyword testCompile, which means the dependency in test directory. Basically, I collect the Junit test in test directory, and the Android Test cases in androidTest directory.

Comments

Post a Comment

Popular posts from this blog

How Bluetooth LE works? -- Link Layer

Image
How Bluetooth LE works? - Link layer Table of Contents 1 Bluetooth LE system architecture 2 Bluetooth LE Physical layer 3 Bluetooth LE Link Layer states 4 Bluetooth LE Link Layer packets 1 Bluetooth LE system architecture This is the first post and hopefully a series of upcoming postings about Bluetooth Low Energy. Above figure is the protocol stack of a whole Bluetooth LE system. The Bluetooth LE is one part of Bluetooth v4.0 specification, it was designed not to pursue high transmission speed but for lower energy consumption. So the Bluetooth LE products can be powered by a button-cell battery for years. How did it do that? This article is a review of Robin Heydon's excellent book – Bluetooth Low Energy, the developer's handbook. Bluetooth LE is completely redesigned of classic Bluetooth protocol, It seems that both the Bluetooth LE and classic Bluetooth has the same architecture from above figure, but actually they are so different inside, an...
Read more

Bluedroid stack in android

Image
Bluedroid stack in android Table of Contents Bluetooth stack in android Bluedroid .VS. Bluez Porting guide of Bluedroid stack 1 Bluetooth stack in android From Android 4.2, google use Bluedroid stack as its default Bluetooth host stack, before android 4.2, its default Bluetooth host stack was Bluez, which is also the Linux distribution's default stack. So why google changed its Bluetooth stack? The reason is maybe that Bluez stack was designed for the desktop environment, so in order to port Bluez into android, android must solve some dependency issues, like porting Dbus, Linux desktop's default IPC, into android. So there are at least five processes to power Bluetooth before android 4.2, they are systems, Bluetooth APP, Bluez, hciattach, and Dbus. The damn thing is that there are bugs between them, so Bluetooth stack is the weakest part in the android system before android 4.2, yeah, it is the usual reason that android system corrupted. So, what's t...
Read more

Network programming in elisp

  Network API in elisp Table of Contents 1 Introduction 2 A example 3 Http server implemented by elisp 1 Introduction Emacs is not just an editor, Yes, that's true. Emacs lisp can do network connection programming by its network API. But there is something difference with other kinds of programming language. First, elisp do not support multi-thread, pretty cool, huh!! Yeh, Multi-threads programming is a horrible venture for you, right! Second, There is no socket similarly conception in elisp, and elisp provide network programming ability as processes. Elisp can open a network connection by function – open-network-stream .  It can make network connection server listen a special port by function - make-network-process . Both of those function return a process object. Then you can communicate with the process by process's API. 2 A example I write a snippet code to figure out How to use it. ( require ' cl ) ( defvar my-network-client-b...
Read more