- From: Harry Halpin <hhalpin@w3.org>
- Date: Wed, 24 Apr 2013 01:23:17 +0100
- To: public-webcrypto@w3.org
Everyone, Tomorrow at our F2F Robin Berjon, who is managing the test-suite for the HTML WG, will walk us through how HTML, WebApps, and other WGs are preparing their test-suites. Here's the links necessary to follow him: Currently, testing documentation is a bit sketchy although the process is straightforward. We also have a new employee (Tobie Langel, on loan from Facebook as a W3C Fellow) that will be helping documentation and the process. The process will work via GitHub, in particular via the W3C Testing Repo: https://github.com/w3c/ WebCrypto is here, as it will be part of the Web Platform: https://github.com/w3c/web-platform-tests/tree/master/WebCryptoAPI It's empty now :) Some of you have GitHub accounts (you know if you've been getting the email updates), and if you want to get access to the test-suite infrastructure, just email me and we'll set it up - or we can do it real quick tomorrow in person. Instructions for the Git process are here: http://darobin.github.com/test-harness-tutorial/docs/using-testharness.html. In general: - There is one subdirectory per section ID in the spec (with subdirectories matching that rule too), up to a max depth of 3. - W3C WGs tend not to use submitted/approved directories. Instead everything that's in the master branch is approved, and people (including from within the group) use pull requests to submit tests. A good example of pull is: https://github.com/w3c/html-testsuite/pull/18 For an async example, see here: https://github.com/w3c/web-platform-tests/blob/master/old-tests/submission/Microsoft/structuredclone/structuredclone_0.html We can use other frameworks - W3C process doesn't restrict us. For example, Selenium can still be used (including for user interaction in particular), but in general as we don't have user-interaction and the W3C process is there to test native functions, the W3C testing process outlined above is generally considered by most other WGs a good way forward. cheers, harry
Received on Wednesday, 24 April 2013 00:23:18 UTC