- From: Bryan Sullivan <blsaws@gmail.com>
- Date: Tue, 31 Jan 2012 15:14:52 -0800
- To: public-test-infra@w3.org
Oops, gotta love Gmail. Anyway I was going to continue, that if anyone has input on those objectives please chime in on this list, and help me develop the set of info that will help us determine consensus etc. I know there is some useful prior work and current practices that will also be referenced, and some analysis done on the pros/cons of them might be useful. But first spreading the word about how groups go about developing test assertions and test documentation/assets, and what methods might be useful to consider for groups who don't have a specific method for these, is the first step. In addition to the page noted below, some initial data is provided at http://www.w3.org/wiki/Testing/Assertions. This is a rough first pass and incomplete, purely in the data collection phase of this. Thanks, Bryan Sullivan On Tue, Jan 31, 2012 at 3:06 PM, Bryan Sullivan <blsaws@gmail.com> wrote: > Hi all, > > To get the ball rolling on the "Documentation Practices" task force of > the Web Testing Interest Group, that I agreed to lead during TPAC, I > have created a set of wiki pages where the work in progress of the TF > can be collected. As noted on the wiki page > (http://www.w3.org/wiki/Testing/Documentation_Practices), the goal of > this task force is to: > * determine the current practices for > developing test assertions as part of W3C specs > processes to review and approve tests > broadening consensus on the above > promoting adoption of the consensus approach > > -- > Thanks, > Bryan Sullivan -- Thanks, Bryan Sullivan
Received on Tuesday, 31 January 2012 23:15:20 UTC