Android GUI test summarize / Android keyevent 測試

Android GUI測試上，只有 monkey 工具類似 MS LTK 裡面的 GUI load test 項目

GUI 測試一直是很耗費人力，且需要很多額外判斷方法的測試項目

如何做到自動化是件困難的事情

Android 目前有一些測試工具或方法，整理如下。

從 Software stack layer 大致分類來看:

Test Type	Methodology
GUI Directly	1.GUI record and play 2.Send key / touch event
Application	1.Instrumentation / Unit test 2.Activity element control
Framework	Hook key logger

從功能分析:

Test Type	Tool Name	Behavior Control	Limitation
GUI Directly	Sikuli	Sikuli Any shell Any scripting tool (AutoIt / AutoHotKey / …) Any program language	Remote screen
	Activity element	Control by activity element
	Experitest	GUI record and play	Commercial Cannot native AP (TBC)
	Key event	Adb keyevent (Key) Sendevent / getevent (Touch)	UI uniform problem
	Monkey	Any shell Any scripting tool (AutoIt / AutoHotKey / …) Any program language
	Monkey runner	TBC
Instrument	Instrument Unit test	Instrument / Unit test Robotium / Selenium Eclipse plugin (Testdroid)	Test single AP only or owned AP only
Framework	Key logger

*Remote screen:

1.MyMobiler (Remote control)

2.DDMS (Display only)

3.VNC (TBT)

4.QTADB (Display only)

5.Android Screen Monitor (Display only)

6.androidscreencast.jnlp (Remote control)

7.Android Projector (Display only)

8.AndroidScreenCapureSetup (Unknown)

9. droidAtScreen-0.5.1.jar (Unknow)