commit | 019c43ef8fe940289145c557bd669df60eb3b759 | [log] [tgz] |
---|---|---|
author | Joe Bowser <bowserj@apache.org> | Mon Sep 10 14:17:31 2012 -0700 |
committer | Joe Bowser <bowserj@apache.org> | Mon Sep 10 14:17:31 2012 -0700 |
tree | 7717ace815a01cebb9d17b6e2f1746d88c571219 | |
parent | 8cb36ea4470113932d59020b818962ed259c06b9 [diff] |
Adding different bridge benchmarking to the Automated Mobile Spec Tests
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!