tag | 8ab2ab8ce9a476059da2f240e3df4c0fa9f1acd2 | |
---|---|---|
tagger | lorinbeer <lorin@adobe.com> | Thu May 30 14:45:11 2013 -0700 |
object | a3374a58451e1e5aa52ab1273f8f189a44ac483d |
Cordova 2.8.0 Release Candidate 1
commit | a3374a58451e1e5aa52ab1273f8f189a44ac483d | [log] [tgz] |
---|---|---|
author | Ian Clelland <iclelland@chromium.org> | Wed May 29 15:24:07 2013 -0400 |
committer | Ian Clelland <iclelland@chromium.org> | Wed May 29 15:27:36 2013 -0400 |
tree | ab98a041d79fc3532addeb36c7204414f4ebade0 | |
parent | 4e18d6dc8da36f841c530a3e4e0d908b2e433c6f [diff] |
[CB-2200] Remove test dependency on deprecated device.name (cherry picked from commit d9bf705c711e9ba47853574ec08ef77c6d988025)
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!