RE: [battery] Battery testing and implementation report update

Hi Anssi,

> From: Kostiainen, Anssi
> Sent: Tuesday, February 10, 2015 15:27
> To: Zhang, Zhiqiang
> Cc: Frederick Hirsch; Marcos Caceres; W3C Device APIs WG; Dominique
> Hazael-Massieux
> Subject: Re: [battery] Battery testing and implementation report update
> 
> Hi Zhiqiang, All,
> 
> > On 10 Feb 2015, at 03:21, Zhang, Zhiqiang <zhiqiang.zhang@intel.com>
> wrote:
> >
> >> From: Kostiainen, Anssi
> 
> [...]
> 
> >> Zhiqiang is probably able to estimate how big an effort it'd be to update
> the
> >> test suite to match the latest spec (and will also welcome PRs :-)). I sent
> >> some suggestions for tasks at:
> >>
> >> https://lists.w3.org/Archives/Public/public-device-
> apis/2015Feb/0005.html
> >
> > Thanks again for the suggestions. I am working on the tests update. Hope
> to finish them in this week and make an initiative testing report before the
> Chinese New Year holidays (Feb. 17th).

I am afraid I cannot generate the initial test report at this time, because the wptreport generates an incorrect one after upgrade it to 0.1.2 (https://www.npmjs.com/package/wptreport). I will check the real problem soon.
 
> Sounds good. If you cannot update all the test cases by 17th Feb, feel free to
> share a subset of the test cases that have been updated for review.

As stated in another mail, all the test cases have been updated to reflect the latest spec.

> The initial test report would include Chrome only until the Firefox
> implementation has been updated.

Hmm, I also find that Chrome doesn't support chargingTime and dischargingTime attributes. See

http://code.google.com/p/chromium/issues/detail?id=401553

This will make most of the manual tests failure. Seems it is better to make the test report until these attributes are implemented.

Thanks,
Zhiqiang

Received on Friday, 13 February 2015 07:29:30 UTC