W3C home > Mailing lists > Public > public-test-infra@w3.org > April to June 2014

WebTV Help for Getting Engaged in W3C Test Effort

From: SULLIVAN, BRYAN L <bs3131@att.com>
Date: Wed, 16 Apr 2014 14:23:36 +0000
To: "'public-test-infra@w3.org'" <public-test-infra@w3.org>, "'public-web-and-tv@w3.org'" <public-web-and-tv@w3.org>
Message-ID: <59A39E87EA9F964A836299497B686C351E52E57A@WABOTH9MSGUSR8D.ITServices.sbc.com>
Hi all,

In the 4th Web & TV Workshop, one of the action items that I said I would take was to help disseminate useful information to WebTV members that want to get engaged in the testing effort at W3C, as a first step toward closing the gaps in WebTV-usecase test assets and methodology noted in the workshop. This is addressing a specific need of the WebTV IG, but should be useful for any community of interest (e.g. WebMob) or new contributors at large.

This information will be provided on the test-infra list (http://lists.w3.org/Archives/Public/public-test-infra/), and for more convenient/long-term use on one or more of:

*         the Testing Wiki (https://www.w3.org/wiki/Testing) - note the "not maintained" banner for now, but I expect that it will get maintained soon as part of this effort, unless the places below take precendence

*         the TTWF site (http://testthewebforward.org/) if/once I figure out how we can add communities of interest (e.g. WebTV, Mobile, etc) to TTWF. TTWF should be the preferred public home for such info I think.

*         The W3C github repository (http://testthewebforward.org/) in particular the readme.md (https://github.com/w3c/web-platform-tests/blob/master/README.md) or some other place on the github site, for more detailed help in getting engaged.

The point of putting this info on one of these more permanent/usable places is to prevent people who want to get engaged, from having to rediscover this info each time (similar to forum FAQ/sticky posts) and bug the list etc with newbie questions. We can also add a "who to ask" list if questions aren't answered there and direct people to the test-infra list as a backup.

Our intent to do this is not to put a management layer on the testing effort, rather to make it easier for people to get engaged and to organize as a community of interest around closing the gaps that matter to them. This may include reviewing existing tests, adding new ones, building metadata e.g. test runner scripts that focus test runs on specific features or link tests to specific features/assertions where that info is missing from tests, sharing test results, etc.

Any other info that people have on "how to get engaged" info and where that is documented, is requested as a response to this post.

Bryan Sullivan | Service Standards | AT&T
Received on Wednesday, 16 April 2014 14:24:33 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:34:10 UTC