“…Thus, some tools test Android applications not looking at the components of the interface, but rather through events generated for the application simulating the user touching the screen, events from the system, and also through data from the sensors of the device. For these tools, we [90], CrashScope [18,52], DroidBot [19], M[agi]C [58], ACTEve [47], PATS [77], BBOXTESTER [92], AppDoctor [63], ORBIT [39], Fest [45], Easy-Mock [45], Hamcrest [45], JUnit [45], Robolectric [45], Robotium [45] [79], Android.Test [45], DroidCrawler [54], Custom-built version of the calabashandroid [44], CATE [57], MobiGUITAR [105], [41], Context Simulator [37], ADAutomation [38], MAT [46], AM-TaaS [49], VTE [55], [59], ACRT [56], EHB-Droid [64], ATG [73], SPAG-C [76], Appetizer [79], Bot-bot [79], Culebra [79], monkeyrunner [79], Mosaic [79], Ranorex [79], HiroMacro [79], Repeti-Touch [79], MAFT [82], MBTS4MA [83], SIG-Droid …”