W3C home > Mailing lists > Public > public-device-apis@w3.org > January 2012

Re: Heads up: testing of the Vibration API

From: Robin Berjon <robin@berjon.com>
Date: Fri, 27 Jan 2012 17:25:35 +0100
Message-Id: <EEB75CFA-C320-47EE-B06C-C0E2CBE22F06@berjon.com>
To: "public-device-apis@w3.org public-device-apis@w3.org" <public-device-apis@w3.org>
On Jan 27, 2012, at 12:30 , Robin Berjon wrote:
> I'll start to commit stuff to HG once it's in a state that roughly works.

A first pass at these tests can be found at:

    http://dvcs.w3.org/hg/dap/file/tip/tests/vibration/submissions/robin

When possible, they use the testharness.js script that we've agreed to align on (it's used by all other API groups). However since these are interactive tests (the user has to pay attention to the vibration that's happening) it cannot do much.

They should properly take vendor prefixes into account, so if that's what your implementation has currently, they ought to work (if you use a vendor prefix that the code doesn't know of, let me know).

I haven't tested these a lot, use with caution! They might not make sense at all in some cases.

The template for the tests uses metadata that makes them fit for integration with the W3C Test Framework. Currently it isn't documented, but I'll be fixing that very soon.

When the tests are reviewed and approved, they can move to the "approved" section. Of course, feel free to make your own submissions :)

The biggest part that's missing right now is tests that interact with Page Visibility. I have ideas about how to do that, but I need more work.

Have a nice week-end!

-- 
Robin Berjon - http://berjon.com/ - @robinberjon
Received on Friday, 27 January 2012 16:26:10 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:14:27 GMT