commit | f86d530fcedc4c3b783282f307b82656bcb3b1d2 | [log] [tgz] |
---|---|---|
author | Fil Maj <maj.fil@gmail.com> | Fri Feb 15 15:01:45 2013 -0800 |
committer | Fil Maj <maj.fil@gmail.com> | Fri Feb 15 15:01:45 2013 -0800 |
tree | 506d3ac9726ad6d3d58a6e2175a2aa5e9d3e7a72 | |
parent | 10e1d54d0e6c2f7f3c2c34566a257724cc93c767 [diff] |
CB-2331: adding "body" property on FileTransferError object.
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!