- From: Dominique Hazael-Massieux <dom@w3.org>
- Date: Thu, 30 May 2013 15:02:22 +0200
- To: public-device-apis@w3.org
Hi, As discussed previously, and as part of my ACTION-625, I have migrated our existing test suites to the W3C github web-platform-tests repository. The battery test cases are now in the pull request 124 on that repo: https://github.com/w3c/web-platform-tests/pull/124 https://w3c-test.org/web-platform-tests/submissions/124/battery-status/ Vibration test cases are in the pull request 125: https://github.com/w3c/web-platform-tests/pull/125 https://w3c-test.org/web-platform-tests/submissions/125/vibration/ Ambient light test cases in pull request 126: https://github.com/w3c/web-platform-tests/pull/126 https://w3c-test.org/web-platform-tests/submissions/126/ambient-light/ And proximity event test cases in 127: https://github.com/w3c/web-platform-tests/pull/127 https://w3c-test.org/web-platform-tests/submissions/127/proximity/ I've removed the existing test cases from the mercurial repository (dvcs.w3.org), and redirect the previous w3c-test.org addresses to the new ones. I have updated the links from the Working Group home page. I have not migrated the test suite for the media capture and streams spec yet, since I need to ask the media capture task force whether they're ok with it. Also, we will need to define the process we want to follow to make these test cases official and thus integrate them in the main repository rather than letting them leave as pull requests. A good source of inspiration is likely to be the WebApps test review and approval workflow: http://www.w3.org/wiki/Webapps/Submitting_tests#Test_Review_and_Approval_Workflow Dom
Received on Thursday, 30 May 2013 13:02:43 UTC