- From: Anssi Kostiainen via GitHub <sysbot+gh@w3.org>
- Date: Mon, 23 Oct 2017 07:12:10 +0000
- To: public-device-apis-log@w3.org
@Honry, as we prepare for this PR to land, could you evaluate the gaps in the [battery-status test suite](https://github.com/w3c/web-platform-tests/tree/master/battery-status) (in the spirit of [test as you commit](https://w3c.github.io/dap-charter/DeviceAPICharter.html#deliverables), soon to be adopted for all deliverables), and update the test suite accordingly? Even if I see my name in OWNERS, I may not have the cycles to pull off the test suite update at this time, and I'd +1 you to become an owner for the battery status test suite. On a quick glimpse, I think we need to update the iframe tests and add new tests the Feature Policy integration, and test interesting edge cases such as https://github.com/w3c/battery/pull/13#issuecomment-330586985 @foolip, this is another API that needs a bunch of manual tests due to its inherent nature, similarly to Vibration API. Is the following guide still considered the state of the art in manual w-p-t testing? :-) http://web-platform-tests.org/writing-tests/manual.html -- GitHub Notification of comment by anssiko Please view or discuss this issue at https://github.com/w3c/battery/pull/13#issuecomment-338567395 using your GitHub account
Received on Monday, 23 October 2017 07:12:14 UTC