tree: 7790474752831a744e99e8aad50d2e43ad60db2a [path history] [tgz]
  1. .settings/
  2. accelerometer/
  3. audio/
  4. autotest/
  5. battery/
  6. benchmarks/
  7. bin/
  8. camera/
  9. compass/
  10. contacts/
  11. events/
  12. inappbrowser/
  13. lazyloadjs/
  14. location/
  15. misc/
  16. network/
  17. notification/
  18. sounds/
  19. splashscreen/
  20. sql/
  21. storage/
  22. tizen-web-ui-fw/
  23. .DS_Store
  24. .project
  25. .rds_delta
  27. config.xml
  28. cordova-2.9.0.js
  29. cordova.js
  30. formation jS.js
  31. icon.png
  32. index.html
  33. index.html~
  35. main.js
  36. master.css

Mobile Spec Suite

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-, edit the VERSION variable in the cordova.js file as follows:

var VERSION='';

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!

  • (with all subdomains)
  • httpssss:// (bad protocol necessary)