Re: [vibration] [capture] [battery] Test suite status, call for contributions (ACTION-675)

Hi Anssi,

I can take a look at the Vibration API tests. They are also not up to date
with the spec. How would I get started?

Regards,

Michael



On Thu, Jan 16, 2014 at 3:09 PM, Kostiainen, Anssi <
anssi.kostiainen@intel.com> wrote:

> Hi All,
>
> This is the status of the test suites for the following deliverables for
> the group: Vibration API, HTML Media Capture, and Battery Status API.
>
> All the specs are at CR, and the group is looking for interested folks’
> contributions to help complete the test suites. Below is the status of
> each, and relevant pointers to the w-p-t GH repo.
>
> * Vibration API
>
> Test suite (partial):
>
>   https://github.com/w3c/web-platform-tests/tree/master/vibration
>
> Status:
>
> The following test cases are missing (as per TODO.txt):
>
> - do nothing when hidden
> - cancel when dynamically hidden
> - reinstate when dynamically shown
> - invalid values
>
> * HTML Media Capture
>
> Test suite (submitted for review):
>
>   https://github.com/w3c/web-platform-tests/pull/306
>
> Status:
>
> The remaining open issue "should we test SHOULD?” is discussed at:
>
>
> http://lists.w3.org/Archives/Public/public-test-infra/2013JulSep/0240.html
>
> It seems the option 3) gets most support ("add meta data to those tests
> that aren't MUST requirements”). The test suite should be updated
> accordingly, after which the tests should be re-reviewed and approved.
>
> * Battery Status API
>
> Test suite (approved):
>
>   https://github.com/w3c/web-platform-tests/tree/master/battery-status
>
> Status:
>
> As per Zhiqiang: "we don't need to create more [test cases], just make the
> tests easier to be run because it is difficult to prepare for testing
> environment to get the event handlers to be fired.”
>
> Looking forward to your test contributions!
>
> This completes my ACTION-675.
>
> Thanks,
>
> -Anssi
>