tree: 61b0b0212f56dbf19908158690264c04719b3729 [path history] [tgz]
  1. .project
  2. .settings/
  3. 404.html
  6. accelerometer/
  7. apple-touch-icon-114x114-precomposed.png
  8. apple-touch-icon-57x57-precomposed.png
  9. apple-touch-icon-72x72-precomposed.png
  10. apple-touch-icon-precomposed.png
  11. apple-touch-icon.png
  12. audio/
  13. autotest/
  14. battery/
  15. camera/
  16. compass/
  17. config.xml
  18. contacts/
  19. cordova-2.0.0.js
  20. cordova.js
  21. crossdomain.xml
  22. css/
  23. events/
  24. favicon.ico
  25. humans.txt
  26. index.html
  27. js/
  28. location/
  29. main.js
  30. master.css
  31. misc/
  32. mobile-spec.wgt
  33. network/
  34. notification/
  35. robots.txt
  36. signature1.xml
  37. sounds/
  38. sql/
  39. storage/
  40. test/
  41. tizen.css
tizen SDK samples/mobile-spec/

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)