Add UI Testing

[sauloaguiar]

Follow these suggestions
http://blog.greenhouseci.com/greenhouse/update/android-testing-with-kotlin/
https://github.com/pot8os/Kotlin-Espresso-sample/blob/master/app/src/androidTest/kotlin/net/pot8os/kotlintestsample/ApplicationTest.kt

To test the following paths in the application:
1.
Given that the app is open
Click on the about menu
Open the dialog and check the displayed information

Given that the app is open
Click on a project
Check the project name is displayed on the action bar

Given an open project
Select a developer under the list
Check that the browser opens with the correct url

[sauloaguiar]

To open the menu - as described in one of the test cases - it was necessary to check for the string instead of the id of the menu.
Espresso NoMatchingViewException when using withId matcher

Check if a dialog is displayed with Espresso

[sauloaguiar]

Need to check on Espresso Idling Resources.
Test cases are failing sometimes because we have an async call on our main screen that is being tested

[sauloaguiar]

Also check this essay on how to properly test apps - hint using dependency injection.

[sauloaguiar]

Some more progress on the task, but a lot of new challenges are coming up. I started by trying to solve the idling resource issue mentioned previously. This blog entry served as guide pointing me to use Jake Wharton's OkHttp Idling Resource lib as the solution. After struggling a bit trying to solve the proposed approach - two issues took me some time along the way:

• How to instantiate Java abstract classes using Kotlin
• Activity rule must be public

Now, the issue is still open because I'm unable to get a reference to my Application class - so I can have a reference to OkHttp member - from my espresso test class.