- From: Arthur Barstow <art.barstow@gmail.com>
- Date: Mon, 12 Jan 2015 08:44:19 -0500
- To: Chris Ducharme <cgdjmrsp@gmail.com>, public-test-infra@w3.org
On 1/9/15 1:40 PM, Chris Ducharme wrote: > Hey all, > > I am a recent CS grad in training to be a security consultant. It has > been suggested to me that contributing to Test the Web Forward would > be a good way to get a better understanding of browsers, HTML5, > Javascript, the DOM, etc. I've got the tests to run locally, and I've > looked through the documentation and at the tests themselves. I have a > basic idea of how I could proceed, in terms of creating tests, but > being that I have no experience with javascript or HTML5 (and not > really any front-end web experience at all), I'm not exactly sure > where to start -- ie I don't know what exactly needs testing (. If > anyone could give me some guidance here, I would greatly appreciate it. Hi Chris, Thanks for the inquiry. It's great to see expressions of interest like this! If your interest is mostly related to Web security related specs, perhaps you should explicitly ask for guidance on the Web Application Security group's list <https://lists.w3.org/Archives/Public/public-webappsec/> (see also the group's spec status page <http://www.w3.org/2011/webappsec/>). Another option is to chat with the good folks in the consortium's #testing IRC channel [IRC]. (I think it is suboptimal the test suites at github/w3c/<spec-name>/ don't provide any status type information f.ex. "features untested", "features considered `well` tested", etc. However, I acknowledge such data can easily become outdated.) -Thanks, ArtB [IRC] <https://www.w3.org/wiki/IRC>
Received on Monday, 12 January 2015 13:44:47 UTC