Is it not possible to automation android app using espresso without source code. Gradle expects a structure like this:
src/main/
src/androidTest/
I am not sure if this is still relevant to you but I will leave my comment for the ages. First some general information:
White-box Testing is simply put - testing an app WITH the source code. It requires programming and understanding of the app architecture when designing the tests
Black-box Testing is testing your app WITHOUT the source code of the app. It again requires some programming, but you design your tests without any knowledge of the architecture.
In your case:
Is it not possible to automation android app using espresso without source code.
As per the upper two definitions - Yes it is possible with a Black-box testing framework.
But I would like to run these automation tests on a different version of the app? Is this possible just by installing the app and running the tests?
Yes this is possible using a black-box app.
However, your choice - Espresso is a white-box testing framework. You have two possible solutions:
as i understand older version of your app doesn't have espresso tests.
Open a commit with different version of app, into androidTest
include tests and run assembleAndroidTest
Gradle task to make an app which already would have included your tests.
This version of app might be useful for Testdroid platform.
I'm not an expert in this, but I can also suggest you to use monkey
tool
Read about it here: http://developer.android.com/tools/help/monkey.html
and if you know a bit Python you can use monkeyrunner
for this.
Check: http://developer.android.com/tools/help/monkeyrunner_concepts.html
These two tools will help you a lot to run the test on the different versions of app.
Hope it help
The answer is yes, you can run automation test using Espresso without app source code.
Espresso is based on Android instrumentation framework, which means the automation test is built into a single test apk. This test apk is different from normal application apk:
There is an instrumentation registered in AndroidManifest.xml, which will be registered to Android system once test apk is installed
The test apk must be signed using the same signature with the application apk, in order to run automation test
The test apk runs in the same process as application apk
Above are the only requirements of any instrument based test framework has. So there is no dependency of source code.
But why we find most of the Espresso tutorials are mixed with source code? Because it will make the test simpler:
You can easily control the activity lifecycle using class ActivityTestRule.
You can test application defined classes easily.
You can test UI widgets using widget id
On the contrary, you have to write lots of reflection code to get the classes you need if you don't compile with source code. For example:
You have to use Class.forName to load the entrance activity and launch it
You have to use Java reflection to test application defined classes
You have to use literal information to find UI widgets, because you don't have the id of the UI widgets
To sum up, it is OK to run Espresso automation test without application source code, but it's much harder and make test codes ugly.
You can refer the example project from AndroidTestWithoutSource.
As per my knowledge, espresso requires application source code.So it is not possible to automate it with just an apk build.