- From: Zhang, Zhiqiang <zhiqiang.zhang@intel.com>
- Date: Fri, 26 Feb 2016 09:12:54 +0000
- To: W3C Device APIs WG <public-device-apis@w3.org>
Hi, After hard debugging and revising, we now have a good quality test suite at http://w3c-test.org/battery-status/ I run all the tests with Firefox Nightly 47 and Chrome beta 49 on both Windows and Android, and generated an implementation testing report snapshot with failure analysis at https://w3c.github.io/test-results/battery-status/20160226.html This report shows that the Battery Status API has got 2 implementations, so that we can advance the specification to next. Failures analyzed as: 1. http://www.w3c-test.org/battery-status/battery-interface-idlharness.html Chrome has 2 failures which are not specific to Battery Status API: - the first due to throwing instead of rejecting on promise returning methods (in this case, getBattery()); may be related to https://bugs.chromium.org/p/chromium/issues/detail?id=335019 - the second due to a general bug of Chrome with WebIDL, see https://code.google.com/p/chromium/issues/detail?id=239915 2. Chrome for Android doesn't support (dis)chargingTime, see https://code.google.com/p/chromium/issues/detail?id=401553. This causes the failure of http://www.w3c-test.org/battery-status/battery-full-manual.html ... and incomplete run of http://www.w3c-test.org/battery-status/battery-plugging-in-manual.html http://www.w3c-test.org/battery-status/battery-unplugging-manual.html I also updated https://www.w3.org/2009/dap/wiki/ImplementationStatus with the above testing results. Thanks, Zhiqiang
Received on Friday, 26 February 2016 09:13:26 UTC