commit | 4e18d6dc8da36f841c530a3e4e0d908b2e433c6f | [log] [tgz] |
---|---|---|
author | Andrew Grieve <agrieve@chromium.org> | Tue May 28 16:59:54 2013 -0400 |
committer | Andrew Grieve <agrieve@chromium.org> | Tue May 28 17:00:18 2013 -0400 |
tree | f0141642a8b37917cb1030fcfe987d9f1ab4f345 | |
parent | d909b04b5965ceb5a15179d0012438caf6bc8e36 [diff] |
Add missing license headers found by RAT (cherry picked from commit db9df63a6831bd1c80c92433f13f53c97a1c225d)
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 (see the code in cordova-incl.js for clarification).
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!