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