Marcel Kinard c255a84941 CB-7674 move preference activation back into onCreate()
The preference creation actually needs to be before
super.onCreate(savedInstance) in order to avoid the exception
"requestFeature() must be called before adding content". Also ran into an
issue in the native tests "Whitelist" and "User WebView/Client/Chrome" where
it would throw an exception that the CordovaWebView appView already had
a parent and needed to be removed from that parent before the invocation
to root.addView(appView). So I conditionally remove the wrong parent.
Also made a change to the native tests so the menus test would work.
I also put super.init() back into the template, though invoking it is optional
as loadUrl will call it automatically if needed.
2014-09-30 19:38:34 -04:00
..
2014-08-29 18:07:29 -04:00
2013-11-29 14:28:10 -08:00

Android Native Tests

These tests are designed to verify Android native features and other Android specific features.

Initial Setup

There really isn't any manual setup to do. The ant script takes care of that. You don't even need to compile cordova-x.y.z.jar or copy it, because project.properties has a library reference to ../framework. However, Robotium has to be installed for the onScrollChanged tests to work correctly. It can be found at https://code.google.com/p/robotium/ and the jar should be put in the 'libs' directory'.

To run manually from command line:

  1. Build by entering ant debug install
  2. Run tests by clicking on "CordovaNativeTests" app icon on the device

To run from Eclipse:

  1. Import Android project into Eclipse
  2. Ensure Project properties "Java Build Path" includes the lib/cordova-x.y.z.jar
  3. Create run configuration if not already created
  4. Run As -> Android JUnit Test

Automatic Runs

Once you have installed the test, you can launch and run the tests automatically with the below command:

adb shell am instrument -w org.apache.cordova.test/android.test.InstrumentationTestRunner