In this fresh forward looking 2.0 test we hope to encourage key technologies that will make the mobile platform simply rock. Of course we have the usual suspects like AJAX support and canvas which were tested in the WCTMB v1 test too. However we gear up by checking for Geolocation support which is very relevant to mobile users and for various helpful offline technologies like application cache and Web storage. These offline technologies help the Web in areas where Internet may be unreliable, which is a lot of places on most mobile devices!

We also make a daring leap into the fray to ask for support of video and audio, which is quite demanding on a mobile device. We allow for all sorts of codecs, though midi files and animated gifs won't pass. :)

We also test for new input types, rich text editing and font face support which could be a workaround where phones have a poor font, for instance for a particular locale. No matter where you are from or what language you speak, we hope to entangle you in the Web with any device to hand.

So go and test your mobile with the new test and if your browser scores a 110% you are cheating.

Thank you and we welcome your feedback on our mailing list.

We derived this methodology from our collaboration with the Web Applications Working Group on the development of the test suite for the Widgets Packaging & Configuration specification.

Feedback on the document is more than welcome!

WebIDL allows to define these interfaces with their methods and properties in an abstract language, while giving specifics on how they have to be implemented in EcmaScript (JavaScript’s official name).

Using that abstract language makes it possible to automatically generate a number of test cases to check the specified interfaces are correctly implemented (or as often, correctly specified!): I discovered a few weeks ago the great WTTJS tool that does exactly this — it takes a WebIDL definition, some indications on how to instantiate the declared interfaces, and it then generates a bunch of test cases that can easily be used directly in browsers.

For instance, after having extracted the WebIDL from the Geolocation API using the WebIDL checker, I got a set of test cases that allowed me to find out that the Geolocation API was not clear enough on defining which interfaces were supposed to be directly instantiable — this has now been partially corrected in the latest Editors draft.

The WebIDL specification is still evolving, and as a result, not all its constructs are currently supported in WTTJS, so running it on a WebIDLs fragments that use the latest syntax capabilities will likely require some light hand edits; but it certainly remains a great tool to help in the development of JavaScript specifications. Thank you, Wakaba!

“The cornerstone of all testing done on the core of the Opera browser is our automated regression testing system, named SPARTAN. The system consists of a central server and about 50 test machines running our 120 000 automated tests on all core reference builds. The purpose of this system is to help us discover any new bugs we introduce as early as possible, so that we can fix them before they cause any trouble for our users.”

Read more on the Core Concerns blog.

The first Test Workshop has concluded as a productive face-to-face meeting.

Work is now focusing on testing Widget Digital signature support in widget runtimes and further review. Your comments are very welcome.

Widget runtime implementors are encouraged to take a look at http://webarchive.nationalarchives.gov.uk/20110509101621/http://dev.w3.org/2006/waf/widgets/tests/test-suite.xml as it may help them implement an interoperable W3C widget runtime.