{"id":1480,"date":"2013-11-26T02:18:52","date_gmt":"2013-11-26T09:18:52","guid":{"rendered":"http:\/\/wiebe-elsinga.com\/blog\/?p=1480"},"modified":"2013-11-26T02:23:58","modified_gmt":"2013-11-26T09:23:58","slug":"functional-testing-for-android","status":"publish","type":"post","link":"http:\/\/wiebe-elsinga.com\/blog\/functional-testing-for-android\/","title":{"rendered":"Functional testing for Android"},"content":{"rendered":"
\n<\/div>\n\n

Applying functional testing is not a new technique during the development of Java software. Writing functional tests gives you a good understanding about the stability of an application or system, during code modifications or if new features are added.\u00a0But what about using functional testing when developing an Android application, it is also easy to achieve?<\/p>\n

“And, is the application still works?” or “Is the application broken?”,\u00a0these are questions that developers should be able to answer if a code change has been made or an improvement has been added.\u00a0This is no different when developing an Android application.\u00a0Also, the use of TDD (Test Driven Development), in which first the test is written,\u00a0after which the code follows, is good practice.\u00a0Automated functional testing has become part of software development. Using Selenium and Fitnesse for testing Java application,\u00a0combined with Jenkins has become avery day pratice to most Java developers.\u00a0So you would expect that this would differ during the development of Android app. Unfortunately this is not (yet) the case.\u00a0Because of the relatively rapid growth of Android, these testing methods aren’t yet mature enough.<\/p>\n

Lets look at four testing framework that can be used during Android app development:<\/p>\n

How to install the specific framework is not part of this article. With the use of code examples pros and cons will be explained for the specific framework.<\/div>\n

 
\nThe Android application<\/a> that is being tested is a simple calculator. The common test scenario we will be implementing is testing if \u20181\u2019 + \u20183\u2019 gives a result of \u20184\u2019.<\/p>\n

UIAutomator<\/h2>\n

The Google test framework UIAutomator<\/a>\u00a0makes it possible to write simple Java (and JUnit) functional tests.\u00a0The framework is not tied to the application that needs to be tested, but also has access to the Android platform itself.
\nThis makes it possible to adjust your Android emulator or physical phone settings while running your test(s). This means that you can test the behavior of the test application if, for example, the internet connection is being switched off.<\/p>\n

UiObject allAppsButton =<\/span> new<\/span> UiObject(<\/span>new<\/span> UiSelector(<\/span>)<\/span>.description<\/span>(<\/span>"Apps"<\/span>)<\/span>)<\/span>;<\/span>
\nallAppsButton.clickAndWaitForNewWindow<\/span>(<\/span>)<\/span>;<\/span>
\n
\nUiObject appsTab =<\/span> new<\/span> UiObject(<\/span>new<\/span> UiSelector(<\/span>)<\/span>.text<\/span>(<\/span>"Apps"<\/span>)<\/span>)<\/span>;<\/span>
\nappsTab.click<\/span>(<\/span>)<\/span>;<\/span>
\n
\nUiScrollable appViews =<\/span> new<\/span> UiScrollable(<\/span>new<\/span> UiSelector(<\/span>)<\/span>.scrollable<\/span>(<\/span>true<\/span>)<\/span>)<\/span>;<\/span>
\nappViews.setAsHorizontalList<\/span>(<\/span>)<\/span>;<\/span>
\n
\nUiObject calculatorApp =<\/span> appViews.getChildByText<\/span>(<\/span>new<\/span> UiSelector(<\/span>)<\/span>.className<\/span>(<\/span>android.widget<\/span>.TextView<\/span>.class<\/span>.getName<\/span>(<\/span>)<\/span>)<\/span>, "Calculator app"<\/span>)<\/span>;<\/span>
\ncalculatorApp.clickAndWaitForNewWindow<\/span>(<\/span>)<\/span>;<\/span>
\n
\nUiObject oneButton =<\/span> new<\/span> UiObject(<\/span>new<\/span> UiSelector(<\/span>)<\/span>.text<\/span>(<\/span>"1"<\/span>)<\/span>)<\/span>;<\/span>
\noneButton.click<\/span>(<\/span>)<\/span>;<\/span>
\n
\nUiObject plusButton =<\/span> new<\/span> UiObject(<\/span>new<\/span> UiSelector(<\/span>)<\/span>.text<\/span>(<\/span>"+"<\/span>)<\/span>)<\/span>;<\/span>
\nplusButton.click<\/span>(<\/span>)<\/span>;<\/span>
\n
\nUiObject threeButton =<\/span> new<\/span> UiObject(<\/span>new<\/span> UiSelector(<\/span>)<\/span>.text<\/span>(<\/span>"3"<\/span>)<\/span>)<\/span>;<\/span>
\nthreeButton.click<\/span>(<\/span>)<\/span>;<\/span>
\n
\nUiObject eqButton =<\/span> new<\/span> UiObject(<\/span>new<\/span> UiSelector(<\/span>)<\/span>.text<\/span>(<\/span>"="<\/span>)<\/span>)<\/span>;<\/span>
\neqButton.click<\/span>(<\/span>)<\/span>;<\/span>
\n
\nUiObject text =<\/span> new<\/span> UiObject(<\/span>new<\/span> UiSelector(<\/span>)<\/span>.className<\/span>(<\/span>"android.widget.EditText"<\/span>)<\/span>.text<\/span>(<\/span>"4"<\/span>)<\/span>)<\/span>;<\/span>
\nassertTrue(<\/span>text.exists<\/span>(<\/span>)<\/span>)<\/span>;<\/span><\/div><\/div>\n

Unfortunately there is little documentation available. Also the framework only supports Android 4.1 or higher.
\nIn short:<\/p>\n