Details
-
Sub-task
-
Resolution: Unresolved
-
Major
-
None
-
android_1.0.0.Alpha1
-
None
Description
Once the packaging problem is figured out, the next step consists of bringing user a way how to configure what should be tested in Arquillian test.
More information about Android is here http://developer.android.com/guide/topics/testing/testing_android.html, focus on "Running Tests" section.
Possible proposal
@RunWith(Arquillian.class) public class AndroidTest { @Test public void androidActivity(@AndroidActivity HelloAndroid helloAndroid) { mView = (TextView) mActivity.findViewById(com.example.helloandroid.R.id.textview); resourceString = mActivity.getString(com.example.helloandroid.R.string.hello); assertEquals(resourceString,(String)mView.getText()); } }
You can obviously inject into fields, make this a class scoped, not method scoped etc. Feel free to experiment and figure out what is the most convenient for users.
Also note that your infrastructure should support Robotium in future.