commit | 3fc5df02cbd8036677e308cd767bef7f46904d21 | [log] [tgz] |
---|---|---|
author | Andrew Grieve <agrieve@chromium.org> | Mon Apr 29 12:26:56 2013 -0400 |
committer | Andrew Grieve <agrieve@chromium.org> | Mon Apr 29 12:28:23 2013 -0400 |
tree | 5aad90b288c6de1d4664628efe873cb1a67906ff | |
parent | c004cd354ecd95f31c12b36ee2dcabc13c8685cb [diff] |
[CB-3295] Add assertions for InAppBrowser load events (cherry picked from commit dc2f6f4ab175ddd987ef614c1f75fb678bbb4ccd)
These specs are designed to run inside the mobile device that implements it - it will fail in the DESKTOP browser.
These set of tests is designed to be used with Cordova. You should initialize a fresh Cordova repository for a target platform and then toss these files into the www folder, replacing the contents.
Make sure you include cordova-*.js in the www folder. You also need to edit cordova.js to reference the version of cordova-*.js file you are testing. For example, to test with cordova-0.9.6.1, edit the VERSION variable in the cordova.js file as follows:
var VERSION='0.9.6.1';
This is done so that you don't have to modify every HTML file when you want to test a new version of Cordova.
The goal is to test mobile device functionality inside a mobile browser. Where possible, the Cordova API lines up with HTML 5 spec. Maybe down the road we could use this spec for parts of HTML 5, too :)
Various parts of this test suite communicate with external servers. Therefore, when you wrap up the test suite inside a Cordova application, make sure you add the following entries to the whitelist!